Skip Headers
Oracle® Application Server Adapter Installation Guide
10g Release 2 (10.1.2)
B14063-05
  Go To Documentation Library
Home		 Go To Product List
Solution Area		 Go To Table Of Contents
Contents		 Go To Index
Index
Previous
Previous 		 Next
Next		  

2 Installation and Configuration

This chapter describes how to install and configure Oracle Application Server adapters. It contains the following topics:

Installation Tasks

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

  1. If you want to install the Complete installation type, then log on to the middle-tier host where you installed the J2EE and Web Cache installation type of Oracle Application Server.

  2. If you are installing on Solaris or Linux, then refer to Oracle Application Server Installation Guide for the specific operating system for instructions to:

    • Set the mount point for the CD-ROM

    • 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 follows
    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 follows
    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.2.0.2

    • OracleAS Adapter for PeopleSoft 10.1.2.0.2

    • OracleAS Adapter for SAP R/3 10.1.2.0.2

    • OracleAS Adapter for Siebel 10.1.2.0.2

    • OracleAS Adapter for CICS 10.1.2.0.2

    • OracleAS Adapter for IMS/DB 10.1.2.0.2

    • OracleAS Adapter for IMS/TM 10.1.2.0.2

    • OracleAS Adapter for Tuxedo 10.1.2.0.2

    • OracleAS Adapter for VSAM 10.1.2.0.2

  12. Click Next.

  13. If you have selected Design-time and Run-time in Step 9, then the select the OC4J home page is displayed. Perform Steps 13a through 13b. Otherwise, the Summary screen is displayed. Go to Step 14.

    1. Select the container where you want to deploy the run-time components. By default, the runtime components are deployed in the OC4J_BPEL container home.

    2. Click Next. The Summary screen is displayed.

      Figure 2-3 Summary Screen

      Description of Figure 2-3 follows
      Description of "Figure 2-3 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:

  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.


    Note:

Postinstallation Tasks for Packaged-Application Adapters

Perform the following postinstallation configuration tasks for packaged-application adapters:


Note:

The directory paths mentioned in this guide follow UNIX conventions. For example, forward slashes (/) are used.

If you are using OracleAS Adapter on Windows, then modify the directory paths as required.

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.

Adapter Library Files
OracleAS Adapter for J.D. Edwards OneWorld XE J.D. Edwards OneWorld Java-based ThinNet API

This API is distributed as .jar files on the J.D. Edwards OneWorld installation media. These libraries can vary based on the J.D. Edwards OneWorld release and include the following filess:

  • Kernel.jar

  • Connector.jar
OracleAS Adapter for PeopleSoft
  • PeopleSoft Java Object Adapter file (psjoa.jar)

    This file provides a low-level interface between client applications and PeopleSoft. This file is provided with PeopleSoft in the PeopleSoft_home_directory/web/PSJOA directory.

    The psjoa.jar file is different for every version of PeopleSoft. When you upgrade your Peopletools release, ensure that you copy the psjoa.jar file for the new release into the lib directory and restart all components.

  • pstools.properties

    This file is required for PeopleSoft 8.1x. This file belongs in the PeopleSoft_home_directory/web/jmac directory.
OracleAS Adapter for SAP R/3 The SAP Java connector (typically named sapjco.jar)

Information on the current set of SAP connectors is available at http://service.sap.com/connectors.

A valid SAP service ID is required to access this file. Follow the instructions provided on the SAP Java Connector (SAP JCo) overview page to download the current version. For more information, contact your SAP BASIS Administrator.

Using the archive tool, open the archive containing the SAP JCo and extract the runtime files. The file names can vary by operating system, but typically are contained in the root of the archive.

Note: All operating systems: You must place the sapjco.jar file in the ORACLE_HOME\adapters\application\lib directory. Then, you must add the sapjco.jar to the Oracle Application Server classpath.

On Windows, librfc32.dll should be placed in the %WINDIR%\system32 directory and sapjcorfc.dll should be placed in the same directory as sapjco.jar (ORACLE_HOME\adapters\application\lib). On other platforms, use the corresponding location. These library files vary by operating system. For example:

Linux/Solaris/OS400:

  • libsapjcorfc.so

  • librfccm.so

HP-UX:

  • librfccm.sl

  • libsapjcorfc.sl

AIX:

  • librfccm.so

  • libsapjcorfc.so

On UNIX platforms, the directory in which the shared library files are located must be added to the shared library variable applicable to the operating system. The following is a list of platforms and associated variables:

AIX:

  • LIBPATH

HP-UX:

  • SHLIB_PATH

Other UNIX Platforms

  • LD_LIBRARY_PATH

Solaris: The following are the two supported methods for specifying the SAP library files:

  • Copy the SAP JCO files (sapjco.jar, librfccm.so, and libsapjcorfc.so) to ORACLE_HOME/jdk/jre/lib/sparc/server

  • Copy the SAP JCO files to /usr/j2sdk1.4.2_09/jre/lib/sparcv9/server

Alternatively, you may add the path to these files to your environment variable definition using the Application Server Control console. For details on application server administration options, see Oracle Application Server Administrator's Guide.
OracleAS Adapter for Siebel For Siebel 6.3.x and later, the Siebel Java Data Bean API, which is distributed as .jar files with the Siebel Thin Client

These libraries vary by Siebel release in both content and name. Therefore, the Siebel Thin Client that comes with the target Siebel system must always be used with the adapter. For example:

For Siebel 6.3.x:

  • SiebelTcOM.jar

  • SiebelTcCommon.jar

  • SiebelTC_enu.jar

  • SiebelDataBean.jar

For Siebel 7.0.3:

  • SiebelJI_Common.jar

  • SiebelJI_enu.jar

For Siebel 7.5.2:

  • SiebelJI_Common.jar

  • SiebelJI_enu.jar

The Siebel COM-based API (Windows only) requires the Siebel Thin Client to be installed and accessible to the Siebel adapter.

Note: The following previously listed files are for English language installations:

  • SiebelTC_enu.jar

  • SiebelJI_enu.jar

  • SiebelJI.jar

For non-English installations, the last three letters (enu) vary.

If you are using the MQ Series as a transport, then you also need to use com.ibm.mq.jar file.

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-5. This page enables you to test the sample Web server installed with the OracleAS Adapter Business Services Engine.

    Figure 2-5 OracleAS Adapter Business Services Engine Home Page

    Description of Figure 2-5 follows
    Description of "Figure 2-5 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>

Note:

The IWayRepoURL, IWayRepoUser, and IWayRepoPassword parameters are used for a database repository only.

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.

Table 2-1 Packaged Application Adapter Directory Structure

Subdirectory Description

bin

Contains the install.xml file

config

Contains the jca_sample subdirectory and the XML-file-based repository for the OracleAS Adapter J2CA

etc

Contains the ibse.ear, iwafjca.ear, iwafjca.rar, and iwse.ora files

lib

Contains library files

tools

Contains the OracleAS Adapter Application Explorer graphical user interface

wsdl

Contains the WSDL files generated by the user

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


Note:

A user can create additional directories under the WSDL directory to organize the generated WSDL files.

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 computer where database is installed.

  2. Copy the jcatransport.properties file at the following directory:

    Oracle_Home\adapters\application\config\jca_sample

  3. Remove comments form the following fields and enter details for the following fields in the jcatransport.properties file

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

  4. Alter the JDBC driver path in Application Explorer as shown:

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

PostInstallation Tasks for Legacy Adapters

This section describes the following postinstallation taks for legacy adapters:

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 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 :

Parameter Description
LegacyServer Specifies the legacy server(s) where attunity connect is running
LegacyPort Specifies the port(s) where attunity connect is listening
LegacyUser Specifies the user ID(s) that can acces mainframe system
LegacyUserCredential Specifies the encrypted pasword(s) for the user

Example 2-1 Updating the collaxa-config.xml File

In the following example, the collaxa-config.xml file is updated with the required parameters.


 <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>

Note:

if you have an anonymous access setup in Oracle Studio, then you need to specify null for both LegacyUser and LegacyUserCredentialproperty.

Example 2-2 Specifying Multiple Connections

To add more instances of legacy systems, provide comma separated values for each computer as shown in the following example:




 <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>

Deinstallation Tasks

To deinstall Oracle Application Server adapters:

  1. Start Oracle Universal Installer, which is installed on your host.

  2. Click Deinstall Products.

  3. Expand the Oracle home directory that contains the products that you want to deinstall.

  4. Select the specific OracleAS Adapter that you want to deinstall.

  5. Click Remove.

  6. Click Yes when prompted. The selected products are deinstalled.

  7. Click Close.


    Note:

    The legacy J2CA resource adapter must be undeployed only if you choose to undeploy the entire set of legacy adapters.

Globalization Support

The Oracle Application Server adapters for packaged applications and legacy applications support a wide variety of encoding and can accept non-ASCII data during runtime. In addition, Application Explorer supports localization, while Oracle Studio does not support localization.


Note:

Application Explorer supports ADA compliance, while Oracle Studio does not support ADA compliance.

  Previous
Previous 		 Next
Next
 
  Go To Documentation Library
Home		 Go To Product List
Solution Area		 Go To Table Of Contents
Contents		 Go To Index
Index