Configuration File Changes

It is recommended that you use the Oracle Utilities Customer Care and Billing template and CM (Customer Modification) feature to make changes to these configuration files. This ensures that your modifications cannot be overwritten by future application patches.

Modify Files: ejb-jar.xml and ejb-weblogic-jar.xml

Location: Oracle Utilities Customer Care and Billing Enterprise Archive (EAR) file

The following needs to be observed while making configuration file changes:

• The Oracle Utilities Customer Care and Billing configuration files, ejb-jar.xml and ejb-weblogic-jar.xml, must be modified to configure Message Driven Beans(MDB). MDBs which receive messages from the integration queues. These files are part of the Oracle Utilities Customer Care and Billing Enterprise Archive (EAR) file.

• The Oracle Utilities Customer Care and Billing application needs to be redeployed after these changes are made.

• Managing Configuration Files: Configuration files such as config.xml, ejb-jar.xml, and ejb-weblogic-jar.xml are managed through template configuration files which reside in the environment's templates directory. When the initialSetup.sh script is executed, environment specific information is combined with the template to create the target file which is then deployed to the correct location. When the environment is started (spl.sh start), changes are automatically deployed to WebLogic.

• Templates:

• Extending existing templates: For CCB version 2.4.x: It is possible to extend existing templates with the use of Include template file(s) in the same location as the existing template. Using #ouaf_user_exit within the target template that is extended, additional configuration from the include template is processed and appended to the target template where the #ouaf_user_exit is present.

• Enabling changes for integration: To enable your changes for integration with Oracle Utilities Network Management System it is recommended that you first make a “CM” copy of the existing template and then make your changes to the CM version. If there are any problems with starting the application, delete the CM versions of the files and rerun initialSetup to regenerate and redeploy the original versions.

If you make CM versions of the template files and later install a patch which updates the base template, the CM version is not updated.

To create MDB to receive messages from the Oracle Utilities Customer Care and Billing inbound queue:

1. Create an MDB for each Oracle Utilities Customer Care and Billing inbound queue to receive messages and invoke the Oracle Utilities Customer Care and Billing service. For simplicity, we refer to the names of the target configuration files in the following examples. However, you should make your changes in the templates/cm_<target file>.include version of the file and then execute initalSetup.sh (Unix) or initalSetup.cmd (Windows) to deploy the generated file.

2. Create or modify the following files to configure the MDBs:

• cm_ejb-jar.xml.wls.jms_1.include

• cm_ejb-jar.xml.wls.jms_2.include

• cm_weblogic-ejb-jar.xml.jms.include

• cm_config.xml.jms.include

3. Add the <message-driven> and <container-transaction> tag for each inbound queue in the ejb-jar.xml files. Also, add a security role with role cisusers in the ejb-jar.xml files.

• cm_ejb-jar.xml.wls.jms_1

Example:

<!-Customer Sync Response Integration Point -->

<message-driven>

<description>MDB for OUCCBCustomerDataSyncResponse</description>

<display-name>OUCCBCustomerDataSyncResponse</display-name>

<ejb-name>OUCCBCustomerDataSyncResponse</ejb-name>

<ejb-class>com.splwg.ejb.mdb.MessageProcessor</ejb-class>

<messaging-type>javax.jms.MessageListener</messaging-type>

<transaction-type>Bean</transaction-type>

<message-destination-type>javax.jms.Queue</message-destination-type>

</message-driven>

• cm_ejb-jar.xml.wls.jms_2

Example:

<!-Customer Sync Response Integration Point -->

<assembly-descriptor>

<security-role>

<role-name>cisusers</role-name>

</security-role>

<container-transaction>

<ejb-name>OUCCBCustomerDataSyncResponse</ejb-name>

<method-name>onMessage</method-name>

</method>

<trans-attribute>NotSupported</trans-attribute>

</container-transaction>

</assembly-descriptor>

• Modify the cm_weblogic-ejb-jar.xml.jms.include file. Add the <weblogic-enterprise-bean> tag for each inbound queue.
The references in <weblogic-enterprise-bean> tag include:

• <ejb-name> - MDB name given in ejb-jar.xml.

• <destination-jndi-name> - JNDI name provided in JMS module ' Foreign server ' Foreign destination ' Local JNDI name.

• <connection-factory-jndi-name> - JNDI name provided in JMS module ' Foreign server ' Remote Connection Factory ' Local JNDI name.

cm_weblogic-ejb-jar.xml.jms.include example:

<weblogic-enterprise-bean>

<ejb-name>OUCCBCustomerDataSyncResponse</ejb-name>

<message-driven-descriptor>

<pool>

<max-beans-in-free-pool>5</max-beans-in-free-pool>

<initial-beans-in-free-pool>1</initial-beans-in-free-pool>

</pool>

<destination-jndi-name>jms/CCB-NMS/OUCCBCustomerDataSyncResponse</destination-jndi-name>

<connection-factory-jndi-name>jms/CCB-NMS/CCBNMSCF</connection-factory-jndi-name>

</message-driven-descriptor>

</weblogic-enterprise-bean>

• cm_config.xml.jms.include example:

<jms-system-resource>

<name>CCBNMSFJS</name>

<target>myserver</target>

<descriptor-file-name>jms/CCBNMSIntegrationModule-jms.xml</descriptor-file-name>

</jms-system-resource>