2 Installation and Configuration

This chapter describes how to install and configure OracleAS Adapter. It contains the following topics:

• Installation Tasks

• Postinstallation Configuration Tasks

• Packaged Application Adapter Directory Structure

• Deinstallation Tasks

2.1 Installation Tasks

To install OracleAS Adapter, 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 on:

   • Setting the mount point for the CD-ROM

   • Starting Oracle Universal Installer

3. Insert the OracleAS Adapter CD-ROM.

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

5. Start the Oracle Universal Installer:

   On...	Do This...
   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.

7. Enter the Oracle home name and directory path where you want to install OracleAS Adapter in the Destination fields. The directory path must be the same as the path at which you installed the J2EE and Web Cache installation type. 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 an installation type from the following, and click Next:

   • Complete

   • Design time

   The Available Product Components screen is displayed.

10. Select the adapters you want to install from the following, and click Next.

    • OracleAS Adapter for J.D. Edwards OneWorld XE

    • OracleAS Adapter for PeopleSoft

    • OracleAS Adapter for SAP R/3

    • OracleAS Adapter for Siebel

11. If you have selected Complete in Step 9, then the Select the OC4J Home page is displayed. Perform Steps 11a through 11b. Otherwise, the Summary screen is displayed. Go to Step 12.

    1. Select the OC4J container in which to deploy the runtime components. By default, the runtime components are deployed in the OC4J container home.

    2. Click Next. The Summary screen is displayed.

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

13. Click Install.

    After the installation is complete, the following postinstallation configuration assistants are started to automatically configure OracleAS Adapter:

    • Deploy JCA Application Adapters

    • Deploy JCA Application Adapters Test

    • Deploy Web Services Application Adapters

    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: If you wish to install the EIS Adapter Plugin, then refer to the installation steps mentioned in Appendix A, "EIS Adapter Plugin". If you wish to install the OracleAS Adapter for PeopleSoft, then refer to the installation steps mentioned in Appendix B, "Configuring OracleAS Adapter for PeopleSoft".

    
    

2.2 Postinstallation Configuration Tasks

Perform the following postinstallation configuration tasks:

• Copying the Library Files

• Verifying the OracleAS Adapter Business Services Engine Installation

• Configuring OracleAS Adapter JCA Version 1.0 After Deployment

• Verifying the OracleAS Adapter JCA Version 1.0 Installation

• Configuring OracleAS Adapter Application Explorer

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.

2.2.1 Copying the Library Files

Some packaged 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.

For...	Copy...
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 typically consist of: 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: The sapjcorfc.jar and librfc32.dll files must be mentioned in the Oracle Application Server CLASSPATH.
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.

2.2.2 Verifying the OracleAS Adapter Business Services Engine Installation

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

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>
   
   

2.2.3 Configuring OracleAS Adapter JCA Version 1.0 After 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 Complete 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_CONTAINER/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>
   

2.2.4 Verifying the OracleAS Adapter JCA Version 1.0 Installation

To verify the OracleAS Adapter JCA version 1.0 installation:

1. Open the ORACLE_HOME/j2ee/home/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 OracleAS Adapter JCA Version 1.0 After 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.

2.2.5 Configuring OracleAS Adapter Application Explorer

Use the OracleAS Adapter Application Explorer to configure the OracleAS Adapter JCA version 1.0 and OracleAS Adapter Business Services Engine repository projects. To configure OracleAS Adapter Application Explorer, run the following command to configure the repository projects:

ORACLE_HOME/adapters/application/tools/ae.bat (WINDOWS)
ORACLE_HOME/adapters/application/tools/ae.sh (UNIX)

2.3 Packaged Application Adapter 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

2.4 Deinstallation Tasks

To deinstall OracleAS Adapter:

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

2. Click Deinstall Products.

3. Expand the Oracle home 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.