Create ear and deploy aqualogic process

Hi all,
I'm just starting to use Aqualogic BPM. I've installed Weblogic 9.2 too in my computer.
I've do the helloworld example process, but i don't know how can i create the ear o war file and deploy it in weblogic, and if i have or not to do something inside the process to do this.
thanks to all.

To create a EAR file in JDeveloper, select the project node and choose NEW from the context menu.
In the NEW gallery select "Deployment Profiles" and choose EAR from the list.
Deployment:
- Create a connection in Oracle JDeveloper to OC4J and deploy directly
- Use java -jar admin.jar .... in OC4J 10.1.2
- Use Oracle Enterprise Manager Console with OC4J 10.1.3
Please have a look at the OC4J documentation on OTN that is available online and for download as part of the Oracle Application Server documentation
Frank

Similar Messages

  • How to create SAR and deploy in OCCAS

    Is there any eclipse plugin for occas server or How occas server can be handled from eclipse?

    To create a EAR file in JDeveloper, select the project node and choose NEW from the context menu.
    In the NEW gallery select "Deployment Profiles" and choose EAR from the list.
    Deployment:
    - Create a connection in Oracle JDeveloper to OC4J and deploy directly
    - Use java -jar admin.jar .... in OC4J 10.1.2
    - Use Oracle Enterprise Manager Console with OC4J 10.1.3
    Please have a look at the OC4J documentation on OTN that is available online and for download as part of the Oracle Application Server documentation
    Frank

  • Create Webservice and deploy

    Dear Gurus,
    I had followed the below steps in creating webservices using ABAP.
    1. Create Package
    2. Create Function group
    3. Create RFC function module
    4. Create webservice from the function module
    5. Create service definition, select port profie and deploy service and assign to Package and transport request
    6. Executed SOAMANAGER transaction , it opens a webpage with internet explorer defaul web page and I dont see any SOA administration related information and I dont have any clue how to proceed further.
    Please let me know if I there is any prerequisities Like SP to be installed, or any configuration / settings needs to be done.
    I am workign in SAP ECC 6.0 (SAP version 700)
    Thanks in advance.
    Thanks
    Shanthi

    Hello,
    In Web Service hierarchy transaction SICF, node APPL_SOAP_MANAGEMENT should be active. The complete path is default_host/sap/bc/webdynpro/sap/APPL_SOAP_MANAGEMENT.
    Once you are in the SOA Management screen, select single service adminstration and select your service and create End Point there.
    Thanks,
    Venu

  • Create webservices and deploy

    Dear Gurus,
    I had followed the below steps in creating webservices using ABAP.
    1. Create Package
    2. Create Function group
    3. Create RFC function module
    4. Create webservice from the function module
    5. Create service definition, select port profie and deploy service and assign to Package and transport request
    6. Executed SOAMANAGER transaction , it opens  a webpage with internet explorer defaul web page and I dont see any SOA administration related information and I dont have any clue how to proceed further.
    Please let me know if I there is any prerequisities Like SP to be installed, or any configuration / settings needs to be done.
    I am workign in SAP ECC 6.0 (SAP version 700)
    Thanks in advance.
    Thanks
    Shanthi

    Hi,
    The steps are
    1. In start menu --> Run --> type Drivers and press enter
    2. In that select the folder etc
    3. Then open the file hosts in notepad
    4. In the hosts file add your server ip and the domain name and save it.
    5. Then in internet explorer click tools --> internet options --> connections --> lan settings ---> advanced and add the domain there also.
    it will work fine
          For this get the assist from your system Admin.

  • Create jar and deploy to server

    Hi ,
    could some one clear my doubts..
    Core java:
    1. created a simple java project , now how do i jar them and deploy them into a server .. how do i run my project from the server.
    Please explain the steps..
    J2EE:
    Above steps if it is on j2ee environment.
    Thanks

    If the jar that you have created is going to be used in J2EE application there are few options available:
    1. Add this to WEB-INF/lib folder so that it becomes part of your application
    2. If you are using Apache Tomcat and you want your jar file to be accessed by all applications that you run on same server add that jar file to:
    <Drive>apache-tomcat-5.5.27\shared\lib
    3. If you are using any IDE and you need this for testing purpose only add this to your classpath

  • Creating ear and war file from deploy file programatically

    Hi All,
    Is there any API available in oc4j to create an ear or war file from a .deploy file...........??
    Thanx in advance.

    There isn't a public API that let's you hook up to the deploy file in JDeveloper.
    You might be able to achieve this with the JDeveloper Ant task:
    http://www.oracle.com/technology/products/jdev/htdocs/partners/addins/exchange/anttasks/index.html

  • How to create Websevice and deploy on Server using Oracle SOA 10g ?

    Is that possible to create WSDL without BPEL process ? How to do this ?? And how to deploy it ??
    Edited by: user11180835 on Aug 21, 2011 8:18 AM

    Create a java Class with your code and expose it as a web service in JDeveloper it self.
    Go to Resources folder-you will find webservices.deploy-right click on it deploy to your application server.
    Use the url provided at the end of the WSDL file to access this Webservice.
    Incase of deploying this webservice on some other environment-take the .ear file and upload in the application tab and then do deployment.
    Thanks,
    Chandra_

  • How to create and deploy a simple jstl applicaton in weblogic 10.3.3

    How to create and deploy a simple jstl applicaton in weblogic 10.3.3

    1) Since JSTL libraries are provided as Web application libraries, they must be deployed before the Web application that is using JSTL functionality is deployed. The libraries can be deployed using the Administration Console or with the command-line weblogic.Deployer tool.
    Here’s an example of deploying a JSTL 1.2 library using the weblogic.Deployer command-line:
    java weblogic.Deployer -adminurl t3://localhost:7001
    -user weblogic -password weblogic
    -deploy -library
    d:/beahome/wlserver_10.3/common/deployable-libraries/jstl-1.2.war
    This command deploys the JSTL 1.2 library using the default library-name, specification-version and implementation-version defined by the MANIFEST.MF in the library.
    After a library is deployed, the extension-name, specification-version and implementation-version of the library can be found in Administration console. This information can also be found in the MANIFEST.MF file of the library WAR file.
    For more information on deploying a Web module refer below URL
    http://docs.oracle.com/cd/E15051_01/wls/docs103/deployment/deployunits.html
    2) To reference a JSF or JSTL library, a standard web application can define a <library-ref> descriptor in the application’s weblogic.xml file. Here is an example:
    <library-ref>
    <library-name>jsf</library-name>
    <specification-version>1.2</specification-version>
    <implementation-version>1.2.0</implementation-version>
    <exact-match>false</exact-match>
    </library-ref>
    For more information on referencing a Web application library refer below URL
    http://docs.oracle.com/cd/E15051_01/wls/docs103/programming/libraries.html
    3) Create a sample JSP in your application and JSP should look as shown below
    <%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %>
    <html>
    <head>
    <title>TestJSTL</title>
    </head>
    <body>
    <c:set var="topic" value="JSTL" />     
    <c:out value="${topic}" />
    </body>
    </html>
    4) Create WAR and deploy and test.
    Edited by: Murali Veligeti on Jul 26, 2012 9:00 AM

  • BAM Data Source and deployment setting in weblogic

    like In db adapter we need to create datasource and deployment plan in weblogic. what I want to know is this same process is valid for BAM adapter also? If yes, what we will specify in baam data source (What configuration i need to give).
    one more thing i noticed that, Outbound connection pool option is also not coming under BAM configuration
    Please help!!
    Thanks,

    hello,
    For BAM related settings are out of the box in web-logic server,here below points are describes steps to setup the Datasource whatever you call;
    1. In the Settings for oracle-bam-adapter page, select the Configuration tab, and then the Outbound Connection Pools tab.
    2. Configure the connection factory interface that you intend to use in Oracle JDeveloper, by expanding the appropriate Group and Instance target and clicking the Java Naming and Directory Interface (JNDI) name.
    3.     To configure the connection factory for RMI-based calls, click to expand the oracle.bam.adapter.adc.RMIConnectionFactory group and select the JNDI name that the user uses in Oracle JDeveloper. The eis/bam/rmi connection factory is provided out of the box.
    4.     To configure the connection factory for SOAP-based calls, click to expand the oracle.bam.adapter.adc.SOAPConnectionFactory group and select the JNDI name that the user uses in Oracle JDeveloper. The eis/bam/soap connection factory is provided out of the box.
    Hostname : local host (host name of BAM server)
    Instance Name: ADCServer1 (default for RMI)
    Password : welcome1 (password of BAM server)
    Port Number : 9001(port number of BAM server)
    Username : weblogic (user name of BAM server)
    5. after saving it need to re-deploy OracleBAMAdaper, In deployments select OracleBAMAdapter click Update button.
    I hope these steps are helpful.
    PS Outbound connection pool option is also not coming under BAM configuration -- for this check BAM server is running or not or any other BAM server installation or ect.
    Thanks
    Siva Sankar
    TechDemocracy

  • Build using 32-bit Sun JDK in dev windows OS and deploy in 32-bit RHEL

    Is there any potential problems associated with building/compiling my Java classes for my EE (Seam) app into an EAR and deploying on 32-bit Windows OS JBoss AS dev box using 32-bit Windows JDK 1.5 and then deploying the same EAR into 32-bit RHEL OS JBoss AS? The dev envmt is not clustered and the UAT RHEL envmt is a 2 node horizontal cluster without state replication (only mod_jk load balancing and failover).
    Perhaps the entity (and other) classes that implement java.io.Serializable will have issues? thx.

    Note: This thread was originally posted in the Serialization forum, but moved to this forum for closer topic alignment.

  • How to create and deploy a JSP which calls a BPEL process in JDEVELOPER

    Hi Gurus,
    I don't know how to create a JSP in JDEVELOPER which call a BPEL process. I have gone through the tutorials. Since, I am new to JDEVELOPER I need some help.
    1. How to create a JSP (I know creating application and project, also I know JSP coding)
    2. How to deploy this JSP?
    3. For the Synchronos BPEL project, the build.xml is created automatically, in this forum, I see people talking about ear war .deploy etc. How do we get them automatically created. Or do we need to create them manually. If it has to be manual some sample scripts would be of great help.
    Any help in this regard would be really great.
    Thanks in advance,
    Sankar.

    I found the following tutorial which clearly explains how to deploy J2EE apps.
    http://www.oracle.com/technology/obe/obe1013jdev/deployment/deployment.htm
    I created a simple jsp file in a project, followed the steps in the tutorial and it got deployed onto: http://localhost:9700
    For invoking BPEL process through JSP, I have reused the jsp files available in : 102.InvokingProcesses\jsp and changed the processes and input accordingly.
    Please post me a query in this thread, if any of you want any specific details.

  • Automate the EAR creation and deployment process

    Hi,
    I am trying to automate the EAR creation and deployment process. I am following this approach - http://www.oracle.com/technetwork/articles/adf/part4-098813.html
    In this approach we use pure ANT without OJDeploy. I am able to Create the EAR file but while deploying to weblogic server manually I get the attached error.
    Error is - java.lang.ClassNotFoundException: javax.faces.webapp.FacesServlet
    I would like to know, Is this the best practise to automate the EAR Creation and Deployment Process? If not, Please provide me some other best approach.
    Thanks in Advance.
    Regards
    Balaji S

    Balaji,
    I am the author of that article.
    At the time I wrote the article, ojdeploy was not working properly - however, the bugs that I noted at the time have been fixed. If I were writing the article today, my strong recommendation would be to use ojdeploy.
    If you insist to use the pure ANT (no ojdeploy) approach, I'd debug your issue this way:
    1). Generate the EAR file using the deploy option from the application navigator in JDeveloper. Deploy that EAR file to your WLS server and test to ensure it works. A note that if you are creating an ADF app, you must deploy the JRF to WLS first.
    2). Once the EAR from JDev is working, use a tool such as WinZip to expand the JDeveloper-generated EAR file and your ANT-generated EAR file. Compare the two. If you find differences, fix the ANT scripts so that they are the same.
    John

  • How to create a custom ear file and deploy it onto a freshly created oc4j

    Hi,
    Wanted to know that how should i go about creating a custom EAR file or for that matter any application and deploy it onto a test oc4j instance created within the 10.1.3 Home of Oracle Apps R12.
    I believe in a standalone Application server installation it is quite simple to deploy an application by creating an oc4j instance using the AS console ,but not very sure about how to go about it in Oracle Apps .
    N.B:I have been able to create a test oc4j instance by the name of Test and able to start and stop it using the opmn of 10.1.3 oracle home.
    Any help in this regard will be appreciated.

    Hi,
    can you please post this question to one of the Apps forums if your main concern is to deploy applications in the context of Oracle Apps?
    It seems that you don't have a problem in creating the EAR file in JDev.
    Frank

  • Programmatically create and deploy process definition

    1. It seems that PAPI does not support process definition creation and deployment. We need to programmatically create and deploy process definitions, what should we use?
    2. Is it possible to programmatically add variable definitions to a process instance? We have an external program that creates the process instance but sometimes the process instance may need to add some additional variables.
    Thank you for your help,
    shirley

    Hi Shirley,
    You're right PAPI wasn't intended to deploy processes, however, you can deploy processes automatically using ANT.
    You'd need to republish and redeploy (again using ANT) to add additional variables to a deployed process. Simplest thing to do would be to add attributes to an existing BPM Object. If you just added a new variable, you'd need to change argument mapping troughout the project.
    hth,
    Dan

  • 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"/>
         <!-- this runs the create.bat which has all of the wscompile parameters -->
         <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>
    <!-- JNDI Name of the Topic that the SvcOwnerShipmentSubscriberMDB listens for messages on -->
    <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.

Maybe you are looking for