2 Installation and Configuration

Installing Oracle Application Server 10.1.3.1

Oracle Application Server can be installed with the following:

• Oracle Application Server SOA Suite

• Oracle BPEL Process Manager

• Oracle Enterprise Service Bus

• J2EE and Web Cache

To install Oracle Application Server adapters, perform the following steps:

1. If you have already installed Oracle BPEL Process Manager (BPEL) and Oracle Enterprise Service Bus (ESB) as part of the SOA suite, skip this step and move to Step 3.

   However, if you have installed the J2EE and Web Cache installation type of Oracle Application Server, then you must modify the {J2EE_HOME}/config/server.xml:

   <shared-library name="oracle.bpel.common" version="10.1.3">
         <code-source path="/temp/dummy/"/>
   </shared-library>
   

   If you do not modify server.xml, then you may encounter an error with the JCA-APP-Adapter not deploying during installation.

2. If you are installing on Solaris or Linux, then refer to Oracle Application Server Installation Guide 10g for Solaris Operating System and Oracle Application Server Installation Guide for hp HP-UX PA-RISC, and Linux x86 for specific operating system for instructions to:

   • Set the mount point for the CD-ROM

   If you are installing on Microsoft Windows, then refer to Oracle Application Server Installation Guide for Microsoft Windows for instructions to:

   • Start Oracle Universal Installer

3. Insert the OracleAS Adapter CD-ROM.

4. Navigate to the software directory of the OracleAS Adapter CD-ROM.

5. Start Oracle Universal Installer. The following table describes the step for starting Oracle Universal Installer.

   Platform	Step
   Solaris or Linux	Enter the following command at the operating system prompt: ./runInstaller
   Windows	Click setup.exe.

   
   

   The Welcome screen is displayed.

6. Click Next. The Specify File Locations screen is displayed as shown in Figure 2-1.

   Figure 2-1 Specify File Locations

   
   Description of "Figure 2-1 Specify File Locations"
   
   

7. Enter the Oracle Home name, where you want to install OracleAS Adapter in the Destination fields. Do not change the directory path in the Source field. This is the location of the OracleAS Adapter installation files.

8. Click Next. The Select Installation Type screen is displayed.

9. Select one of the following types of installation type:

   • Design time and Run time

   • Design time

10. Click Next. The Available Product Components screen is displayed, as shown in Figure 2-2.

    Figure 2-2 Available Products Components

    
    Description of "Figure 2-2 Available Products Components"
    
    

11. Select the adapters you want to install from the following list:

    • OracleAS Adapter for J.D. Edwards OneWorld XE 10.1.3.1.0

    • OracleAS Adapter for PeopleSoft 10.1.3.1.0

    • OracleAS Adapter for SAP R/3 10.1.3.1.0

    • OracleAS Adapter for Siebel 10.1.3.1.0

    • OracleAS Adapter for CICS 10.1.3.1.0

    • OracleAS Adapter for IMS/DB 10.1.3.1.0

    • OracleAS Adapter for IMS/TM 10.1.3.1.0

    • OracleAS Adapter for Tuxedo 10.1.3.1.0

    • OracleAS Adapter for VSAM 10.1.3.1.0

12. Click Next.

13. If you have selected Design-time and Run-time in Step 9, then the Administration Settings is displayed, as shown in Figure 2-3. Perform Steps 13a through 13b. Otherwise, the Summary screen is displayed. Go to Step 14.

    Figure 2-3 Administration Settings

    
    Description of "Figure 2-3 Administration Settings"
    
    

    1. Type the AS Administrator password.

    2. Click Next. The Summary screen is displayed, as shown in Figure 2-4.

       Figure 2-4 Summary Screen

       
       Description of "Figure 2-4 Summary Screen"
       
       

14. Review specific details on the Summary screen, including the disk requirements to ensure that you have sufficient disk space.

15. Click Install.

    After the installation is complete, the following postinstallation configuration assistants are started to automatically configure OracleAS Adapter, as shown in Figure 2-5:

    • Deploy JCA Legacy Adapters

    • Deploy JCA Application Adapters

    • Deploy JCA Application Adapters Test

    • Deploy Web Services Application Adapters

      Figure 2-5 Configuration Assistants Screen

      
      Description of "Figure 2-5 Configuration Assistants Screen"
      
      

16. If installation and configuration are successful, then the End of Installation screen is displayed. The selected adapters are installed in the adapters/application directory of your Oracle home for packaged application adapters.

    For details about the installation, refer to the latest installActionsYEAR_MM_DD_TIME.log file located in the oraInventory_location/logs directory on UNIX or the Program Files\Oracle\Inventory\logs directory on Windows.

Applying Oracle Application Server 10g Release 3 (10.1.3) Patch Set 4 (10.1.3.4.0)

The next task is to apply Oracle Application Server 10g Release 3 (10.1.3) Patch Set 4 (10.1.3.4.0).

This section describes the procedure for Oracle Application Server 10g Release 3 (10.1.3) Patch Set 4 (10.1.3.4.0). It includes the following steps:

1. Insert Disk1 of the Oracle Application Server 10g Release 3 (10.1.3) Patch Set 4 (10.1.3.4.0) media, or navigate to the Disk1 subdirectory in the directory that contains the unpacked patch set software.

2. Start Oracle Universal Installer:

   • For Linux x86:

     Run the runInstaller command.

   • For Microsoft Windows (32-Bit):

     Double-click setup.exe.

   The Oracle Universal Installer: Welcome page appears, as shown in Figure 2-6.

   Figure 2-6 The Oracle Universal Installer: Welcome Page

   
   Description of "Figure 2-6 The Oracle Universal Installer: Welcome Page"
   
   

3. Review the Oracle Universal Installer Welcome screen and click Next.

   The Oracle Universal Installer: Specify File Locations screen appears, as shown in Figure 2-7.

   Figure 2-7 The Oracle Universal Installer: Specify File Locations Page

   
   Description of "Figure 2-7 The Oracle Universal Installer: Specify File Locations Page"
   
   

4. Enter the following details in the Specify File Locations page.

   • Source: This is the full path to the products.xml file from which the product will be installed. If you started the installer by using the runInstaller command or the setup.exe file, then the installer detects and uses the default values of the products.xml file. Do not change the path.

   • Name: Select the name of the Oracle home you want to patch from the drop-down menu.

   • Path: This field is filled in automatically when you select an existing Oracle home from the Name drop-down menu.

   • Browse: Use this button to navigate the file system and select the source or destination locations.

5. Click Next after specifying the file location.

   The Administrator (oc4jadmin) Password page appears, as shown in Figure 2-8.

   Figure 2-8 The Administrator (oc4jadmin) Password Page

   
   Description of "Figure 2-8 The Administrator (oc4jadmin) Password Page"
   
   

6. Enter the oc4jadmin user password for the Oracle Application Server instance that is being patched, and then click Next.

   A warning informing that the middle tier will be shutdown appears, as shown in Figure 2-9.

   Figure 2-9 The Warning Page

   
   Description of "Figure 2-9 The Warning Page"
   
   

7. Click OK.

   The Summary page appears, as shown in Figure 2-10.

   Figure 2-10 The Oracle Universal Installer: Summary Page

   
   Description of "Figure 2-10 The Oracle Universal Installer: Summary Page"
   
   

8. Verify your selections and click Install.

   The Install page appears showing the progress of the patch set installation appears, as shown in Figure 2-11.

   Figure 2-11 The Oracle Universal Installer: Install Page

   
   Description of "Figure 2-11 The Oracle Universal Installer: Install Page"
   
   

9. After the patch set is installed, the configuration Assistants configure components automatically. The Configuration Assistants page appears, as shown in Figure 2-12.

   Figure 2-12 The Oracle Universal Installer: Configuration Assistants Page

   
   Description of "Figure 2-12 The Oracle Universal Installer: Configuration Assistants Page"
   
   

10. After installing the configuration assistants the End of Installation appears, as shown in Figure 2-13.

    Figure 2-13 The Oracle Universal Installer: End of Installation Page

    
    Description of "Figure 2-13 The Oracle Universal Installer: End of Installation Page"
    
    

Installing Patches

The first postinstallation step is to install the following mandatory patches available on metalink:

• Patch 5717193 for Tuxedo adapters.

• Patch 5895585 for Application Adapters: mySAP, Siebel, Peoplesoft and J.D. Edwards OneWorld XE.

• Patch 5895598 for Legacy Adapters: Tuxedo, CICS, VSAM, IMS/TM and IMS/DB.

Copying the Library Files

Packaged-application adapters require you to copy library files to directories.

1. Copy the library files for these adapters into the ORACLE_HOME/adapter/application/lib directory.

Verifying BSE deployment

To verify the OracleAS Adapter Business Services Engine installation:

1. Open the following page in your Web browser:

   http://hostname:port/ibse/IBSEServlet/
   

   where hostname is the name of the Oracle Application Server host and port is the HTTP port of the Oracle Application Server. For example:

   http://localhost:80/ibse/IBSEServlet
   

   The OracleAS Adapter Business Services Engine home page opens, as shown in Figure 2-14. This page enables you to test the sample Web server installed with the OracleAS Adapter Business Services Engine.

   Figure 2-14 OracleAS Adapter Business Services Engine Home Page

   
   Description of "Figure 2-14 OracleAS Adapter Business Services Engine Home Page"
   
   

2. Click IVP, iwayivp, ivp, and Invoke.

   An XML response similar to the following is displayed in your browser:

   <?xml version="1.0" encoding="UTF-8" ?>
   - <SOAP-ENV:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:SOAPENV="
   http://schemas.xmlsoap.org/soap/envelope/"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
   - <SOAP-ENV:Body>
   - <ivpResponse xmlns="urn:oraclesoftware:ibse:jul2003:ivp:response"
   cid="A0328ED84ABFA055C4F64B8039C991AA">
   <CurrentTime>2004-01-05T19:15:48Z</CurrentTime>
   <Version>IWAY5.5</Version>
   </ivpResponse>
   </SOAP-ENV:Body>
   </SOAP-ENV:Envelope>
   

Configuring the J2CA deployment

OracleAS Adapter JCA supports file and database repository. The default repository is a file repository. You can create the database repository by running the iwse.ora SQL script in the adapters/application/etc directory.

If you selected the Design-time and Run-time installation type, then Oracle Universal Installer automatically deploys OracleAS Adapter JCA version 1.0 and provides a default oc4j-ra.xml configuration file. This file contains a default ManagedConnectionFactory with eis/Oracle JCAAdapter/DefaultConnection as the JNDI name:

<connector-factory location="eis/OracleJCAAdapter/DefaultConnection"  connector-name="IWAFJCA10">   <config-property name="IWayHome" value="../../adapters/application"/>   <config-property name="IWayConfig" value="jca_sample"/>   <config-property name="IWayRepoURL" value=""/>   <config-property name="IWayRepoUser" value=""/>   <config-property name="IWayRepoPassword" value=""/>   <config-property name="logLevel" value="debug"/></connector-factory>

You can create a different ManagedConnectionFactory by editing the oc4j-ra.xml configuration file. To do this:

1. Open the ORACLE_HOME/j2ee/OC4J_BPEL/application-deployments/default/jca-app-adapter/oc4j-ra.xml file.

2. Change the iWayConfig parameter to point to the corresponding OracleAS Adapter JCA version 1.0 repository project.

3. Set the JNDI location to the correct value. For example:

   <connector-factory location="eis/OracleJCAAdapter/MyConnection" connector-name="IWAFJCA10">
      <config-property name="IWayHome" value="../../adapters/application"/>
      <config-property name="IWayConfig" value="My_jca_config"/>
      <config-property name="IWayRepoURL" value=""/>
      <config-property name="IWayRepoUser" value=""/>
      <config-property name="IWayRepoPassword" value=""/>
      <config-property name="logLevel" value="debug"/>
      </connector-factory>
   

Verifying the J2CA Installation

To verify the J2CA version 1.0 installation:

1. Open the ORACLE_HOME/j2ee/OC4J_BPEL/applications/jca-app-adapter-test /iwafjca/WEB-INF/web.xml file.

2. Modify the deployment descriptor web.xml file to point to the JNDI location of the ManagedConnectionFactory defined in Step 2 of "Configuring the J2CA deployment".

   You can access the OracleAS Adapter JCA test servlet using the following URL:

   http://hostname:port/iwafjca
   

   where hostname is the name of the Oracle Application Server host and port is the HTTP port of the Oracle Application Server.

Directory Structure

The packaged application adapters are installed into the adapters/application subdirectory of your Oracle home directory. Table 2-1 shows the directory structure. The license.xml file is also installed in the application directory.

The directory\legacy folder contains the .rar file for legacy adapters. In addition, the adapters\lib folder contains the orabpel-adapters.jar file.

Starting Application Explorer

Use Application Explorer to configure the OracleAS Adapter J2CA version 1.0 and OracleAS Adapter Business Services Engine repository projects. To start Application Explorer on Windows, From the Start menu, select Programs, OracleAS_home Adapters, and then select Application Explorer.

In addition, on Windows, iaexplorer.bat is found under OracleAS_home\adapters\application\tools

Where OracleAS_home is the directory where Oracle Application Server is installed.

On UNIX, load the iwae.sh script, found under OracleAS_home/adapters/application/tools

Where OracleAS_home is the directory where Oracle Application Server is installed.

Configuring the Database Repository for J2CA

1. Execute the iwse.ora SQL statement on the machine where database is installed.

2. Create the jcatransport.properties file and save it in the following directory:

   Oracle_Home\adapters\application\config\jca_sample

3. Enter values for iwafjca.repo.url, iwafjca.repo.user and iwafjca.repo.password fields in the newly created jcatransport.properties file, as shown in the following example:

   iwafjca.repo.url=jdbc:oracle:thin:@90.0.0.51:1521:orcl

   iwafjca.repo.user=scott

   iwafjca.repo.password=scott1

4. Open the oc4j-ra.xml file in a text editor.

5. Provide the JDBC connection information as a value for the IWAYRepo_URL property.

6. Provide a valid user name for the IWAYRepo_User property.

7. Provide a valid password for the IWAYRepo_Password property.

8. Save your changes to the oc4j-ra.xml file.

9. Alter the JDBC driver path in Application Explorer. Change the path shown in example1 to the path listed in example2:

   Example1:

   lcp=..\lib\orabpel-adapters.jar;C:\jdev\jdbc\lib\classes12.jar;C:\jdev\jdbc\lib
   \nls_charset12.jar;%lcp%
   

   Example2:

   lcp=..\lib\orabpel-adapters.jar;..\..\..\jdbc\lib\ojdbc14.jar;..\..\..\jdbc\l
   ib\nls_charset12.jar;%lcp%
   

Modifying server.xml

You must edit $ORACLE_HOME/j2ee/(container)/config/server.xml, where the container could be either home or oc4j_soa based on your installation. Typically, SOA Basic installation uses the home container while the SOA advanced installation uses the oc4j_soa container.

Perform the following steps to modify server.xml:

1. Create an entry for jca.app.adapter.libraries in server.xml. The required jar files should be added to this new library section. Typically these jar files are EIS library files delivered by respective EIS vendors.

   The following is a sample entry into server.xml for jca.app.adapter.libraries:

   <shared-library name="jca.app.adapter.libraries" version="1.0"
   library-compatible="true">
   <code-source path="C:\soadp1\adapters\application\lib\psjoa.jar"/>
   <code-source path="C:\soadp1\adapters\application\lib\psGenCompF840Mi14.jar"/>
   <code-source path="C:\soadp1\adapters\application\lib\sapjco.jar"/>
   </shared-library>
   

   Note:

   In the preceding example substitute your oracle home in the path. Only jar files should be added in the preceding example. Additionally, *.so or *.dll files should be mentioned in PATH.

2. You should import jca.app.adapter.library in the oracle.bpel.common section in the shared library of server.xml, as shown in the following example:

   <import-shared-library name="jca.app.adapter.libraries"/>
   

Modifying oc4j-ra.xml

The following are the steps to modify oc4j-ra.xml:

1. Add the following code to the imported-shared-libraries section of oc4j-ra.xml:

   <import-shared-library name="jca.app.adapter.libraries"/>
   

2. Make changes in the two oc4j-ra.xml files, as mentioned in the following example:

   1. Example1:

      <<j2ee-home>>\application-deployments\default\jca-app-adapter\
      oc4jra.xml
      

   2. Example2:

      <<j2ee-home>>\connectors\jca-app-adapter\jca-app-adapter\META-INF\
      oc4j-ra.xml
      

   Note:

   If you re-deploy JCA-App-Adapter, then the changes mentioned in the preceding examples will be deleted.

Configuring HP Itanium 64 Machine for mySAP ERP Adapter

You must perform the following steps to configure an HP Itanium 64 bit machine to work with the mySAP ERP adapter. Note that the SAPJCO libraries require using the java libraries and executable files delivered by HP with the Itanium 64 bit machine and not the java delivered with Oracle Application Server.

1. Point the libraries in the profile to the 64 bit versions and set the java options to 64 bit. And then, ensure that the java class loader has the read and execute permissions on the binaries. The following is a sample of the setting of the .profile file. Note that the folders used in this example are for illustration purpose only.

   • The following is a sample code for the java options to 64 bit:

     _JAVA_OPTIONS=-D64
     export _JAVA_OPTIONS
     

   • The following is a sample code to include the 64-bit libraries CLASSPATH=/rdms/fpgjpr in the PATH, CLASSPATH and SHLIB_PATH variables:

     export CLASSPATH
     SHLIB_PATH=$SHLIB_PATH:/rdbms/fpgjpr
     export SHLIB_PATH
     PATH=$PATH:/rdbms/fpgjpr:/opt/java1.5/jre/bin/IA64W:/opt/java1.5/jre/lib:/opt/java1.5/lib
     export PATH
     

   Note:

   You must perform the following steps to change the settings of the .profile file:

   1. Make a backup of the profile.

   2. Make the required changes to the .profile file.

   3. Exit and enter into the UNIX login.

2. Set the permissions on the three files; sapjco.jar, libsapjcorfc.so, and librfccm.so to read and execute.

3. Point Oracle Application Server to the java file that was delivered with HP Itanium. It should not point to the java that was delivered with Oracle Application Server. To do this, you must modify the data id(<data id="java-bin" value="/opt/java1.5/jre/bin/IA64W/java"/>) in the oc4j_soa process type. You must set the new java home, as shown in the following example:

   <process-type id="oc4j_soa" module-id="OC4J" status="enabled">
                  <module-data>
                     <category id="start-parameters">
                        <data id="java-options" value="-server
   -XX:MaxPermSize=192M -ms512M -mx1024M -XX:AppendRatio=3
   -Djava.security.policy=$ORACLE_HOME/j2ee/oc4j_soa/config/java2.policy
   -Djava.awt.headless=true -Dhttp.webdir.enable=false
   -Doraesb.home=/rdbms/ora102/product/10.1.3.1/OracleAS_1/integration/esb
   -Dhttp.proxySet=false -Doc4j.userThreads=true -Doracle.mdb.fastUndeploy=60
   -Dorabpel.home=/rdbms/ora102/product/10.1.3.1/OracleAS_1/bpel
   -Xbootclasspath^/p:/rdbms/ora102/product/10.1.3.1/OracleAS
   _1/bpel/lib/orabpel-boot.jar  -Dhttp.proxySet=false -Dfile.encoding=ISO8859_1
   -DAF_DEBUG_REC_CONV=true"/>
                        <data id="java-bin" value="/opt/java1.5/jre/bin/IA64W/java"/>
                     </category>
                     <category id="stop-parameters">
                        <data id="java-options" value="-Djava.security.policy=$ORACLE_HOME/j2ee/oc4j_soa/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false"/>
                     </category>
                  </module-data>
                  <start timeout="600" retry="2"/>
                  <stop timeout="120"/>
                  <restart timeout="720" retry="2"/>
                  <port id="default-web-site" range="12501-12600" protocol="ajp"/>
                  <port id="rmi" range="12401-12500"/>
                  <port id="rmis" range="12701-12800"/>
                  <port id="jms" range="12601-12700"/>
                  <process-set id="default_group" numprocs="1"/>
               </process-type>
   

   Note:

   The following are the steps to make changes to the opmn.xml file:

   1. Shutdown Oracle Application Server.

   2. Take a backup of the opmn.xml file.

   3. Make the required changes to the opmn.xml file.

   4. Restart Oracle Application Server.

Installing OPatch 7408494

This section describes how to install the OPatch 7408494 for legacy adapters. This section includes the following topics:

• Preinstallation Tasks for OPatch 7408494

• Installation Tasks for OPatch 7408494

• Postinstallation Tasks for OPatch 7408494

• Deinstallation Task for OPatch 7408494

% opatch lsinventory

% cd 7408494
% opatch rollback -id 7408494

Configuring Run-Time Connections

Perform the following steps to configure run-time connections:

1. Edit the oc4j-ra.xml file present at the following location:

   ORACLE_HOME\j2ee\OC4J_BPEL\application-deployments\default\jca-legacy-adapter

2. Set the following settings for each connection:

   <oc4j-connector-factories>
     <connector-factory location=" " connector-name="Oracle Legacy Adapter">
       <config-property name="userName" value=" "/>
       <config-property name="password" value=" "/>
       <config-property name="eisName" value=" "/>
       <config-property name="serverName" value=" "/>
       <config-property name="workspace" value=" "/>
       <config-property name="portNumber" value=" "/>
       <config-property name="persistentConnection" value=" "/>
       <config-property name="keepAlive" value=" "/>
       <config-property name="firewallProtocol" value=""/>
       <config-property name="connectTimeout" value=""/>
       <config-property name="encryptionProtocol" value=""/>
       <config-property name="encryptionKeyName" value=""/>
       <config-property name="encryptionKeyValue" value=""/>
       <config-property name="fakeXa" value="false"/>
       <config-property name="useNamespace" value="true"/>
     </connector-factory>
   </oc4j-connector-factories>
   

   The following table lists the properties that must be specified:

   Property	Description
   location	Specifies the JNDI location where Oracle Application Server should bind the connection factory instance for application components. It is mandatory that you specify the location as eis/legacy/eisName. This convention is used by the design-time WSIL browser when it generates the legacy adapter service WSDLs containing the JNDI location (specifically for the adapterInstanceJndi attribute on the jca:address element); this is the same JNDI location that the runtime uses to acquire a connection. For example, if the eisName is DEMOEvent, then the location should be specified as eis/legacy/DEMOEvent. In this example, the given eisName is DEMOEvent, therefore the WSIL design time sets adapterInstanceJndi=eis/legacy/DEMOEvent in the WSDL, and the runtime automatically will use eis/legacy/DEMOEvent JNDI location to acquire a run-time connection. Therefore, you need to set this same value for the location attribute, otherwise, the run-time resolution is going to fail and error out.
   eisName	Sets the name of the adapter to use.
   serverName	Sets the TCP/IP address or host name where the Oracle Connect daemon is running.
   workspace	Specifies the name of an Oracle Connect server workspace to use. The default workspace is Navigator.
   portNumber	Specifies the TCP/IP port where the Oracle Connect daemon is running on the server. The default port is 2552.
   fakeXa	Values can be set to true or false. When set to true, The XA APIs are converted internally to local transaction APIs.
   useNamespace	Values can be set to true or false. When set to true, XSD metadata are provided with namespace and payload nodes are built using this namespace. Note: It is recommended that you set this property to true.

   
   

   The following table lists the optional properties:

   Property	Description
   userName	Specifies a user who can access the Oracle Connect server. The user is defined in the Oracle Connect daemon configuration.
   password	Specifies a valid password for the user.
   persistentConnection	Set to true or false. When set to true, connections can persist across multiple requests or connection context changes. It is recommended to set this property to true.
   keepAlive	Set to true or false. When set to true, the socket used for the connection is always kept open. It is recommended to set this property to true.
   firewallProtocol	Specifies the firewall protocol used: either none or fixedNat (the Nat protocol using a fixed address for the daemon). The default is none.
   connectTimeout	Specifies the connection timeout in seconds. The default is 0, meaning that there is no connection timeout
   encryptionProtocol	Specifies the name of encryption protocol to use. The default is null. The RC4 protocol is supported.
   encryptionKeyName	Specifies the name of the symmetric encryption key to use.
   encryptionKeyValue	Specifies the value of the symmetric encryption key to use.

   
   

Configuring Design-Time Connections

If you need to browse legacy interactions using WSIL browser in Oracle JDeveloper, then update the collaxa-config.xml file. This enables the BPEL Process Manager to communicate with the legacy server. The collaxa-config.xml file is available at the following location:

$Oracle_Home/integration/orabpel/system/config

Perform the following steps to configure design-time connections:

1. From the Start menu, select Programs, Oracle BPEL PM, and then select Developer Prompt.

2. Type encrypt <passwd>.

3. In the collaxa-config.xml file, update the parameters listed in the following table:

<property id="LegacyServer">
        <name>Legacy server(s) where Oracle Connect is installed</name>
        <value>mvs08</value>
        <comment>
        <![CDATA[Server IP where Oracle Connect has been installed.
        <p/>
        The default fault is value <i>localhost</i>.]]>
       </comment>
   </property>

<property id="LegacyPort">
        <name>Legacy server port(s) where Oracle Connect is running</name>
        <value>2554</value>
      <comment>
      <![CDATA[Server port where Oracle Connect has been installed.
      <p/>      The default is <i>2551</i>.]]>     </comment>
</property>

<property id="LegacyUser">      <name>Legacy server user(s) where Oracle Connect is running</name>      <value>null</value>      <comment>      <![CDATA[Server user who has access to Oracle Connect.      <p/>      The default is <i>Null</i>.]]>     </comment>
</property>

<property id="LegacyUserCredential">        <name>Legacy server user credential(s) where Oracle Connect is                  running</name>        <value>null</value>
        <comment>        <![CDATA[Credential for server user that has access to Oracle Connect.        <p/>        The default is <i>Null</i>.]]>        </comment> </property>

<property id="LegacyServer">        <name>Legacy server(s) where Oracle Connect is installed</name>        <value>mvs08,mvs09</value>        <comment>        <![CDATA[Server IP where Oracle Connect has been installed.        <p/>        The default is <i>localhost</i>.]]>        </comment> </property>

 <property id="LegacyPort">        <name>Legacy server port(s) where Oracle Connect is running</name>        <value>2554,2555</value>        <comment>        <![CDATA[Server port where Oracle Connect has been installed.        <p/>        The default is <i>2551</i>.]]>        </comment>  </property>

<property id="LegacyUser">        <name>Legacy server user(s) where Oracle Connect is running</name>        <value>null,xyz</value>        <comment>        <![CDATA[Server user who has access to Oracle Connect.        <p/>        The default is <i>Null</i>.]]>        </comment> </property>

 <property id="LegacyUserCredential">        <name>Legacy server user credential(s) where Oracle Connect is running</name>        <value>null,AVCGS80JK9J08M9MLYJM90U</value>        <comment>        <![CDATA[Credential for server user that has access to Oracle Connect.        <p/>        The default is <i>Null</i>.]]>        </comment> </property>