Deploy a J2EE Web Services App in CE 7.1 SP1 SDN Preview

Hi,
I am new to SAP CE 7.1 SP1 (SDN Preview). I have a SAP J2EE (web services) application developed for SAP Netweaver 7.0.
How to deply the application in CE 7.1 SP1.
thanks in advance,
Nagarjuna.

Hi Nagarjuna,
the easiest way will be to use the Deployment perspective in NWDS. Just choose Window > Open Perspective > Other > Deployment.
If you have the application packages in a deployable archive (EAR, SCA, SDA, ...) in the file system, right-click External Deployable Archive and select Add. You can also choose archives to be deployed from the workspace.
If your application cannot be deployed or doesn't run properly, you might have to make some changes to it in order to port it from NW 7.0 to 71.
Other methods of deployment:
- There's a program called JSPM which is aimed primarily at non-development, admin users (the guys running the production system).
- There's a command-line deployment tool - have a look at <Install drive>\usr\sap\CE1\J00\j2ee\deployment\scripts.
Cheers,
Thorsten

Similar Messages

Deploying ADF BC as J2EE Web Service

I am attempting to deploy some ADF BC components (just the data model) as a J2EE web service. In the Application Module Editor I have selected the "Remoteable Application Module" and selected the "J2EE Web Service" option. Some of my public methods that I have exposed on the Client Interface (which return primitive types or serializable complex types) of the AM are placed into the WSDL of the web service. I would like to return a representation of one of the View objects and understand since the view itself is not a serializable type, I cannot return this directly. I created a public method on the Application Module that returns a RowSet (which I grabbed from the view) and it allows me to put that method on the Client interface but it does not show up in my web service. Is there anyway to directly return a representation of the view without manually retrieving the data and placing it in a custom class/bean that I return and then have to turn back into a view on the calling side?
Thanks for any help

Hi,
exposing a VO as a WebService will come a s a feature in JDeveloper 11. Until then you can only expose methods
Frank

JAX-RPC vs OC4J J2Ee web service

Hi,
Currently we use Oracle10G 10.0.3 developer preview edition. we deployed same web service on both JAX-RPC platfrom and OC4J J2EE web service platfrom (RPC encoding style). We found that old platform seems to perform better than JAx-RPC platfrom with regard to serialization and de-serialzation. We also did the test on Doc/literal style in JAX-RPC platfrom and its performance is not as good as the one deployed on old platform. We understand JAX-RPC is new implementation and Oracle10.0.3 is under developer preview edition and so it may not be optimized. We have following questions
1. Is this a known issue in JAX-RPC platform?
2. Is there anyway to optimize JAX-RPC web service? Like using different XMl parser (instead of Oracle XML parser)
3. When is the final release of 10.0.3 expected?
4. Will Oracle be supporting old web service platfrom (OC4J J2EE web service platform)? If so how long?
Thanks and regards
__Hari

Hi,
Currently we use Oracle10G 10.0.3 developer preview edition. we deployed same web service on both JAX-RPC platfrom and OC4J J2EE web service platfrom (RPC encoding style). We found that old platform seems to perform better than JAx-RPC platfrom with regard to serialization and de-serialzation. We also did the test on Doc/literal style in JAX-RPC platfrom and its performance is not as good as the one deployed on old platform. We understand JAX-RPC is new implementation and Oracle10.0.3 is under developer preview edition and so it may not be optimized. We have following questions
1. Is this a known issue in JAX-RPC platform?
2. Is there anyway to optimize JAX-RPC web service? Like using different XMl parser (instead of Oracle XML parser)
3. When is the final release of 10.0.3 expected?
4. Will Oracle be supporting old web service platfrom (OC4J J2EE web service platform)? If so how long?
Thanks and regards
__Hari

Error while returning complex data type in a J2EE web service

Hello,
I am implementing J2EE web service which returns array of custom class object.
I have implemented serializable interface to custom class, and also to session bean.
But it gives the following error:
Serializing object [Lcom.ltitl.j2ee.ejb.classes.ProjectDetails;@2a2289 fails. Nested message: XML Serialization Error. Object of Class [com.ltitl.j2ee.ejb.classes.ProjectDetails] does not have property [ObjId] of type [java.lang.Integer]. Check if the right object is passed to the serialization routine..
As error stated about some property ObjId..I tried including such property in my class. But now it gave exception while deploying stating that ObjId already defined.
Also I want to return multiple arrays of complex custom classes. i tried using vectors but didnt work. What is the method to return arrays of complex custom classes.
Please help..
Abhijeet

Trying to create a web service that returns a Collection doesn't seem to be possible in Netweaver. The reason for this is that languages other than Java have difficulty in mapping Collections, amongst others, to their own native equivalents.
There is a discussion on the subject here you may find useful:
http://forum.capescience.com/showthreaded.php?Cat=&Board=webservices&Number=147&page=0&view=collapsed&sb=5&o=&vc=1
The short answer is to use object Arrays instead, or a custom class that contains an array of each type of object you would expect to find in your Vector
Hope this helps
Steve

NullPointerException in Create J2EE Web Service Wizard

I created an EJB2.1 session bean that has a method which returns an user defined class and also throws user defined exception. I tried to use the Create J2EE Web Service and chose to use RPC/Encoded scheme.
The WSDL and java-wsdl mapping files were generated, but I got the following messages and exception. The webservices.xml and oracle-webservices.xml were not generated and wizard did not finish. Any ideas why would this happen?
Web Service Log :
Generating WSDL and mapping file
Generating deployment descriptors
ERROR: [failed to localize] Unable to find member message in jax-rpc mapping metadata for the exception whose wsdl message is: {http://mypackage/}MyException
Exception dialog :
java.lang.NullPointerException
     at oracle.j2ee.ws.tools.wsa.Util.createDeploymentDescriptors(Util.java:482)
     at oracle.j2ee.ws.tools.wsa.Util.createDeploymentDescriptors(Util.java:759)
     at oracle.jdeveloper.webservices.model.Generator.generateDDFiles(Generator.java:734)
     at oracle.jdeveloper.webservices.model.java.BaseJavaGenerator.doGeneration(BaseJavaGenerator.java:173)
     at oracle.jdeveloper.webservices.model.Generator.generateImpl(Generator.java:447)
     at oracle.jdeveloper.webservices.model.Generator.generate(Generator.java:295)
     at oracle.jdeveloper.webservices.model.WebService.saveEditImpl(WebService.java:3971)
     at oracle.jdeveloper.webservices.model.WebService.mav$saveEditImpl(WebService.java)
     at oracle.jdeveloper.webservices.model.WebService$1.run(WebService.java:3817)
     at oracle.jdeveloper.webservices.model.GeneratorUI$GeneratorAction.run(GeneratorUI.java:446)
     at oracle.ide.dialogs.ProgressBar.run(ProgressBar.java:551)
     at java.lang.Thread.run(Thread.java:595)

Specifically, this happens only when there is an exception thrown from the session bean method.

How to create stub for C++ client to invoke a j2ee web service

Hi All,
I have developed a j2ee web service which is deployed in Tomcat. I have to call this service from C++ client. I have followed "Axis C++ Client User's Guide" to create stub for my service. I am running WSDL2Ws tool with command
D:\axisserver\axis-c-win\wsdls>java -cp %AXISCLASSPATH_C%; org.apache.axis.wsdl.wsdl2ws.WSDL2Ws Calculator.wsdl -lc++ -sclient. While running this WSDL2Ws tool , it is giving error.
Exception Stack is as follows.
Exception in thread "main" java.lang.NoSuchMethodError
at org.apache.axis.wsdl.wsdl2ws.info.Type.<init>(Unknown Source)
at org.apache.axis.wsdl.wsdl2ws.info.TypeMap.getType(Unknown Source)
at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.createParameterInfo(Unknown Source)
at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.addRPCStyleInputMessageToMethodInfo(Unknown Source)
at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.setMethodInfo(Unknown Source)
at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.getServiceInfo(Unknown Source)
at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.generateWrappers(Unknown Source)
at org.apache.axis.wsdl.wsdl2ws.WSDL2Ws.main(Unknown Source)
Anybody can suggest me what i missed...
Thanks in advance...

Hi all,
I have solved this issue. I had JDK1.3 by default. So it was giving error. When i use java from jdk1.4, it created stubs for web service. Java version was the problem. Now it is working fine.
Thanks....

J2EE Web services and JAX-RPC

Hello..
While working with J2EE web services using JDeveloper and OC4J, I noticed that it really doesn't confirm to Sun's JAX-RPC standard. The Web Service interface class does not extend the "Remote" and all methods don't throw "RemoteException" as mandated by JAX-RPC standard.
I have few questions:
(1) Are the OC4J J2EE web services completey different from JAX-RPC based web services.??
(2) Does Oracle have any implementation of JAX-RPC??
(3) Is Sun the only one promoting and implementing the JAX-RPC standard? Or are there other players?
thanks...

(1) Are the OC4J J2EE web services completey different from JAX-RPC based web services.??
OC4J J2EE Web Services originate from Oracle/Apache SOAP with several differences:
a. A model where each type of implementation gets a specific servlet (e.g. one for EJB's, one for PL/SQL, one for stateless and stateful Java classes. Architecturally, you can see the picture here:
http://otn.oracle.com/docs/products/ias/doc_library/903doc_otn/generic.903/b10004/orawebservices.htm#1024808
(scroll down a half page for the picture)
b. The packaging of the Web services rather than using the Apache SOAP registration mechanism uses something closer to JSR 109 (also known as Web Services for J2EE, part of J2EE 1.4 with JAX-RPC, SAAJ [SOAP API forAttachments in Java] and JAXP [Java API for XML Parsing]), where the Web service is packaged as an ordinary ear file for deployment.
Oracle built this implementation by extrapolating from the JAX-RPC documentation that was available last year before it was a final specification in an effort to release a production quality Web services implementation that was aligned with JAX-RPC. It has been through two releases - Oracle9iAS 9.02 and Oracle9iAS 9.0.3 and is now being evolved to JAX-RPC as we move to J2EE 1.4.
(2) Does Oracle have any implementation of JAX-RPC??
We are planning to release a JAX-RPC implementation in the new year (I don't have specific dates yet) on OC4J. The production implementation of this will be as seamless a migration as possible from the existing implementation. Oracle9i JDeveloper will also add support for JAX-RPC as a 3rd option in its list of choices available. You can get a sense of how such a migration would work by running the Web services wizard in JDev for Apache SOAP and then, in a separate project, running it for Oracle9iAS J2EE Web Services - imagine there being another option for JAX-RPC. The work to migrate should be as simple as running a wizard or command line utility (known as the Web Services Assembler tool in Oracle9iAS).
(3) Is Sun the only one promoting and implementing the JAX-RPC standard? Or are there other players?
Pretty much every one in the Java side of industry will be implementing JAX-RPC. The important time to note is when J2EE 1.4 is released ... sometime in the new year ... I believe around March but may be mistaken. Part of J2EE 1.4 is required support for JAX-RPC, SAAJ, Web Services for J2EE etc etc. This will standardize the implementation of Web services. Oracle, like others in the industry, supports the standard protocols, (SOAP), interfaces (WSDL) and registries (UDDI) - what J2EE 1.4 does is standardize the packaging, deployment and implementation (the wrappers generated by the tooling).
My guess is that around JavaOne (June 2003) there will be a rash of announcements from J2EE vendors announcing support of JAX-RPC and J2EE 1.4 (or early implementations) as we will be in the same race that happened in 2001/2002 when J2EE 1.3 was the spec to announce implementations around.
Mike.

Timeout error at J2EE Web Service client

i have a .NET web service. a J2EE web service client deployed on Websphere application server 5.1 is invoking it. some services on .NET end take a long time to return a value. in such cases, the following error occurs on J2EE end. please suggest a solution.
faultCode: Server.generalException
faultString: java.net.SocketTimeoutException: Read timed out
faultActor: null
faultDetail:
java.net.SocketTimeoutException: Read timed out
at com.ibm.ws.webservices.engine.WebServicesFault.makeFault(WebServicesFault.java:150)
at com.ibm.ws.webservices.engine.transport.http.HTTPSender.invoke(HTTPSender.java:200)
at com.ibm.ws.webservices.engine.PivotHandlerWrapper.invoke(PivotHandlerWrapper.java:212)
at com.ibm.ws.webservices.engine.WebServicesEngine.invoke(WebServicesEngine.java:255)
at com.ibm.ws.webservices.engine.client.Connection.invokeEngine(Connection.java:685)
at com.ibm.ws.webservices.engine.client.Connection.invoke(Connection.java:611)
at com.ibm.ws.webservices.engine.client.Connection.invoke(Connection.java:441)
at com.ibm.ws.webservices.engine.client.Stub$Invoke.invoke(Stub.java:662)

Hi, am also getting time out .. excepiton in client
i added the following code inside stub class constructer...
System.out.println("GET TIME OUT ::::"+super.getTimeout());
super.setTimeout(77777);
System.out.println("GET TIME OUT AFTER SET::"+super.getTimeout());
compilation success. However am getting runtime exception after the sop.
GET TIME OUT ::::0
javax.xml.rpc.ServiceException: WSWS5014E: Error instantiating generated Stub class.
can you please tell me how u solved the issue.
Thanks
Bogi

Error deploying custom java web service -Jdeveloper11.1.1.3.0

Hi all,
Error deploying custom java web service in - Jdeveloper 11.1.1.3.0
Weblogic Server Exception: weblogic.deploy.api.internal.utils.DeployerHelperException: The source 'C:\DOCUME~1\.......\LOCALS~1\Temp\.xyz..........Project-context-root.war'
for the application 'xyz....Project-context-root' could not be loaded to the server 'http://hostname:port/bea_wls_deployment_internal/DeploymentService'.
Server returned HTTP response code: 409 for URL: http://hostname:port/bea_wls_deployment_internal/DeploymentService
See server logs or server console for more details.
weblogic.deploy.api.spi.exceptions.ServerConnectionException: [J2EE Deployment SPI:260041]Unable to upload 'C:\JDeveloper\mywork\MyApllicationName\Project\deploy\xyz........Project-context-root.war' to 't3://hostname:port'
#### Deployment incomplete. ####
Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
Thanks
Edited by: soauser on Sep 3, 2010 8:55 AM

Any help for the above post is appreciated..
Edited by: soauser on Sep 3, 2010 11:58 PM

Error deploying custom java web service in SOA11g-Jdeveloper 11.1.1.3.0

Hi all,
I am getting Error deploying custom java web service in SOA 11G- Jdeveloper 11.1.1.3.0
Weblogic Server Exception: weblogic.deploy.api.internal.utils.DeployerHelperException: The source 'C:\DOCUME~1\.......\LOCALS~1\Temp\.xyz..........Project-context-root.war'
for the application 'xyz....Project-context-root' could not be loaded to the server 'http://hostname:port/bea_wls_deployment_internal/DeploymentService'.
Server returned HTTP response code: 409 for URL: http://hostname:port/bea_wls_deployment_internal/DeploymentService
See server logs or server console for more details.
weblogic.deploy.api.spi.exceptions.ServerConnectionException: [J2EE Deployment SPI:260041]Unable to upload 'C:\JDeveloper\mywork\MyApllicationName\Project\deploy\xyz........Project-context-root.war' to 't3://hostname:port'
#### Deployment incomplete. ####
Remote deployment failed (oracle.jdevimpl.deploy.common.Jsr88RemoteDeployer)
Edited by: soauser on Sep 3, 2010 7:44 AM
Edited by: soauser on Sep 3, 2010 7:45 AM
Edited by: soauser on Sep 3, 2010 7:46 AM

Any help for the above post is appreciated..
Edited by: soauser on Sep 3, 2010 11:58 PM

How to deploy my own web services to the Start BPEL PM Server?

Recently, I am learning the JDeveloper BPEL Designer(version 10.1.2.0), I had finished my first BPEL process CreditFlow flowing the quickstart guider.
Now I wonder how to deploy my own web services to the Start BPEL PM Server? I mean I don't want to invoke the CreditRatingService as I did flowing the quickstart guider, but to invoke my own web servcies. Now I had made some web services with eclipse and deployed them to the tomcat5.0. but how can I invoke these my own web services just like I invoked the CreditRatingService in the JDeveloper BPEL Designer?
Thank you!

Copy the WSDL file from your Tomcat server onto your development machine. Add them to your project in JDeveloper. Then add a partnerlink and specify the WSDL location. Then add you role, variables and compile!

How to deploy business objects web services on tomcat

Hi everyone can anyone tell how i need to deploy business objects web services on tomcat, i installed business objects on unix server.what r the steps i need to follow in order to deploy web services on business objects. this web services must be called by a java program externally, that the reason i am deploying web services.
i downloaded business objects web services portal sample zip file. the wssdkj2eeportal directory is created with ant_scripts,src, dsws.config and wsportalassemblyscripts.bat.
i am trying to configure the dsws.config, by modifying it to
<configuration version="1.0">
   <WebService Name="BusinessObjects Enterprise XI 3.1 sp3" Icon="image/java.gif">
      XI 3.1 Web Services
      <Connection URL="http://169.111.33.61:8080/dswsbobje/services/session" Proxy="0" Timeout="120000" />
   </WebService>
   <Proxy Name="Outside" URL="http://http-cache.mycompany.com:3667" />
</configuration>
what i need to do in order to deploy
i am using bo xi 3.1 sp3

Hi,
You deploy all the web applications provided by BOE with the use of Wdeploy tool installed with BOE installation, for details please reffer the following document
[BusinessObjects Enterprise XI 3.1 Web Application Deployment Guide for UNIX*|http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000715844%26_SCENARIO=01100035870000000202]
Regards,
Ramu.
Edited by: Gowda Timma Ramu on Nov 9, 2010 8:39 PM

Can we deploy a java web service on OC4J within EBS 12.1.3

Hi,
I needed some instructions if this is possible to deploy a java web service on OC4J in EBS 12.1.3.
We don't have SOA gateway integration. The web service is simple SOAP web service.
Is there any document that can be referred for this ?
Thanks

I would try a number of things:
1) Try generating the web service artifacts by using the web service assembler tool that comes with oc4j 10.1.3 dp3. You can use either the command line or ant assembly tasks that are available with the download. There are some fairly detailed examples of using the ant tasks for web service generation at http://www.oracle.com/technology/tech/java/oc4j/1013/howtos/index.html (under the "web services" heading).
2) Try deploying the generated ear file using the admin console. I believe that should work.
3) If for some reason that doesn't work you can try to use the deployment ant tasks (also detailed in the how to examples).
I believe the reason you did not deploy successfully is that even though the core service implementation class, SEI, and JAX-RPC descriptor are portable the artifacts generated in order to deploy the service to a particular application server are unique. JWSDP is tailored to the sun platform.
Hope that helps.
-- Jon

Deploy J2EE Web Service with otherwise than SUN1AS

Right now i have a webservice up and running on a Sun1 that comes with J2EE1.4 tutorial.
But if i try to deploy the war to other AS (say OC4J), saving the web.xml transformed to 2.3, the call to this WS fails because it says the Servlet is not a Servlet (wich is quite right). So, what is going on?
Can't I deploy a WAR containing a WS generated with deploytool to other AS?
Thanks and thanks again,
Mariano.

Things I've learnt these days.
1-) J2EE is still too new for many Application Servers.
2-) Developing web services is a tough, long way to go.
I finally realized war's containing web services are not that portable at all.
I had to download Jdev's 10g preview in order to deploy 1 miserable JAX-RPC web service in OC4J.
And I still can't return a java.util.HashMap in the service's response...not to mention trying to add its mapping in JDev's web service creating process...
So, hold still gentleman, for it's rough.
Thanks,
Mariano.

Creating And Deploying A JWSDP Web Service Client to Weblogic 8.1

This setup produces an EAR containing a message driven bean in a jar file. When the MDB receives a message
it checks to see if there is any data in a database table and if so calls the web service with that data. These instructions
are for MS-Windows environments.
In my setup I have:
the weblogic domain at c:\b2b80
the jwsdp at c:\apps\jwsdp-1.3
extra jar files for the app server in c:\b2b80\lib
the main weblogic installation at c:\apps\weblogic810\
1> Download the the JWSDP version you wish to use and install it. (In this example I'm using 1.3)
2> Create a project structure for you client like this:
     /project
          /earbuild
               /META-INF
          /ejbbuild
               /META-INF
          /ejbsource
          /wssource
3> in the /project directory you will need a build.xml file that looks something like this: (the ant build targets are described at the end of this document)
==============================================================
<?xml version="1.0"?>
<project name="svcowner" default="buildall" basedir=".">
     <property file="classpath.settings"/>
     <property name="wssource" value="wssource"/>
     <property name="ejbsource" value="ejbsource"/>
     <property name="compileejbdest" value="ejbbuild"/>
     <property name="earbuilddest" value="earbuild"/>
     <property name="jarfilename" value="svcownerejb.jar"/>
     <property name="earfilename" value="svcowner.ear"/>
     <property name="debug" value="true"/>
     <property name="deprecation" value="true"/>
     
     <target name="cmdline_wscompile">
          <exec executable="wssource/create.bat"/>
     </target>
     <target name="compileejb" depends="cmdline_wscompile">
          <javac debug="${debug}" srcdir="${wssource}" classpath="${BUILD_CLASSPATH}"
               destdir="${compileejbdest}" includes="**/*.java" deprecation="${deprecation}"/>
          <javac debug="${debug}" srcdir="${ejbsource}" classpath="${BUILD_CLASSPATH}"
               destdir="${compileejbdest}" includes="**/*.java" deprecation="${deprecation}"/>
     </target>
     <target name="buildejbjar" depends="compileejb">
          <jar jarfile="${earbuilddest}/${jarfilename}" manifest="${compileejbdest}/META-INF/MANIFEST.txt">
               <fileset dir="${compileejbdest}">
                    <include name="**/*.*"/>
               </fileset>
          </jar>
     </target>
     <target name="buildear" depends="buildejbjar">
          <jar jarfile="${earfilename}">
               <fileset dir="${earbuilddest}">
                    <include name="**/*.*"/>
               </fileset>
          </jar>
     </target>
     <target name="deploy">
          <copy file="${earfilename}" todir="../../config/domain/applications"/>
     </target>
     <target name="buildall" description="build everything" depends="buildear, deploy">
     </target>
</project>
==============================================================
4> You need a matching classpath.settings file in the same directory, something like this:
==============================================================
BUILD_CLASSPATH=/b2b80/lib/saaj-impl.jar;/b2b80/lib/saaj-api.jar;/b2b80/lib/jaxrpc-api.jar;/b2b80/lib/jaxrpc-impl.jar;c:/b2b80/lib/jaxrpc-spi.jar/b2b80/classes/;/b2b80/classes;/apps/weblogic810/server/lib/weblogic.jar;/apps/weblogic810/server/lib/weblogic_sp.jar;/apps/weblogic810/server/lib/xmlx.jar;/apps/weblogic810/server/ext/weblogic-tags.jar;/apps/weblogic810/server/ext/jdbc/oracle/920/ojdbc14_g.jar;/b2b80/lib/log4j.jar
==============================================================
5> In the /project/earbuild/META-INF directory you need an application.xml file:
==============================================================
<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE application PUBLIC '-//Sun Microsystems, Inc.//DTD J2EE Application 1.2//EN' 'http://java.sun.com/j2ee/dtds/application_1_2.dtd'>
<application>
<display-name>svcownerb2b</display-name>
<description>Application description</description>
<module>
<ejb>svcownerejb.jar</ejb>
</module>
</application>
==============================================================
6> The /project/ejbsource directory contains the source for the client application. In my case this is a message driven bean (note that code below isn't complete). The most important part of the code below is the setting of the javax.xml.soap.MessageFactory system property.
System.getProperties().put("javax.xml.soap.MessageFactory","com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl");
If you don't do this a weblogic class will be used and the code will fail.
==============================================================
package com.svcclient.ejb.svcownershipment;
import java.text.*;
import java.io.*;
import java.sql.*;
import java.util.Properties;
import javax.ejb.*;
import javax.jms.*;
import javax.naming.*;
import javax.sql.DataSource;
import com.svcclient.util.*;
import org.w3c.dom.*;
import com.svcclient.websvc.svcowner.*;
import javax.xml.rpc.Stub;
public class SvcOwnerShipmentSubscriberMDB implements MessageDrivenBean, MessageListener
private transient MessageDrivenContext mdc = null;
private static Context context;
private final static String CLASSNAME = "SvcOwnerShipmentSubscriberMDB";
private String DATASOURCE_JNDI = "svcclient.b2b";
private static DataSource mDS = null;
private SimpleDateFormat dateFormat = new SimpleDateFormat("yyyy-MM-dd");
public SvcOwnerShipmentSubscriberMDB()
System.getProperties().put("javax.xml.soap.MessageFactory","com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl");
try
if (context == null)
context = new InitialContext() ;
if (mDS == null)
mDS = (DataSource)context.lookup(DATASOURCE_JNDI);
catch (NamingException ex)
ex.printStackTrace();
catch(Exception ex)
ex.printStackTrace();
public void onMessage(javax.jms.Message message)
TextMessage msg = null;
String ordernumber = null;
String lineid = null;
try
if (message instanceof TextMessage)
msg = (TextMessage) message;
ordernumber = msg.getStringProperty("ordernumber");
               // the JMS message contains a property that is an order number
createAndSendXML(ordernumber);
catch (Throwable ex)
ex.printStackTrace();
private void createAndSendXML(String ordernumber)
if(ordernumber==null)
return;
PreparedStatement statement = null;
ResultSet rset = null;
java.sql.Connection conn = null;
try
conn = DBHelper.getConnection(mDS,"SvcOwnerShipmentSubscriberMDB.createAndSendXML");
statement = conn.prepareStatement("select * from ..."); // you SQL here
statement.setString(1,ordernumber);
rset = statement.executeQuery();
StringBuffer data = new StringBuffer();
data.append("<? version=\"1.0\"?>\n");
data.append("<shippingRequest>\n");
while(rset.next())
data.append("\t<order_date>"+dateFormat.format(new java.util.Date(rset.getTimestamp("SCHEDULE_SHIP_DATE").getDate()))+"</order_date>\n");
data.append("\t<brand_name>svcclient</brand_name>\n");
data.append("\t<shipRequestType>Sale</shipRequestType>\n");
data.append("</shippingRequest>\n");
          // call the web service with the data from the database
DataExchanger_Impl impl = new DataExchanger_Impl();
Stub stub = (Stub)(impl.getDataExchangerSoap());
DataExchangerSoap dx = (DataExchangerSoap)stub;
String resp = dx.exchangeData("svcclient", "mypassword", "Sales", data.toString());
catch(SQLException sqle)
sqle.printStackTrace();
catch(Exception e)
e.printStackTrace();
finally
try
if (rset != null)
rset.close();
if (statement != null)
statement.close();
if (conn != null)
conn.close();
catch(Exception x){}
public void ejbCreate() { System.out.println("In SvcOwnerShipmentSubscriberMDB.ejbCreate()"); }
public void setMessageDrivenContext(MessageDrivenContext mdc) { this.mdc = mdc; }
public void ejbRemove() throws javax.ejb.EJBException { System.out.println("In SvcOwnerShipmentSubscriberMDB.remove()"); }
==============================================================
7> The /project/ejbbuild/META-INF directory needs a MANIFEST.txt file.
Manifest-Version: 1.0
8> The /project/ejbbuild/META-INF directory needs a ejb-jar.xml file. This just sets up the MDB which is the client.
==============================================================
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC '-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN' 'http://java.sun.com/dtd/ejb-jar_2_0.dtd'>
<ejb-jar>
<display-name>SvcOwnerShipmentSubscriberMDB</display-name>
<enterprise-beans>
<message-driven>
<display-name>SvcOwnerShipmentSubscriberMDB</display-name>
<ejb-name>SvcOwnerShipmentSubscriberMDB</ejb-name>
<ejb-class>com.svcclient.ejb.svcownershipment.SvcOwnerShipmentSubscriberMDB</ejb-class>
<transaction-type>Container</transaction-type>
<message-driven-destination>
<destination-type>javax.jms.Topic</destination-type>
<subscription-durability>NonDurable</subscription-durability>
</message-driven-destination>
</message-driven>
</enterprise-beans>
<assembly-descriptor>
<container-transaction>
<method>
<ejb-name>SvcOwnerShipmentSubscriberMDB</ejb-name>
<method-name>onMessage</method-name>
<method-params>
<method-param>javax.jms.Message</method-param>
</method-params>
</method>
<trans-attribute>NotSupported</trans-attribute>
</container-transaction>
</assembly-descriptor>
</ejb-jar>
==============================================================
9> The /project/ejbbuild/META-INF directory needs a weblogic-ejb-jar.xml file.
==============================================================
<?xml version="1.0"?>
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN" "http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd">
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>SvcOwnerShipmentSubscriberMDB</ejb-name>
<message-driven-descriptor>
<pool>
<max-beans-in-free-pool>5</max-beans-in-free-pool>
<initial-beans-in-free-pool>1</initial-beans-in-free-pool>
</pool>

<destination-jndi-name>jms.svcownerShipmentsTopic</destination-jndi-name>
</message-driven-descriptor>
</weblogic-enterprise-bean>
</weblogic-ejb-jar>
==============================================================
10> The /project/wssource directory needs a dataexchange.wsdl file. This is the WSDL describing the web service
we want to connect to with our client.
==============================================================
<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:tns="https://www.svcowner.com/mfg/DataExchange/"
xmlns:s="http://www.w3.org/2001/XMLSchema"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:http="http://schemas.xmlsoap.org/wsdl/http/"
targetNamespace="https://www.svcowner.com/mfg/DataExchange/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
name="">
<wsdl:types>
<s:schema elementFormDefault="qualified"
targetNamespace="https://www.svcowner.com/mfg/DataExchange/">
<s:element name="exchangeData">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="sender" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="password" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="transactionType" type="s:string" />
<s:element minOccurs="0" maxOccurs="1" name="data" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
<s:element name="exchangeDataResponse">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="exchangeDataResult" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
</s:schema>
</wsdl:types>
<wsdl:message name="exchangeDataSoapIn">
<wsdl:part name="parameters" element="tns:exchangeData" />
</wsdl:message>
<wsdl:message name="exchangeDataSoapOut">
<wsdl:part name="parameters" element="tns:exchangeDataResponse" />
</wsdl:message>
<wsdl:portType name="DataExchangerSoap">
<wsdl:operation name="exchangeData">
<wsdl:input message="tns:exchangeDataSoapIn" />
<wsdl:output message="tns:exchangeDataSoapOut" />
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="DataExchangerSoap" type="tns:DataExchangerSoap">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" />
<wsdl:operation name="exchangeData">
<soap:operation soapAction="https://www.svcowner.com/mfg/DataExchange/exchangeData"
style="document" />
<wsdl:input>
<soap:body use="literal" />
</wsdl:input>
<wsdl:output>
<soap:body use="literal" />
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="DataExchanger">
<wsdl:port name="DataExchangerSoap" binding="tns:DataExchangerSoap">
<soap:address location="https://svc.svcowner.com/mfg/dataexchange.php" />
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
==============================================================
10> The /project/wssource directory needs a websvc_config.xml file. This file tells wscompile where
to find the WSDL file and the package name for the generated classes.
==============================================================
<?xml version="1.0" encoding="UTF-8"?>
<configuration xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
     <wsdl location="wssource/dataexchange.wsdl" packageName="com.svcclient.websvc.svcowner"/>
</configuration>
==============================================================
11> The /project/wssource directory needs a create.bat file. This just sets up the environment
and calls the wscompile batch file in the JWSDP. I had to tweak the wscompile.bat file to match
my environment as well.
==============================================================
SETLOCAL
SET WSDP=C:\apps\jwsdp-1.3\
SET ANT_HOME=%WSDP%;apache-ant
SET PATH=%ANT_HOME%\bin;%WSDP%jaxrpc\bin;%PATH%
SET JAVA_HOME=c:\apps\weblogic810\jrockit81sp2_141_05
call wscompile -gen:client -s ./wssource -keep -g -d ejbbuild wssource/websvc_config.xml
==============================================================
12> The /project directory needs a build.bat file. Just a way for me to make sure my
environment is set up right before doing the build.
==============================================================
SETLOCAL
SET ANT_HOME=c:\apps\jakarta-ant-1.4.1
SET PATH=%ANT_HOME%\bin;%PATH%
SET JAVA_HOME=c:\apps\weblogic810\jrockit81sp2_141_05
call ant -buildfile build.xml %1 %2 %3 %4 %5 %6 %7 %8 %9
==============================================================
13> You need to copy the following jar files from the JWSDP into a location they can be used by the
app server during run time and also for the build process. In my set up this is c:\b2b80\lib. Note that
these are pointed to by the file in step 4.
c:\apps\jwsdp-1.3\jaxrpc\lib\jaxrpc-api.jar
c:\apps\jwsdp-1.3\jaxrpc\lib\jaxrpc-impl.jar
c:\apps\jwsdp-1.3\jaxrpc\lib\jaxrpc-spi.jar
c:\apps\jwsdp-1.3\saaj\lib\saaj-api.jar
c:\apps\jwsdp-1.3\saaj\lib\saaj-impl.jar
14> You must make sure that the jar file in step 13 are at the front of the classpath for the
weblogic server. WL comes with classes that conflict with these jars.
15> I also had to add the root ssl certificate from the partners certificate authority to the java keystore
using the keytool because this service uses SSL:
C:\apps\weblogic810\jrockit81sp2_141_05\jre\bin>keytool -import -keystore ..\lib\security\cacerts -alias svcownerroot -keypass password -file c:\temp\svcownerroot.cer
==============================================================
So the idea is this, you run the /project/build.bat file from within the /project directory. This
calls ant which uses the build.xml file to create everything and copy the EAR to the weblogic deployment
directory. The default ant target is buildall.
The cmdline_wscompile target runs the /project/wssource/create.bat file which in turn runs the wscompile.bat
file from the jwsdp. This causes the dataexchange.wsdl file to processed and the client files to be generated.
The generated java files go into the /project/wssource directory. The generated class files go into the
/project/ejbbuild directory. They need to be there so the MDB can use them.
Next the compileejb ant target compiles the MDB java file and places the resulting class file into the
/project/ejbbuild directory.
Next the buildejbjar ant target takes everything in the /project/ejbbuild directory and creates the ejb jar
file that will be included in the EAR. This file is placed in the /project/earbuild directory.
Finally the buildear ant target takes everything in the /project/ejbbuild directory and produces the EAR
file for deployment. The EAR file is placed in the /project directory.
The deploy task simply copies the EAR file into the weblogic domain applications directory.

It's really the web service that determines what kind of authentication is required. You can't just use any old strategy. If the web service isn't expecting it in that form, it won't work. Typically, either HTTP BASIC Auth or WS-Security is used. You'd have to contact the people responsible for the web service to know what kind of auth it requires.

Deploy a J2EE Web Services App in CE 7.1 SP1 SDN Preview

Similar Messages

Maybe you are looking for