Installing the Integration

After setting the environment variables, open a command prompt and execute the installation scripts. This section provides additional details to supplement those steps.

• The installDB commands perform the followings tasks:

• Create the Error Handling user for the integration.

• Create the Error Handling tables and Error Lookup tables.

• Insert the seed data that is used for Error Handling scenarios that occur during the BPEL flow instances.

• The installWL commands perform the following tasks:

• Create the JDBC DataSource for the ErrorHandling Module.

• Create an outbound connection pool instance for the database by updating the DBAdapter_CCB2-MDM2.rar file.

• Create JMS server/JMS module/JMS connection pool/JMS persistence store/JMS queues and assigns the error queues to the interface queues.

• Create JMS outbound connections to both Oracle Utilities Customer Care and Billing and Oracle Utilities Meter Data Management by updating the JMSAdapter_CCB2-MDM2.rar file.

• Create the csf key for the integration.
Oracle Utilities Meter Data Management and Oracle Utilities Customer Care and Billing.

• CCB2-MDM2_MDM2

• CCB2-MDM2_CCB2

The installSOA commands perform the following tasks:

• Update the MDS repository with all artifacts.

• Create the application partition where the composites are deployed.
For example: CCB2-MDM2.

• Compile and deploy all composites.

Environmental Variables

export ORACLE_HOME=/scratch/gbuora/SOA14c/Oracle_Home export SOA_HOME=$ORACLE_HOME/soa

export MW_HOME=$ORACLE_HOME # If you want to keep MW_HOME for compatibility

# Source the WebLogic environment setup script from new location source $ORACLE_HOME/wlserver/server/bin/setWLSEnv.sh

# Set product home and cd into its bin

export PRODUCT_HOME=/scratch/gbuora/SOA14c/product_homes/CCB2-MDM2 # expor class path of ant-contrib.jar

export CLASSPATH=/scratch/gbuora/ant-contrib.jar:$CLASSPATH cd $PRODUCT_HOME/bin

Installation Commands

ant -f InstallBuild.xml installDB -DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml | tee InstallDB.log

ant -f InstallBuild.xml installWL -DinstallJMSWrappers=true -DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml | tee InstallWL_withwrapps.log

ant -f InstallBuild.xml installSOA -DinstallJMSWrappers=true -DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml | tee InstallSOA_withwrappers.log

Note that the following modified commands (which include "-DinstallJMSWrappers=true") are to be used for JMS Wrapper functionality.

Linux:

• cd $PRODUCT_HOME/bin

ant -f InstallBuild.xml installDB -DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml -l installDB.log

• cd $PRODUCT_HOME/bin

ant -f InstallBuild.xml installWL -DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml -l installWL.log

• cd $PRODUCT_HOME/bin

ant -f InstallBuild.xml installSOA -DinstallJMSWrappers=true -DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml -l installSOA.log

Windows:

• cd %PRODUCT_HOME%\bin

ant -f InstallBuild.xml installDB -DInstallProperties=%PRODUCT_HOME%/config/InstallProperties.xml -l installDB.log

• cd %PRODUCT_HOME%\bin

ant -f InstallBuild.xml installWL -DInstallProperties=%PRODUCT_HOME%/config/InstallProperties.xml -l installWL.log

• cd %PRODUCT_HOME%\bin

ant -f InstallBuild.xml installSOA -DinstallJMSWrappers=true -DInstallProperties=%PRODUCT_HOME%/config/InstallProperties.xml -l installSOA.log

This provides the JMS wrappers over the JMS queues and exposes them as webservices, removing the dependency on the Message Driven Beans (MDBs) in the edge applications. The participating applications can directly interact with integration using the webservice endpoints exposed for respective integration flows.

In this integration, asynchronous processes use queues to send and receive messages from the edge applications. By default, the edge applications need to setup their JMS and MDB configuration to send and receive messages to and from the queue.