Aqualogic 5.7 - web services in a clustered environment

Folks,
Has anyone encountered the following problem:
1. Expose a process as a web service (ex. process creation)
2. Deploy the process to a clustered weblogic server (in my case, weblogic 8.1sp6)
3. Start up all nodes
what I notice is that one of the nodes exposes the webservice via the normal fuegoServices/ws/... URL, but the other one doesn't.
And when I stop the one node that does expose the service, suddenly the web service appears in the other node!
All other web applications, like the portal and webconsole, are available in both nodes when both are up.
Does anyone know what I'm missing? Surely there is a configuration item somewhere that I need to set, but I just don't know where.
Thanks,
-Ian

As long as your users are in the LDAP for your 10.5 server, they should be able to authenticate to your Leopard Server and utilize the services you need. I haven't tried using a 10.5 server "connected to a directory server" that was a 10.4 server yet, but I would think that it should still allow your users to authenticate via it's connection to your OD server.

Similar Messages

Web services on a clustered server

Hi,
          I'm newbie on web services and I made a simple web service with bea workshop. when I try to deploy it on a bea WLS that has a unique server all works fine, also when I try to test the WS through http://myserver:7001/myapplication/mywebservice.jws or when I try to visualize the WSDL file through http://myserver:7001/myapplication/mywebservice.jws?WSDL.
          But when I try to deploy the same WS on a clustered server (with 1 admin server and 2 clustered server) I don't find the WS and if I try to visualize the WSDL file I get a WEBSERVICE ERROR on the browser :O
          can anyone help me
          thanks in advice
          Daniele

External domains are a prerequisite here, and a minimum of one public static IP address.
You can set that up with a reverse proxy (Apache reverse proxy) through the Xserve box, allowing connections from outside to reach the Xserve and the Xserve communicating with the Mac Mini box. This is basically a web pass-through, were Apache running on your Xserve can hand off to your Mac Mini. This involves reading the [web manual|http://www.apple.com/server/macosx/resources/documentation.html] and using Server Admin to establish the reverse proxy.
You can also set up a mid-level server-grade external firewall (using an external firewall and not a Mac is locally preferred for various reasons) to have it port-forward connections based on IP address, for instance. This is a more traditional set-up for a web server, and is covered in various IP network configuration discussions around the Internet. This involves setting up your network with a reasonable mid-range commercial or open-source firewall, and establishing port-forwarding on the firewall.
You must expect your servers to be attacked, and you will be attacked. The servers I administer are attacked many times a day, with XSS and SQL injection attempts and probes for various other known vulnerabilities, dictionary attacks against passwords, and attempts to post spam on the web sites are also very common. This involves monitoring your logs, watching for attacks, and staying current on all your software and keeping your archives current; your (trusted) backups are the path back from a server breach.
You may want to consider a DMZ for your public-facing services, which is another feature of a typical server-grade firewall, as a web breach can get hairy for the rest of your LAN. Using a properly-configured DMZ usually isolates a breach.
Here's an old [write-up on the various network pieces|http://labs.hoffmanlabs.com/node/275] that can be involved in a small server-oriented network configuration.

Web Services Session /Singleton cluster environment

Hi!
I am having trouble figuring out how to do sessions in web services.
I am trying to build an app that uses multiple GUI's in different languages (not java) and we want to implement our business layer with web services.
I need a session to save user settings, and user info so that I can avoid going to the database and ldap in every call.
So far my idea is to have a web service that deals with the authentication. If the user is valid, the web service will save in a singleton that has hashmap the user setting and return to the client the hashmap key as a token.
The client has the responsibility to save the token and to use it in later calls.
The problem that I have is that a singleton would not work in a cluster environment! And I really don't want to be passing all the user information between calls
Any ideas how can I solve this???

Hi Gaurav,
Yes, the currently running session will be taken care of by the another server node which is up and running.
Your question: Does this mean that the a session of WebDynpro application will continue to work or the changes are lost and the user needs to login again?
"The state of the session is maintained in the persistent storage after the last successfully ended request." Which means that for example a user was filling up a form and haven't saved the changes and the server crashes then the data on that form will be lost when the second server node starts processing the request. But if the user had saved the data before the server crashes that state of the session will be stored and the data of the form will be saved and user need not fill it up again. If the Server crashes in between the HTTP request session then the request is assinged to the another server node to generate the response. In none of the case user needs to login again.
Your question: Fundamentally the question is what WebDynpro uses behind the scenes for maintaining session?
It uses Java Serialization to serialize the HTTP Sessions
"Serialization involves saving the current state of an object to a stream, and restoring an equivalent object from that stream. The stream functions as a container for the object. The information stored in the container can later be used to construct an equivalent object containing the same data as the original."
Edited by: Aishwarya Sharma on Oct 7, 2008 8:07 AM

How to create Web Service based on PI WSDL message

Hi all,
we have following scenario:
Within PI (version 7.1) we set up a message type and inbound service interface. This service interface should send the PI message to a web service running on a SAP J2EE (version 7.01). As the PI message is sent as WSDL I thought it should be easy to build a web service on the SAP J2EE based on this WSDL from PI.
Unfortunately, I have problems creating the Web Service.
For my current project we integrated the NWDI to the SAP NetWeaver Developer Studio and I'm required to add the Web Service to an existing DC (Development Component) within the NWDI.
What I tried so far is:
- I created a Deployable Proxy Project and within this I created a Client Proxy Definition based on the WSDL from the PI. But I can't add this Proxy to the DCs of the NWDI and I don't know how to implement my own coding here in order execute specific functions.
- I created a new class within the NWDI DC and a public method. Based on this I created a Virtual Interface and a Web Service Definition (WSD). Then I added this to a Web Service Deployment Descriptor. I uploaded this to the SAP J2EE. But I'm not able to access this and I don't know hoe to assign the WSDL here.
I also tried here to create a client proxy based on this WSD as I thought I might assign the WSDL here. But I don't see the WSD in the list of Web Services uploaded to the SAP J2EE...
Can you please advice me how to create a Web Service in such an environment?
regards
René Jurmann

Hi Tahir,
sorry that you needed to wait this long - but this is how I created the web service:
The steps on how to create the web service in NetWeaver Developer studio are nearly the same as described in the blog http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/5838. [original link is broken] [original link is broken] [original link is broken]
Some steps I just skipped and some others I added. Some of the steps I did the way I described it as I needed to connect the web service with the SAP PI.
Prerequisites:
Add Java Perspective and J2EE Development Perspective to the open perspectives.
Within "Window - Preferences - Web Services" check "Soap extensions visible in the virtual interface editor"
The SDM of the corresponding SAP J2EE is configured within "Window - Preferences"
Create a Development Component (DC) with type "J2EE -> EJB Module"
The business logic of the web service will be implemented in an Enterprise Java Bean (EJB). So first the EJB component must be created:
     Choose "File -> New -> Other"
     In opening PopUp choose "Development Component -> Development Component Project"
     Select the Software Component for which you want to add the DC (e.g. "Local Development -> MyComponents")
     Choose now vendor, name and type:
          vendor is an alpha-numeric string of 20 characters starting with a letter - all in lower case
          name is an alpha-numeric string starting with a letter - all in lower case
          vendor and name concatenated must not be longer then 40 characters
          the name can be separated into different part using "/" as separator
          each part of the name must not be longer than 8 characters
          the type is "J2EE - EJB Module"
          you can specify a Caption as general description for the web service
Create new EJB
To create the EJB itself:
     In J2EE DC Explorer of J2EE Development Perspective expand new DC and right-click on folder "ejbModule"
     Choose "New - EJB" with following details:
          EJB Name: <name as for PI service Interface to be created - starting in upper case>
          EJB Project: <pre selected>
          Bean Type: Stateless Session Bean
          Default EJB Package: <corresponds to namespace in PI>
          generate default interfaces: Checked
Regarding the "Default EJB Package" this should be created according the namespace in PI for which all PI objects will be created. This only applies if you have some naming conventions here.
Example:
Namespace in PI is: http://company.net/pi/SOFTWARE_COMP/Application
The corresponding package then is: net.company.pi.software_comp.application
Implement coding for web service
As the web service will be called via PI some transfer variables will be submitted. Most likely, those variables will not be standard type (e.g. String) but a complex type. Those types must be generated as Java classes. Below an example of a complex type I needed:
Data Type
net.company.pi.software_comp.application.types.MessageProcessingInformation
Structure:
     Element name          Element type
     sendingSystemID          String
     interfaceID               String
     businessProcessVariantCode     String
     testIndicator               Boolean
For every element described a public "get", "set" and "has" method must be created in the corresponding Java class:
package net.company.pi.software_comp.application.types;
import java.io.Serializable;
public class MessageProcessingInformation implements Serializable {
     protected String sendingSystemID;
     protected String interfaceID;
     protected String businessProcessVariantCode;
     protected Boolean testIndicator;
     public String getSendingSystemID() {
          return sendingSystemID;
     public void setSendingSystemID(String value) {
          this.sendingSystemID = value;
     public boolean hasSendingSystemID() {
          if(sendingSystemID != null && !sendingSystemID.equals("")){
               return true;
          return false;
All Java classes representing complex types and all classes referenced here (used for sub-types) must implement java.io.Serializable. Java standard types which do not implement this class must not be used as sub-types.
As soon as all data types are declared the real business logic can be implemented:
     In J2EE DC Explorer of J2EE Development Perspective expand DC - "ejb-jar.xml" - <Name> and double click on "ejbCreate"
     In detail view select folder "Business Methods" and click "Add"
     choose name of business method - this should be the same as the PI message type used for the service interface - starting lower case
     return type should be "void"
     add needed parameters fully qualified - including package (as specified in PI and created previously in DC)
     you can mark certain parameters as array if necessary
Remark:
It might be that after saving you get an error. This might be as the package name of one component is copied to the corresponding Java class at the very beginning (before the package declaration within the Java class). Simply delete the string here.
It also might be, that the new business method is only defined in the remote interface class but not in the bean class. Just create an according method in the bean class.
Within the newly created business method within the bean class you can now implement the business logic.
Create a DC with type "J2EE -> Enterprise Application"
In order to create the "real" web service and deploy it to the J2EE an Enterprise Application project has to be created. So create a new DC as for the EJB Module but choose as type "J2EE -> Enterprise Application".
After the DC is created right click on the EJB DC and choose "Add to EAR Project". Choose the new DC.
Create web service for EJB
As soon as you implemented the business logic you can create the "real" web service. Therefore:
     Right click on the EJB name below "ejb-jar.xml"
     Choose "New - Web Service"
     Choose proper "Web Service Name" and "Configuration Name" (probably oriented at the EJB name)
     Copy the URL of the web service - you'll need it later for PI configuration
     on the second next screen use the same name for "Virtual Interface" and "Web Service Definition" (the name should be the name of the "Endpoint")
     the "EAR Project" should be preselected
Unfortunately, the web service can't be used in its current configuration to be accessed by PI. Therefore the Virtual Interface must be changed. To do so, expand folder "Virtual Interfaces" and double click the virtual interface created.
Within the detail view expand in tabs "Mapping" and "Types" the complete folder structure. For any "SOAP Extension" where a namespace can be defined use as namespace the corresponding namespace in PI (e.g. http://corpintra.net/pi/CBFC_GLOBAL_SAP_APPL/BillerDirect) but do not change any "Soap Extension" of a standard Java type. (if you don't have any naming convetions for namespaces in PI you can leave the SOAP Extension here. But then the namespace in PI should be set accordingly.)
Probably it can be necessary on top level "Soap Extensions" in tab "Mapping" to leave "Use Namespaces for Parameters" unchecked. For some of my web services this parameter must be checked for others not - just try.
If you can define a "New Name", "Local Name" or "Item Label" for a Soap Extension then use a name with starting upper case letter. (For Java Naming conventions most of the data type names will start with lower case letters.) Especially the method name must be renamed this way in order to stick to the PI namings.
As a last point to change here check in tab "Mapping" all "Incoming Parameters" which you specified as array. Use for those as "New Name" a different name - do not just simply change from lower case to upper case. This is necessary as on PI we need to create two levels although here only one is specified.
For any own sub-type declared as array the name within the coding should also differ from the corresponding Java Class name the type refers to.
If all this is done you can deploy the web service to the J2EE:
     right click on "Enterprise Application" DC and choose "Development Component - Build..." and build all corresponding components
     right click on "Enterprise Application" DC and choose "Development Component - Deploy"
Test the new web service via <J2EE URL>/wsnavigator/enterwsdl.html
Create PI interface
After the web service is created successfully the PI integration can be started.
Therefore, within the Enterprise Services Builder create a data type according to the web service definition. All components defined on top-level for this data type should be declared as incoming parameter for the web service business method. Therefore it could be necessary to create some sub data types on PI first and add those to the "master" data type.
Ensure that the names of the components correspond to the names defined in the web service (see virtual interface here). Those names must exactly be the same - including lower/upper case. Also take care for the ordering of the components.
In case you need to include arrays following applies:
The upper level is of occurrence "1:1". This has only one sub-entry with occurrence "1:n". The names for upper and sub-level must not equal.
Based on the data type a message type is created. The name of the message type must be exactly the same as the name of the web service business method. (Hint: the name of the web service business method was most likely changed in the virtual interface. Then this name must correspond to the message type name.) Based on the message type an asynchronous inbound interface is to be created (which will be referred in the Integration Directory). The operation name for this interface (left panel) should be the same as the name for the web service business method.
Create PI mappings and routings
How to map (message mapping and operation mapping) from source to the web service message I wont explain here as this depends on the source message. The only important things here are:
     When creating the SOAP communication channel within the Integration Builder the "Target URL" is:
          <J2EE URL>/<Access URL as specified in web service creation>?wsdl&style=document
     The soap action is the name of the web service business method.
     Most likely the web service needs authentication to be executed.

Web Service in ABAP

All
I have created a Web Service in our Development environment
and we have given the WSDL to our consumer and he can consume
this service without issue.
We have saved the Devlopment work against the Transport Request.
Q: We will be transporting this development to our
next Test System and then production. Will the WDSL URL change?
I understand that URL will change since the Server will be different.
but to confirm my understanding, this question is.
Q: since we are transporting this Service from Dev to Test/Prod,
how do we find the new WDSL and URL for test/Prod system.
Please advice on the steps.
Cheers
RJ

Hi Kerim,
first of all, thank you for giving my a good path to analyze this issue. Finally I found a new error information inside the SRT_UTIL:
-ERROR_CONTEXT
--ERROR_INFO
---EXCEPTION_INFO
----TYPE CX_SOAP_CORE
----ERROR_TEXT SRT: Plain SOAP: Reliable messaging (RM) configured, but no Message
ID and no WSRM assertion provided.
----CX_SOAP_CORE
-----E_LOCATION
------CLASS     CL_SOAP_PLAIN_PROTOCOL
------METHOD
CHECK_FOR_QOS
-----E_TEXT    SRT: Plain SOAP: Reliable messaging (RM) configured, but no Message
ID and no WSRM assertion provided.
-----E_ID       1222
-----E_FAULT_LOCATION
1
-----E_AREA
-----E_HOST     1
-----E_PROCESS_CONTROL
--PROVIDER_INFO
---INTERFACE_NAME       Z_BW_WSDLTEST
---INTERFACE_NAMESPACE urn:sap-com:document:sap:rfc:functions
---PROVIDER_INTERFACE
Z_BW_WSDLTEST
---OPERATION_NAME       Z_WSDLTEST
---OPERATION_NAMESPACE urn:sap-com:document:sap:rfc:functions
---PROCESSING_UNIT
Sector 4: WS-Provider
---PROCESSING_MODE      Synchronous
---COMMUNICATION_TYPE
REMOTE
---WORK_PROCESS_NUMBER 30
---WORK_PROCESS_PID
606248
--REQUEST_INFO
---PROTOCOL     HTTP/1.1
---REQUEST_URI
/sap/bc/srt/rfc/sap/z_bw_wsdltest/100/zbwwsdltest/zbwwsdltest
Then I followed this description:
-ERROR_CONTEXT
--ERROR_INFO
---EXCEPTION_INFO
----TYPE CX_SOAP_CORE
----ERROR_TEXT SRT: Plain SOAP: Reliable messaging (RM) configured, but no Message
ID and no WSRM assertion provided.
----CX_SOAP_CORE
-----E_LOCATION
------CLASS     CL_SOAP_PLAIN_PROTOCOL
------METHOD
CHECK_FOR_QOS
-----E_TEXT    SRT: Plain SOAP: Reliable messaging (RM) configured, but no Message
ID and no WSRM assertion provided.
-----E_ID       1222
-----E_FAULT_LOCATION
1
-----E_AREA
-----E_HOST     1
-----E_PROCESS_CONTROL
--PROVIDER_INFO
---INTERFACE_NAME       Z_BW_WSDLTEST
---INTERFACE_NAMESPACE urn:sap-com:document:sap:rfc:functions
---PROVIDER_INTERFACE
Z_BW_WSDLTEST
---OPERATION_NAME       Z_WSDLTEST
---OPERATION_NAMESPACE urn:sap-com:document:sap:rfc:functions
---PROCESSING_UNIT
Sector 4: WS-Provider
---PROCESSING_MODE      Synchronous
---COMMUNICATION_TYPE
REMOTE
---WORK_PROCESS_NUMBER 30
---WORK_PROCESS_PID
606248
--REQUEST_INFO
---PROTOCOL     HTTP/1.1
---REQUEST_URI
/sap/bc/srt/rfc/sap/z_bw_wsdltest/100/zbwwsdltest/zbwwsdltest
Then I followed this description: http://scn.sap.com/thread/3278733
So I checked the Web Service operatioprofil where I changed the profil setting to asynchronously and the reliability message transport automatically switched to false. Unfortunately without success, means the error from SRT_UTIL persists!

Implementing Web Services in Lodestar

Dear all,
I'm trying to implement Web services using the Lodestar suite.
In particular, what I am trying to do is to implement a Web service that executes a Rate Schedule procedure.
The idea is to receive an XML message in input, perform some logic within the Rate Schedule, and then produce an XML in output.
Currently, I am able to register the Web service into the Lodestar environment and let clients to invoke it.
Upon the receive of a message, the proper Rate Schedule is executed and an output XML message is produced.
Unfortunately, what I am not able to do is to pass the content of the input message of the Web service to the Rate Schedule.
Do you know how to solve this issue?
Thanks in advance
Enrico

Sorry for such a late reply. There were few architectural changes coz of which web service implementation was taken outside OAE app. So, I was unable to get the debug output.
Still, I would be interested in knowing the possible root cause of the issue and a possible solution.
Thanks
Shruti

Join the Web Services Panel at COLLABORATE '06!

Please email [email protected] (latest by April 12, 2006) if you are interested in participating on the Web Services Panel scheduled to be held on Wednesday, April 26, 2006 during COLLABORATE '06 conference at the Gaylord Opryland Resort & Convention Center, Nashville, Tennessee, USA.
Panel members will share their knowledge, experiences, tips and techniques in using Web Services in an Oracle environment. Participate in an educational discussion with a panel of industry experts who will discuss unique and innovative approaches to using Web Services with E-Business Suite, PeopleSoft and JD Edwards applications. Learn about Web Services, Service-Oriented Architecture (SOA), Fusion Middleware, Project Fusion and more. Product Managers from Oracle Corporation will participate on the Web Services Panel as well.
Look forward to seeing you in Nashville!

Please email [email protected] (latest by April 12, 2006) if you are interested in participating on the Web Services Panel scheduled to be held on Wednesday, April 26, 2006 during COLLABORATE '06 conference at the Gaylord Opryland Resort & Convention Center, Nashville, Tennessee, USA.
Panel members will share their knowledge, experiences, tips and techniques in using Web Services in an Oracle environment. Participate in an educational discussion with a panel of industry experts who will discuss unique and innovative approaches to using Web Services with E-Business Suite, PeopleSoft and JD Edwards applications. Learn about Web Services, Service-Oriented Architecture (SOA), Fusion Middleware, Project Fusion and more. Product Managers from Oracle Corporation will participate on the Web Services Panel as well.
Look forward to seeing you in Nashville!

Web Services Deployment

Not sure if this is the best forum, but I am looking for guidance on deploying a simple Web Service in eBS r12i.
So basically, we want to have the Web Service available on the Web Server used by the application.
Any help much appreciated

Hi Anil,
Yes, this is a common setup in the field. One of the WebLogic Server Proxy Plug-ins
(i.e. NSAPI plug-in, Apache plug-in, IISAPI plug-in), is typically setup to "proxy"
the web service requests by either path (i.e. using all or a portion of the target
endpoint URL), MIME type (i.e. text/xml for SOAP 1.1 and application/soap+xml
for SOAP 1.2), or a combination of both.
Proxy "by path" and the Apache proxy plug-in are the most commonly chosen configuration
for this.
Refer to the information at the following link for specifics on how to setup the
WebLogic Server Proxy plug-in for Apache:
http://e-docs.bea.com/wls/docs70/plugins/apache.html#123030
Regards,
Mike Wooten
"Anil Kumar" <[email protected]> wrote:
>
What is the deployment strategy for the web services that are running
on WebLogic
7.x that is behind a firewall fronted by a web server in the DMZ? In
other words,
can a web services client (in our case, the client is another WebLogic
Server)
call the web service through the web server? If not, what are the typical
deployment
strategies for web services in a production environment?

Migrate Web Services

Hi,
We have developed several Web Services on an ECC 6.0 system. After upgrading the ECC system to ECC 6.0 Enhancement Package 4 the Administration & Monitoring is done through SOAMANAGER but we are unable to view the Web Services created prior to the upgrade. Instead we can view them only via WSADMIN and WSCONFIG. Our requirement is to have a common Administration, Configuration and Monitoring environment for both old and new Web Services (i.e. SOAMANAGER). Is it possible to migrate the old web services to the new environment? If this is the case could please advise us on how this is done and what are the possible effects on the old Web services? For instance will the URL of the WSDL be changed after we u2018migrateu2019 the old web services.
Thank you in advance.
Kind Regards
Mike

Hi,
You should also ask this question in the RDBMS forum -
General Database Discussions
Regards,
Mike

Web Services Deployment in Oracle9i

I have read several articles on Web Services on TechNet. It is still
not clear to me:
1. If I use Oracle9i EE on HP UNIX 11, do I have everything to deploy
web services. Many articles on web services mention about Oracle9i AS
OC4J containers. Does that mean I need Oracle9i AS (do I need to get a
license for it) or OC4J containers can be downloaded (if not already
available) with Oracle9i EE.
2. Same question for Oracle 10G, do I need Oracle10gAS for deployment.
I know using Oracle Jdeveloper, it is easy to develop web services, but
do I need anything from Developer to deploy a web service,
Thanks a lot.

Hi Anil,
Yes, this is a common setup in the field. One of the WebLogic Server Proxy Plug-ins
(i.e. NSAPI plug-in, Apache plug-in, IISAPI plug-in), is typically setup to "proxy"
the web service requests by either path (i.e. using all or a portion of the target
endpoint URL), MIME type (i.e. text/xml for SOAP 1.1 and application/soap+xml
for SOAP 1.2), or a combination of both.
Proxy "by path" and the Apache proxy plug-in are the most commonly chosen configuration
for this.
Refer to the information at the following link for specifics on how to setup the
WebLogic Server Proxy plug-in for Apache:
http://e-docs.bea.com/wls/docs70/plugins/apache.html#123030
Regards,
Mike Wooten
"Anil Kumar" <[email protected]> wrote:
>
What is the deployment strategy for the web services that are running
on WebLogic
7.x that is behind a firewall fronted by a web server in the DMZ? In
other words,
can a web services client (in our case, the client is another WebLogic
Server)
call the web service through the web server? If not, what are the typical
deployment
strategies for web services in a production environment?

How my client can acces to my web Services??

We want buy Oracle9iAS and we want know How our clients can access aour web services? They need some special software? or just need to send us a XML?
Thanks

As long as they can send standard XML based SOAP messages, Oracle can handle it. Interoperability based on standards is critical for the team building Web services into the Oracle environment.
Backing that up, here is some pointers. Oracle belongs to both the Web Services Interoperability (WS-I) group (actually was a founding member along with IBM and Microsoft - http://www.ws-i.org) and SOAPBuilders (which is an ad-hoc consortium of several dozen vendors working on interoperability - http://ws-interop.oracle.com/soapbuilder/). One of our roles on the WS-I team is working on building a reference implementation of the WS-I Basic profile (specific versions of SOAP, WSDL and UDDI) which will be used to show interoperability amongst vendors in the WS-I.
If you download the developer preview of Oracle9iAS Containers for J2EE (see: http://otn.oracle.com/tech/java/oc4j/content.html) you will see it includes the SOAPBuilders interoperability test showing this so you can test it out yourself.
To see which standards groups Oracle belongs to, check out this page - in the Java space we participate in over 68 Java Specification Requests and more every day - but we also belong to W3C, OASIS and dozens of other standards groups and take that participation very seriously: http://otn.oracle.com/tech/xml/htdocs/standard.html
Finally, to see how your partners can test in an Oracle Web services environment independent of any special software, check out the latest demo put up a few days ago showing the built in tester that comes with any Web service published on Oracle9iAS - you get a Web page which lets you pass in parameters and try the Web service out on the fly. This tutorial happens to be publishing PL/SQL as a Web service but the same applies if you publish an EJB, JMS queue, or Java class as a Web service (see step 24):
http://otn.oracle.com/tech/webservices/htdocs/series/plsql/content.html
Hope this is a start for you.
Mike.

Coldfusion 11 Web Services and SSL Issue

Our company has two web services that we host that a vendor uses to grab information from on a periodic basis. These services ran fine on a CF8 SSL site, but once we switched to 11, the services can no longer be created. However, I can create them on our unsecured test site (which also is running CF 11) and access them externally without issue. When I try to create the webservice in the url, I just get a blank page back instead of the XML I should be getting. Is there something special I am missing that has to be done to create web services in a secure environment? The raw error message I get when trying to invoke the secure web service is below:
coldfusion.xml.rpc.XmlRpcServiceImpl$BadWsdlXMLException: Unable to parse WSDL as an XML document. at coldfusion.xml.rpc.XmlRpcServiceImpl.retrieveWSDL(XmlRpcServiceImpl.java:976) at coldfusion.xml.rpc.XmlRpcServiceImpl.access$000(XmlRpcServiceImpl.java:96) at coldfusion.xml.rpc.XmlRpcServiceImpl$1.run(XmlRpcServiceImpl.java:309) at java.security.AccessController.doPrivileged(Native Method) at coldfusion.xml.rpc.XmlRpcServiceImpl.registerWebService(XmlRpcServiceImpl.java:302) at coldfusion.xml.rpc.XmlRpcServiceImpl.getWebServiceProxy(XmlRpcServiceImpl.java:692) at coldfusion.tagext.lang.InvokeTag.doEndTag(InvokeTag.java:469) at coldfusion.runtime.CfJspPage._emptyTcfTag(CfJspPage.java:2987) at cfcallmattersearch2ecfm1244659485.runPage(D:\Web\sims\st\callmattersearch.cfm:9) at coldfusion.runtime.CfJspPage.invoke(CfJspPage.java:246) at coldfusion.tagext.lang.IncludeTag.handlePageInvoke(IncludeTag.java:734) at coldfusion.tagext.lang.IncludeTag.doStartTag(IncludeTag.java:570) at coldfusion.filter.CfincludeFilter.invoke(CfincludeFilter.java:65) at coldfusion.filter.IpFilter.invoke(IpFilter.java:45) at coldfusion.filter.ApplicationFilter.invoke(ApplicationFilter.java:487) at coldfusion.filter.RequestMonitorFilter.invoke(RequestMonitorFilter.java:42) at coldfusion.filter.MonitoringFilter.invoke(MonitoringFilter.java:40) at coldfusion.filter.PathFilter.invoke(PathFilter.java:141) at coldfusion.filter.ExceptionFilter.invoke(ExceptionFilter.java:94) at coldfusion.filter.BrowserDebugFilter.invoke(BrowserDebugFilter.java:78) at coldfusion.filter.ClientScopePersistenceFilter.invoke(ClientScopePersistenceFilter.java:2 8) at coldfusion.filter.BrowserFilter.invoke(BrowserFilter.java:38) at coldfusion.filter.NoCacheFilter.invoke(NoCacheFilter.java:58) at coldfusion.filter.GlobalsFilter.invoke(GlobalsFilter.java:38) at coldfusion.filter.DatasourceFilter.invoke(DatasourceFilter.java:22) at coldfusion.filter.CachingFilter.invoke(CachingFilter.java:62) at coldfusion.CfmServlet.service(CfmServlet.java:219) at coldfusion.bootstrap.BootstrapServlet.service(BootstrapServlet.java:89) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:303) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at coldfusion.monitor.event.MonitoringServletFilter.doFilter(MonitoringServletFilter.java:42 ) at coldfusion.bootstrap.BootstrapFilter.doFilter(BootstrapFilter.java:46) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.j ava:241) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:422) at org.apache.coyote.ajp.AjpProcessor.process(AjpProcessor.java:198) at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.jav a:607) at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:313) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source)

I've got this working on our dev and test servers. Now I'm trying to deploy it to production. We have an external prod server in a DMZ that calls the web service on our internal prod server. We only have port 443 open in the firewall between these two servers (not port 80). I am able to do a <cfhttp> call to the WSDL over 443 and get back the xml. However, if I make the web service call using <cfinvoke> I get the following error:
Cannot perform web service invocation getNthDayOfMonth.
The fault returned when invoking the web service operation is:
org.apache.axis2.AxisFault: Connection refused
        at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
        at org.apache.axis2.transport.http.HTTPSender.sendViaPost(HTTPSender.java:197)
        at org.apache.axis2.transport.http.HTTPSender.send(HTTPSender.java:75)
        at org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(Common sHTTPTransportSender.java:402)
        at org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSen der.java:231)
        at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:443)
        at org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406)
        at org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java :229)
        at org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
        at standard.StandardDate_functionCfcStub.getNthDayOfMonth(StandardDate_functionCfcStub.java: 192)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorI... ''
I am able to successfully call the same web service (on the internal prod server) using the same code from my internal dev server. However, when I look at my httpd logs on the internal prod server, I don't see the request in the ssl logs. It shows up in the access_log file as:
150.231.26.130 - - [03/Feb/2015:13:48:57 -0500] "POST /standard/date_function.cfc HTTP/1.1" 200 397 "-" "Axis2"
Any thoughts why this appears to still be coming through port 80?

SOAP / Web Service clustering WLS 7.0.2

          Hi there,
          I'm looking for information on if and how WLS 7.0.2 is capable of
          clustering Web Services. We created the Web Service like following:
          - Created a stateless session bean first
          - Created the web service with a servicegen ant task
          I browsed through edocs.bea.com but
          up to now with no success.
          Any help is greatly appreciated.
          Best regards,
          Fabio


          "Fabio Barone" <[email protected]> wrote:
          >
          >Hi there,
          >
          >I'm looking for information on if and how WLS 7.0.2 is capable of
          >clustering Web Services. We created the Web Service like following:
          >- Created a stateless session bean first
          >- Created the web service with a servicegen ant task
          >
          >We need the clustering service for high availability, not
          >for load balancing or session fail-over.
          >
          >Our IT dept. offered a hardware solution with CISCO load-balancers
          >first (our preferred solution for high availability).
          >However, the guys here are not able to configure the hardware properly,
          >that's why we're looking for alternatives with the WLS cluster.
          >
          >I browsed through edocs.bea.com but
          >up to now with no success.
          >
          >Any help is greatly appreciated.
          >
          >Best regards,
          >Fabio
          Fabio, your other alternative is through a group of Web servers configured identically
          using Weblogic proxy plugins. WLS can also act as a load-balancing proxy to interface
          with a Cluster. Search bea docs for Load-balancing Proxy.....
          Good Luck

Connecting client and web services with aqualogic

Hello, im engineer in training period at Unilog (Lyon,France) and im tesing aqualogic for evaluation
im nearly beginner in .NET and ESB and completely beginner in aqualogic, i have 1 problem :
i want to test communication between my .NET client and webservice, through Aqualogic.
i made some configuration but i wonder if its the right solution:
i created a proxy service with a pipeline pair node and a route node directed to registered business service.
But i dont know exactly how to connect my .NET client with aqualogic proxy service.
My client code is :
private void btnConnect_Click(object sender, System.EventArgs e)
Annu.Service1 oAnnu = new Annu.Service1();
oAnnu.Url = "http://localhost/WebService1/Service1.asmx";
string t = oAnnu.Tel("Dupont");
TextBox1.Text = t;
(this client code works without aqualogic, Annu is my Web reference to my web service)
Many thx again, cordially,
Pascal Camellini.
Message was edited by:
camellini

At the time of creating proxy service you should have filled endpoint url which is different from business service. Place the end point url of the proxy service in the client code url what you have written.
Follow the above step it will work properly

Aqualogic ESB Capabilities beyond web services ?

I'm new to Aqualogic 2.0 ESB and I'm exploring integration posibilities and scenarios where it will be useful.
I have some questions regarding limitations and interoperability with other:
- is there an overlap between ALSB 2.0 and WebLogic Integration?
- Is posible to integrate something like a back end system using CICS (ECI) and a client using web services via AquaLogic ? if so, How ?
- How can I use the underlying capabilities of the underlying WebLogic 9.0 server (i.e J2EE Connectors, jdbc pools, etc) from Aqualogic ?
- Can I publish an EJB remote interface running in another app. server as a "service" in Aqualogic 2.0
thanx in advance

I've only gone as far as reading high-level information and seeing some demos, but I think I can answer some of this.
Concerning the difference between ALSB and WLI, it's expected that WLI could be used to build a service that would be an ALSB endpoint. ALSB is a "no coding" interface. You simply define endpoints, transports, and routing rules. WLI is a development platform.
I'm not sure how to interpret the CICS question. Does your client have a web service invocation API? If so, then you could integrate that with ALSB.
To sort of answer the last two questions with a summary, if you can provide a web compatible interface to a component, then you can integrate it with ALSB. That interface could a web service or JMS. Depending on what version of things you're using, you can automatically provide a web service interface to an EJB session bean.

Aqualogic 5.7 - web services in a clustered environment

Similar Messages

Maybe you are looking for