Preparing for the AIA Communication Pack 2.

01 Installation

The following products are mandatory to be installed in sequence while installing AIA:

1) Oracle Database 10g Release 2 (10.2.0.1)

2) Oracle Database 10.2.0.3 Patchset Upgrade
3) Oracle SOA Suite 10g (10.1.3.1)-Enterprise Edition
4) Oracle SOA 10.1.3.3 Patchset Upgrade
5) AIA for Communications 2.0: Oracle SOA 10.1.3.3 patches
6) Oracle Service Registry 10.1.3.1
7) AIA for Communications 2.0.0
8) AIA Communication Patch for 2.0.1(720226)
9) Deploying and Configuring BRM JCA Adapter

3) Installation of SOA Suite 10g(10.1.3.1)-Enterprise Edition

1. Perform an advanced installation of the J2EE Server, Web Server and SOA Suite
install type,
2. You must create the ORABPEL, ORAESB and ORAWSM schemas into your
Oracle database before you begin the installation. To do so:
a) On Oracle Application Server Disk 1, go to the install/soa_schemas/irca
Directory.
b) Run the irca.sh script.

Passwords : ORABPEL -> orabpel

ORAESB -> oraesb
ORAWSM -> orawsm

NB: The Script should be run by the user having database execute
permissions.

3. The operating system user who will be installing Oracle Application Server needs
to set (or unset) the following environment variables.

Tips: i) To check the value of environment variables, use the env command. These
display all the currently defined environment variables and their values.
% env

ii) Edit your PATH, CLASSPATH, and LD_LIBRARY_PATH environment variables so

that they do not reference any Oracle home directories.

Environment Variable Summary

Environment Variable Set Or Unset

PATH, CLASSPATH, and Must not contain references to directories
LD_LIBRARY_PATH in any Oracle home
directories

DISPLAY Set it to the monitor where you want to the

installer window to
 appear.

TMP and TMPDIR Optional. If unset, defaults to /tmp.

ANT_HOME Must not be set. % unset ANT_HOME

TNS_ADMIN Must not be set.

ORA_NLS Must not be set. $ unset ORA_NLS

LD_BIND_NOW Must not be set.

4. After SOA Suite installation following things need to be checked:

In the ORACLE_HOME/j2ee/<oc4j_instance_name>/config/server.xml file for the

‘ascontrol’ application ‘start’ should be set to ‘true’.

<application name="ascontrol"
path="../../oc4j_instance_name/applications/ascontrol.ear"
parent="system"
start="true" />

5. In ‘default-web-site.xml’ the entry for ‘ascontrol’ application should have ‘ohs-

routing=true’.

<web-app application="ascontrol"
name="ascontrol"
load-on-startup="true"
root="/em"
ohs-routing="true" />

6. Taking a backup of configuration

Backup directory is located at <ORACLE_HOME>/backup_restore.

Edit config.inp files in the <ORACLE_HOME>/backup/config directory as the following

way:

oracle_home (optional) Do not insert a value for this. Using the

command-line interface,
set ORACLE_HOME in the shell environment
first.

log_path (optional) Specify the full path of the log file directory. If
the full path is not
specified, the default log directory
ORACLE_HOME/backup_
restore/logs is automatically created when
the -m
configure command is executed. If a
 log_path is specified in
the config.inp file, but the specified
directory does not exist,
OracleAS Recovery Manager automatically
creates the specified
log directory whether or not the -f (force)
option is used in the
-m configure command. However, the
configuration file
backup directory is not automatically created
unless the -f
option is specified.

config_files_list Do not insert a value for this; leave it as

config_files_
list=DO_NOT_SET.
This parameter will be updated with the
appropriate list of
configuration files for your installation when
you run bkp_
restore.pl -m configure.

config_backup_path Specify the full path of the configuration file

(mandatory) backup directory.

install_type Do not insert a value for this; leave it as

install_type=DO_
NOT_SET.
This parameter is updated with the
appropriate value for your
installation when you run bkp_restore.pl -m
configure.

orainst_loc_path This parameter is used for UNIX platforms

(optional) only. If the default
path is overridden during installation, specify
the full path of the
directory where the oraInst.loc file exits.
Otherwise, leave the
parameter with the default value.

plugin_config_files_ Do not update this parameter. It is updated

list=DO_NOT_SET when you enable
components containing plug-in backup input
files.

Run the following command:

i) ./bkp_restore.sh -m configure
ii) ./bkp_restore.sh -m backup_instance_cold
The Screen Shot For Installation of Oracle SOA Suite:

Screen 1
Screen 2

Screen 3
Screen 4

Screen 5
Screen 6

Screen 7
Screen 8

Screen 9
Screen 10

Screen 11
 Screen 12

4. Oracle SOA 10.1.3.3 Patchset Upgrade

1. If you have edited the dsa.conf file, then make a copy of it. The file will be
over-written during patch application.

2. If you use adapters, then make copies of the oc4j-ra.xml files. The files will be
over-written during patch application.

3. Ensure the following values are set in the

ORACLE_HOME/owsm/bin/install.properties file:
install.http.host=hostname (The machine name with the domain name)
install.http.port=7777(HTTP Port Assigned during Installation of SOA Suite)

4. Ensure the OC4J instances are running. You can check the status using the
following command:
For UNIX:
ORACLE_HOME/opmn/bin/opmnctl status
 5. Start runInstaller

6. Replace the current dsa.conf file with the copy made in step i).

7. Replace the oc4j-ra.xml files with the copies made in step ii).

Screen Shots for SOA Suite Patch Installation

Screen 1

Screen 2
Screen 3

Screen 4
Screen 5

Screen 6
 Screen 7

8. Post-Application task for Patch Set 3

i) Connect to the Oracle database as orabpel user.
ii) Run the following script :
<ORACLE_HOME>/bpel/system/database/scripts/upgrade_10131_10133_oracle.sql

iii) Enable PHP

Make the following changes in the file : ORACLE_HOME/Apache/Apache/conf/httpd.conf

a) Comment Ph4 directive:

#LoadModule php4_module libexec/libphp4.so
#AddModule mod_php4.c

b) Add the following directive :

LoadModule php5_module libexec/libphp5.so
AddModule mod_php5.c

AddType application/x-httpd-php .php .php5

AddType application/x-httpd-php-source .phps

c) Set the PHPRC environment variable to point to the php5.ini file:

setenv PHPRC ORACLE_HOME/Apache/Apache/conf/php5.ini

NB: Here the ORACLE_HOME is Application Server Home.

 iv) Enable Java Single Signon (Optional)

5. Installation of AIA for Communications 2.0: Oracle SOA 10.1.3.3 patches

The following 9 patches no needs to be installed:

1. 5473225
2. 5515836
3. 6311809
4. 6367355
5. 6443218
6. 6484367
7. 6499177
8. 6502942
9. 6503011

This is the patch to be installed through ‘OPatch’ utility. To install the patch simply
extract the file ‘p2617419_10102_GENERIC.zip’ using ‘unzip’ command into
‘ORACLE_HOME’ directory.

To apply all the patches extract all the zips under ‘fmw_patches’ directory & do the
following:

i) Set your current directory to the directory where the patch is located:
$ cd 5473225

ii) Ensure that the directory containing the opatch script appears in $PATH then
enter the following command:

$ opatch apply

Do steps i) and ii) for all the patch numbers mentioned above.

NB: To verify whether all the patches are installed type the command:

opatch lsinventory

9. Installation of Oracle Service Registry-10.1.3.1

Refer to Oracle Service Registry-10.1.3.1 Installation.pdf.

The following steps need to be carried out to increase the memory of Oracle AS.

i) Open the configuration file from the location : /opmn/conf/opmn.xml

ii) Locate the section :<module-id=”OC4J”>
iii) Change the ‘start-parameters’ as follows:
<category id="start-parameters">
<data id="java-options" value="-server -XX:MaxPermSize=128m -Xmx1024m
-Doc4j.userThreads=true
-Djava.security.policy=$ORACLE_HOME/j2ee/home/config/java2.policy
-Djava.awt.headless=true"/>
</category>

The Screen Shots are as follows

Screen 1
Screen 2

Screen 3
Screen 4
Screen 5

Screen 6

Screen 7
 Screen 8

NB: In the above screen The Database Administrator Name should be “sys as sysdba”
Screen 9

Screen 10

Screen 11
Screen 12

Screen 13
Please don’t check 4443 in case it is only http port

Screen 14

Screen 15
 Screen 16

After the installation do the following steps to complete the installation (This step is not
required if you have selected use ssl(HTTPS) while installing the service registry)

i) Delete the file <OC4J_HOME>/j2ee/home/keystore if it exists.

ii) Generate the server identity into <OC4J_HOME>/j2ee/home/keystore using the Java
keytool as follows:

keytool -genkey -keyalg RSA -alias oracle -keystore /<OC4J_HOME>/j2ee/home/keystore -storepass

<PASSWORD>

iii) Copy <OC4J_HOME>/j2ee/home/config/http-web-site.xml to

<OC4J_HOME>/j2ee/home/config/secure-website.xml.
iv) Edit <OC4J_HOME>/j2ee/home/config/secure-web-site.xml by changing the
port and adding the parameter secure="true" to the <web-site> element; for
example:

<web-site port="4443" ... secure="true">

v) Add the following element into the into the <web-site> element, use absolute
path to keystore file, for example:

<ssl-config keystore="<OC4J_HOME>/j2ee/home/keystore" keystore-

password="<PASSWORD>"/>
 vi) Add the path reference to secure-web-site.xml into the file server.xml:

<web-site path="./secure-web-site.xml" />

vii) Change the <web-app> definition for the Oracle AS Service Registry in both default-
web-site.xml & secure-web-site.xml with ‘shared=”true” attribute.

7. Installation of Oracle Communications 2.0:

PreInstallation Requirements

1) Confirm that directory browsing is enabled in the Apache server that SOA Suite is using.
For this, edit the <SOA_HOME>/Apache/Apache/conf/httpd.conf file as follows:
Using an editor like vi , edit the httpd.conf file and scroll until you find a line like this: “Options
All Indexes FollowSymLinks MultiViews” modify it to “Options All Indexes FollowSymLinks
MultiViews Indexes”

<Directory />
Options All Indexes FollowSymLinks MultiViews Indexes
AllowOverride None
</Directory>

2) JAVA_HOME is set to <ORACLE_HOME>/jdk

Example: export JAVA_HOME=<ORACLE_HOME>/jdk
3) PATH variable has bin of JAVA_HOME variable.
Example: export PATH=.:$JAVA_HOME/bin:$PATH

4) Suspend all other SOA Suite server activities prior to launching the Oracle AIA Installer.
During the course of installation, Oracle SOA Suite will be restarted multiple times. It is
strongly recommended that all server activities should be suspended during this time.

NB:Here the ORACLE_HOME is Application server home directory

5) To respond to the prompts from the Oracle AIA Installer, you will need to collect the
information shown in the following table.

Details of Local SOA Suite Installation

Server Name hostname.domainname
HTTP Port 7777
Username oc4jadmin
Password tikona123
OC4j Instance Name oc4j_soa
OPMN Request Port 6003
Oracle Database Server Details
Server Name hostname.domainname
Port Number 1521
Username sys (Should be user having dba privilege)
Password tikonadb
SID tikonadb
Oracle Service Registry Details
Server Name hostname.domainname
HTTP Port 7777
Username(administrator) admin
Password tikona123
OPMN Request Port 6003
OSR Registry Home Absolute home path where registry is
installed
Application Details – Siebel CRM
Host Name Will be provided by Siebel CRM
Port Number Will be provided by Siebel CRM
Username Will be provided by Siebel CRM
Password Will be provided by Siebel CRM
Application Details – Oracle Communications BRM
Host Name Will be provided by BRM
Port Number Will be provided by BRM
Database Host Name Will be provided by BRM
Database Port Will be provided by BRM
SID Will be provided by BRM
Username Will be provided by BRM
Password Will be provided by BRM
AQ Queue Name Will be provided by BRM

Screenshots of AIA 2.0.0 Installers

Screen 1
 Screen 2

Screen 3

NB: Deselect the option Revenue Accounting 2.0.0.0.0

Screen 4

Screen 6
Screen 7

Screen 8
Screen 9

Screen 10
Screen 11

Screen 12
 Screen 13

NB:Revenue Account Config Utility will not appear in the screen if you don’t install that
8) AIA Communication Patch for 2.0.1(720226)

i) Go to Disk1/install and run the installer

Screenshots of AIA Patch Installer

 Screen 1

Screen 2

NB: Click Yes

Screen 3

Screen 4
 Screen 5

10) Deploying and Configuring BRM JCA Adapter

 i) Open the Oracle_home/j2ee/Instance/config/applications.xml
configuration file for the J2EE instance.

ii) Add the oracle.bpel.common entry (shown in bold below) to the

imported-shared-libraries section of the file:

<imported-shared-libraries>
<import-shared-library name="adf.oracle.domain"/>
<import-shared-library name="oracle.bpel.common"/>
</imported-shared-libraries>

Save and close the file.

iii) Login to Application Server Page:

iv) Click on oc4j_soa instance in the above screen shot

v) Click on Applications Tab

vi) From the View Drop down Click on Standalone Resource Adapters
vii) Select the archive file present In your machine and click next

viii) Give a name to the BRM Adapter and click next

ix) In the next page you kind find the Status deployment screen.
x) After successful deployment, return the applications.xml file to its
original settings and add the oracle.bpel.common code source to the
BRM Adapter oc4j-ra.xml file:

Open the Oracle_home/j2ee/Instance/config/applications.xml configuration

file for the J2EE instance.

Remove the following oracle.bpel.common entry (shown in bold below):

<imported-shared-libraries>
<import-shared-library name="adf.oracle.domain"/>
<import-shared-library name="oracle.bpel.common"/>
</imported-shared-libraries>

Save and close the file.

xi) Open the JCA Resource Adapter oc4j-ra.xml file from the
Oracle_home/j2ee/Instance/application-
deployments/default/BRMAdapterDeploymentName directory.

Add the oracle.bpel.common entry (shown in bold below) to the oc4j-

connector-factories section of the file:

<oc4j-connector-factories...>
<imported-shared-libraries>
<import-shared-library name="oracle.bpel.common"/>
</imported-shared-libraries>
<oc4j-connector-factories>

xii) After successful deployment you can view the BRM Adapter name in
the Standalone resource adapters list as shown in screen shot below
xiii) Click on the Oracle BRM Adapter and go to Connection factories tab
and click create

xiv) Click Continue

 xv) Give a name to the JNDI Location(example eis/BRM)and Other
credentials as provided by BRM and click finish

The BRM Adapter is now ready to Use.

Important Location:

Installation Log: /ora/ora10gdb/oraInventory/10gupd/logs/<log-file-name.log>

Oc4j-ra.xml: <Application Server Home>/j2ee/oc4j_soa/application-

deployments/default/JmsAdapter

Log.xml:
<Application Server Home>/j2ee/oc4j_soa/log/oc4j_soa_default_group_1/oc4j/log.xml

Important Commands :

Starting opmn :
Go to opmn home i.e <ApplicationServerhome>/opmn/bin
Type: ./opmnctl startall

Stopping opmn:

Go to opmn home i.e <ApplicationServerhome>/opmn/bin

Type: ./opmnctl stopall
Status of opmn:
Go to opmn home i.e <ApplicationServerhome>/opmn/bin
Type: ./opmnctl status

Starting dbconsole

$ emctl start dbconsole

Starting Database Listener:

$ lsnrctl start