This chapter describes the tasks that you must complete before installing Oracle Application Integration Architecture (Oracle AIA) pre-built integrations.
Before installing Oracle AIA, perform the following tasks:
Perform the procedure in "Enabling Unicode Support on UNIX" for all pre-built integration options in UNIX environments.
Perform the procedure in "Deploying JCA Resource Adapter" for the following pre-built integration options:
Agent Assisted Billing Care
Order to Cash for Oracle Communications Billing and Revenue Management (BRM)
Perform the procedure in "Configuring the Timeout Values" for the Order to Cash for BRM pre-built integration option.
Perform the procedure in "Creating Oracle Data Integrator Repositories" for the Agent-Assisted Billing Care pre-built integration option.
Perform the procedures in "Cluster Pre-Installation Tasks" for Oracle AIA in clustered environments.
On UNIX operating systems, Oracle recommends enabling Unicode support for Oracle Service Oriented Architecture (SOA).
To enable Unicode support:
In the command line for the system where Oracle Fusion Middleware is installed, run the following commands:
setenv LANG en_US.UTF-8 setenv LC_ALL en_US.UTF-8
where en_US is your locale.
These environment variables set the installation default locale and override the value of any other environment variables that begin with LC_.
Open Oracle JDeveloper.
From the Tools menu, select Preferences.
From the tree table, select the Environment element.
From the Encoding menu, select UTF-8.
Click OK.
For the Agent Assisted Billing Care pre-built integration option and the Order to Cash for BRM pre-built integration option, you must deploy and configure JCA Resource Adapter.
See Oracle Communications Billing and Revenue Management JCA Resource Adapter for information about JCA Resource Adapter, including installation, configuration, and deployment instructions.
For the Order to Cash for BRM pre-built integration option, you must modify the JTA Transaction value, the Enterprise JavaBeans (EJB) BPELDeliveryBean value, and the SyncMaxWaitTime value.
To modify JTA Transaction value and EJB BPELDeliveryBean value:
Log in to the WebLogic Server console for the domain to which you will deploy Oracle AIA.
In the Change Center of the Administration Console, click Lock & Edit.
In the Domain Structure tree, select the domain name at the top of the tree.
Click the Configuration>JTA tab.
Set the value of the Timeout Seconds property to 3600.
Click Save.
In the Domain Structure tree, click Deployments.
In the Deployments table, expand soa-infra, then expand EJBs, and then select BPELDeliveryBean.
Click the Configuration tab.
In the Transaction Timeout field, enter 3000.
Click Save.
In the Change Center of the Administration Console, click Activate Changes.
To modify SyncMaxWaitTime values:
Log in to Oracle Enterprise Manager Fusion Middleware Control.
Expand the SOA folder and right-click soa-infra.
Select SOA Administration>BPEL Properties.
Click More BPEL Configuration Properties.
Set the value of syncMaxWaitTime property to 120.
Click Apply.
Note:
These are the recommended minimum timeout values. Your environment may require different values.
The Agent Assisted Billing Care pre-built integration requires an Oracle Data Integrator master repository and work repository. Although Oracle Data Integrator must be installed on the same machine as Oracle AIA, the Oracle Data Integrator repositories can be on different machines.
When setting up your SOA domain, you must connect to repositories created using Oracle Fusion Middleware Repository Creation Utility (RCU). You can use these repositories with your pre-built integrations, or you can use RCU to create new repositories.
Oracle recommends backing up the master and work repositories before configuring Oracle AIA.
For information about Oracle Data Integrator Master and Work repositories, see the following:
The discussion of administering repositories in Oracle Fusion Middleware Administering Oracle Data Integrator
The discussion of creating the master and work repository schema in Oracle Fusion Middleware Installing and Configuring Oracle Data Integrator
Perform the tasks described in this section if you are installing Oracle AIA in a clustered environment.
In a clustered environment, Oracle recommends using Node Manager to start managed servers. Before starting servers, configure the Node Manager startup properties.
To configure the Node Manager startup properties:
Open the nodemanager.properties file, typically located in the following directory:
MW_home/user_projects/domains/domain_name/nodemanager
Search for the following property:
StartScriptEnabled
Confirm that the value of the property is true. If it is not, change the value to true. For example:
StartScriptEnabled=true
Save and close the file.
In a web browser, log in to the WebLogic Server Administration Console.
In the Domain Structure panel, expand Environment and click Machines.
For each machine in the Machines table, do the following:
Select the machine name.
Select the Node Manager tab.
Check that the Listen Address field contains the fully qualified name of the system. For example:
system1.example.com
If the field contains localhost, replace it with the fully qualified name of the system.
Check that Listen Port contains a port number. For example:
5556
Click Save.
In the command line, navigate to the following directory:
domain_home/bin
Restart Node Manager using one of the following commands:
On UNIX systems:
sh startNodeManager.sh
On Windows systems:
startNodeManager.cmd
For more information about configuring and using Node Manager, see Oracle Fusion Middleware Administering Node Manager for Oracle WebLogic Server.
To restart servers that have pending configuration changes:
Log in to the WebLogic Server Administration Console.
In the Change Center panel, click View changes and restarts.
Select the Restart Checklist tab.
Select any servers in the cluster that appear in the table, including the administration server and managed servers, and click Restart.
If you are installing Oracle AIA on a cluster and are using Oracle HTTP Server, add the servers to the mod_wol_ohs.conf file.
To add the servers to the mod_wol_ohs.conf file:
Navigate to the following directory:
domain_home/config/fmwconfig/components/OHS/instances/componentName
Open the mod_wl_ohs.conf file.
Add the following code:
# WSM-PM <Location /wsm-pm> SetHandler weblogic-handler WebLogicCluster host1:port1,host2:port2 </Location> # SOA soa-infra app <Location /soa-infra> SetHandler weblogic-handler WebLogicCluster host1:port1,host2:port2 </Location> # SOA inspection.wsil <Location /inspection.wsil> SetHandler weblogic-handler WebLogicCluster host1:port1,host2:port2 </Location> # Worklist <Location /integration/> SetHandler weblogic-handler WebLogicCluster host1:port1,host2:port2 </Location> # B2B <Location /b2b> SetHandler weblogic-handler WebLogicCluster host1:port1,host2:port2 </Location> <Location /b2bconsole> SetHandler weblogic-handler WebLogicCluster host1:port1,host2:port2 </Location> # UMS <Location /sdpmessaging/ > SetHandler weblogic-handler WebLogicCluster host1:port1,host2:port2 </Location> # UMS WS <Location /ucs/messaging/webservice > SetHandler weblogic-handler WebLogicCluster host1:port1,host2:port2 </Location> # Default to-do taskflow <Location /DefaultToDoTaskFlow/> SetHandler weblogic-handler WebLogicCluster host1:port1,host2:port2 </Location> # Workflow <Location /workflow> SetHandler weblogic-handler WebLogicCluster host1:port1,host2:port2 </Location> #Required if attachments are added for workflow tasks <Location /ADFAttachmentHelper> SetHandler weblogic-handler WebLogicCluster host1:port1,host2:port2 </Location> # SOA composer application <Location /soa/composer> SetHandler weblogic-handler WebLogicCluster host1:port1,host2:port2 </Location> # BPM composer (ONLY FOR BPM Systems) <Location /bpm/composer > SetHandler weblogic-handler WebLogicCluster host1:port1,host2:port2 </Location> # BPM workspace (ONLY FOR BPM Systems) <Location /bpm/workspace > SetHandler weblogic-handler WebLogicCluster host1:port1,host2:port2 </Location> <Location /StoreFrontServiceHooks> SetHandler weblogic-handler WebLogicCluster host1:port1,host2:port2 WLLogFile /tmp/web_log.log </Location> <Location /StoreFrontService> SetHandler weblogic-handler WebLogicCluster host1:port1,host2:port2 WLLogFile /tmp/web_log.log </Location> <Location /StoreFrontModule> SetHandler weblogic-handler WebLogicCluster host1:port1,host2:port2 WLLogFile /tmp/web_log.log </Location> <Location /sce > SetHandler weblogic-handler WebLogicCluster host1:port1,host2:port2 </Location> <Location /AIAValidationSystemServlet> SetHandler weblogic-handler WebLogicCluster host1:port1,host2:port2 </Location> <Location /CustomerHub-matchfetch-context-root> SetHandler weblogic-handler WebLogicCluster host1:port1,host2:port2 WLLogFile /tmp/web_log.log </Location> <Location /bea_wls_internal> SetHandler weblogic-handler WebLogicCluster host1:port1,host2:port2 WLLogFile /tmp/web_log.log </Location> <Location /MirrorServlet> SetHandler weblogic-handler WebLogicCluster host1:port1,host2:port2 </Location> <Location /ws_utc > SetHandler weblogic-handler WebLogicCluster host1:port1,host2:port2 </Location>
where host1:port1 and host2:port2 are the managed servers in your Oracle Service Oriented Architecture (SOA) cluster and the ports on which they listen. Include all the managed servers in your SOA cluster in a comma-separated list.
Save and close the file.
To disable the WebLogic Server Web Services Endpoint Failover feature:
Log in to Oracle Enterprise Manager Fusion Middleware Control.
In the Target Navigation pane, expand the SOA folder, then right click soa-infra.
Select SOA Administration, and then select Common Properties.
At the bottom of the page, click More SOA Infra Advanced Configuration Properties.
On the Attributes tab, select WebservicesEndpointFailoverEnabled.
From the Value menu, select false.
Click Apply.
To configure your WebLogic servers for Oracle AIA in a clustered environment:
Log in to the WebLogic Server Administration Console.
In the Domain Structure pane, expand Environment and click Servers.
Do the following for the administration server and each managed server in the domain:
In the Servers table, select the server name.
Select the Protocols tab.
Select the HTTP tab.
Select the Enable Tunneling option.
Click Save.
Restart the administration server and all managed servers.
For pre-built integration options that include OSM, if your OSM Customer Order Management system is clustered, do the following:
In the Domain Structure pane, expand Services, then Messaging.
Select JMS Modules.
In the JMS Modules table, select AIAJMSModule.
In the Summary of Resources table, select the OSM link with the SAF Remote Context type.
In the URL field, add all OSM clustered nodes.
For example:
t3://osm1.example.com:7070,osm2.example.com:8070
Click Save.
For pre-built integration options that include OSM, if your OSM Service Order Management system is clustered, do the following:
In the Domain Structure pane, expand Services, then Messaging.
Select JMS Modules.
In the JMS Modules table, select AIAJMSModule.
In the Summary of Resources table, select the SOM link with the SAF Remote Context type.
In the URL field, add all OSM clustered nodes.
For example:
t3://osm1.example.com:7070,osm2.example.com:8070
Click Save.
Restart the cluster.
Before installing Oracle AIA, check that Node Manager and your SOA server are configured and running.
To check that Node Manager is running:
Log in to the WebLogic Server Administration Console.
In the Domain Structure panel, expand Environment and click Machines.
For each machine in the Machines table, do the following:
Select the machine name.
Select the Monitoring tab.
Check that the Status row says Reachable.
If Node Manager is not reachable, check that it is properly configured and start it as described in Oracle Fusion Middleware Administering Node Manager for Oracle WebLogic Server.
To check that your SOA server is running,
Log in to the WebLogic Server Administration Console.
In the Domain Structure panel, select the name of your domain.
Select the Monitoring tab.
In the Health Information table, confirm that the state of your SOA server is RUNNING.
If the SOA server is not running, start it as described in the discussion of using Node Manager to start a managed server in Oracle Fusion Middleware Administering Node Manager for Oracle WebLogic Server. Always start your SOA server using Node Manager.