Oracle Utilities Customer Care and Billing Integration to Oracle Utilities Meter Data Management

Implementation Guide Oracle Utilities Customer Care and Billing Integration to Oracle Utilities Meter Data Management Installation Guide Release 12.1 Media Pack E64681-01 June 2015

Oracle Utilities Customer Care and Billing Integration to Oracle Utilities Meter Data Management Installation Guide, Release 12.1 Media Pack Copyright 2015, Oracle and/or its affiliates. All rights reserved. Primary Author: Oracle Corporation This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government. This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group. This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents Overview... 1-1 Additional Resources... 1-1 Abbreviations... 1-2 Installation... 2-1 Integration Pack Software Requirements... 2-1 Participating Applications... 2-1 Oracle SOA/Weblogic Server... 2-1 Pre-Installation Tasks... 2-2 Installation Steps... 2-2 Installing the Integration... 2-9 Post-Installation Checklist... 2-11 Verifying JMS and JDBC Configuration... 2-11 Verifying Composites in Enterprise Manager... 2-14 Verifying the csf-key Generation... 2-15 Verifying the User Messaging Service List... 2-15 Configuring Edge Applications... 2-16 Deploying/Undeploying Individual Composites... 3-1 Undeploying Composites... 3-1 Deploying Individual Composites... 3-2 Connection Mapping... 3-2 MDS Folders... 4-1 Undeploying MDS Folder... 4-1 Deploying MDS Folder... 4-2 Uninstalling the Integration... 5-1 Troubleshooting the Integration... 6-1 Password Expiry for Database... 6-1 Security Policies... 6-1 Contents - i

Chapter 1 Overview Additional Resources This guide describes the installation steps that must be completed before Oracle Utilities Meter Data Management can be integrated with Oracle Utilities Customer Care and Billing. For more information regarding this integration, foundation technology and the edge applications, refer to the following documents: Topic Oracle Utilities Customer Care and Billing Integration to Oracle Utilities Meter Data Management Release 12.1 Media Pack Release Notes Oracle Utilities Customer Care and Billing Integration to Oracle Utilities Meter Data Management Release 12.1 Media Pack Implementation Guide Description Same folder as this document, with the distribution for this product or the OTN page: http://www.oracle.com/technetwork/apps-tech/ utilities/documentation/index.html Edge application documentation: Oracle Utilities Customer Care and Billing documentation Oracle Utilities Meter Data Management documentation SOA Suite 12c documentation Installing SOA Suite 12c with Enterprise Manager 12.1.3.0.0 on Weblogic Server 12c (12.1.3.0.0) Refer to the Oracle applications documentation page: http://www.oracle.com/technetwork/apps-tech/ utilities/documentation/index.html Refer to the SOA documentation at: http://www.oracle.com/technetwork/middleware/ soasuite/documentation/index.html See the SOA documentation at: http://www.oracle.com/technetwork/middleware/ soasuite/documentation/index.html#121300 Overview 1-1

Topic Oracle Support Visit regularly to stay up to date with the latest updates to this integration Oracle University for training opportunities Description https://support.oracle.com http://education.oracle.com/ Abbreviations Abbreviations used in this guide are listed below: CCB - Oracle Utilities Customer Care and Billing MDM - Oracle Utilities Meter Data Management MDS - Metadata Store DVM - Domain Value Map AIA - Application Integration Architecture SOA - Service Oriented Architecture EBF - Enterprise Business Flow Overview 1-2

Chapter 2 Installation The following sections describe the settings and requirements for a successful installation of Oracle Utilities Customer Care and Billing Integration to Oracle Utilities Meter Data Management Media Pack. This section provides information on the following: Integration Pack Software Requirements Pre-Installation Tasks Installation Steps Post-Installation Checklist Configuring Edge Applications 2.1 Integration Pack Software Requirements The following software and platforms must be installed and configured before the integration pack can be installed. Note: For complete details, refer to the product specific installation instructions. 2.1.1 Participating Applications Oracle Utilities Customer Care and Billing v2.3.1.1 or higher installed on an Oracle database with the latest supported service pack. Oracle Utilities Meter Data Management v2.0.1.1 or higher installed on an Oracle database with the latest supported service pack. 2.1.2 Oracle SOA/Weblogic Server Oracle SOA suite 12c with Oracle Enterprise Manager 12.1.3.0.0 on WebLogic Server 12.1.3.0.0. Note: This integration does not require AIA Foundation Pack to be installed. Installation 2-1

2.2 Pre-Installation Tasks 2.3 Installation Steps Pre-Installation Tasks The following tasks should be completed before you install the integration media pack: 1. Ensure that Oracle SOA Suite 12c is installed and running. For more information, refer to the documentation at http://www.oracle.com/ technetwork/middleware/soasuite/documentation/index.html#121300 2. Login to the WebLogic Server Administration console to confirm there are no changes in Pending Activation status. Complete this step to verify that the WebLogic Server is in a healthy state. If any items are in Pending Activation status, then there is likely an issue on the server. All issues must be resolved before you can proceed with the installation. 3. Start Node Manager, if not already running. 4. Restart the Enterprise Manager and the WebLogic Admin server. 5. Make sure the WebLogic Admin server, SOA server, and Node Manager are up and running. Perform the following steps to complete the installation procedure: 1. Download the installation CCB2-MDM2.zip file from Oracle Software Delivery Cloud (http://edelivery.oracle.com/). Note: For specific instructions about installing this integration on non- Windows/ Linux platforms see Oracle Support Knowledge article ID 1349320.1. 2. Extract the zip file to get the installation folder. This folder includes subfolders such as bin, config, Install, MDS-Artifacts, and services. Installation 2-2

Installation Steps CCB2 MDM2 Product Home Directory 3. Set the following environment variables for Linux and Windows OS: Variable Example Linux and Windows OS MW_HOME SOA_HOME PRODUCT_HOME XXX/Middleware/Oracle_Home XXX/Middleware/Oracle_Home/soa Directory where CCB2-MDM2.zip is extracted. Example: Linux: PRODUCT_HOME=/slot/oracle/CCB2-MDM2 Windows: PRODUCT_HOME=D:\Oracle\CCB2-MDM2 Installation 2-3

Installation Steps Note: The syntax for PRODUCT_HOME changes depending on whether you are installing on Linux or Windows. The following sections refer to this as $PRODUCT_HOME in Linux and it should be referred to as %PRODUCT_HOME% in Windows. If you are using Windows, replace $PRODUCT_HOME with %PRODUCT_HOME% throughout the document. Note: As installation commands and arguments are lengthy, please copy the installation commands in a notepad and ensure that the command is formatted correctly without any syntax or formatting errors. The following commands (setwlsenv.sh on Linux and setwlsenv.bat on Windows) set the environment variables used for executing the installation scripts. Linux: source $MW_HOME/wlserver/server/bin/setWLSEnv.sh Windows: cd %MW_HOME%\wlsserver\server\bin\ setwlsenv.cmd Below is an example to set up environment variables in a typical installation: Linux: export MW_HOME=/Oracle/Middleware/Oracle_Home export SOA_HOME=$MW_HOME/soa export PRODUCT_HOME=/Product_Homes/CCB2-MDM2 source $MW_HOME/wlserver/server/bin/setWLSEnv.sh Windows: SET MW_HOME=C:\Oracle\Middleware\Oracle_Home SET SOA_HOME=%MW_HOME%\soa SET PRODUCT_HOME=C:\Product_Homes\CCB2-MDM2 cd %MW_HOME%/wlserver/server/bin/ setwlsenv.cmd InstallProperties.xml is an XML file. Ensure you follow XML editing standards while editing InstallProperties.xml. All XML elements need to be closed properly. XML element in InstallProperties.xml file does not contain any attribute. The following table lists the properties available in the InstallProperties.xml file along with their usage. The default values are specified wherever applicable. Note: If the installation fails because of incorrect values defined in the InstallProperties.xml file, run uninstall, populate the correct values, and then run install again. Property Description Example <config> <modulename> Name of the integration module. Default: CCB2-MDM2 Do not change this value. <CCB-MDM2> Workflow Notification Properties <WorkFlow.Notification> Installation 2-4

Installation Steps Property Description Example <from.emailid> Email ID which should be set in the From property of Workflow Notification bean. Admin.user@yourdomain.com <mode> Type of notification mode EMAIL CCB Application Information <CCB> <Protocol> CCB Service Protocol http <Host> Host name of the CCB server. CCB_HOST.yourdomain.com <Port> Port number of the CCB server CCB_PORT_NO <ContextRoot> CCB service context root CCB_CONTEXT_ROOT_NA ME <ApplicationUserName> Application login username CCBUSER <ApplicationPassword> Application login password CCBPWD MDM Application Information <MDM> <Protocol> MDM service protocol http <Host> Host name of the MDM server MDM_HOST.yourdomain.com <Port> Port number of the MDM server MDM_PORT_NO <ContextRoot> MDM service context root MDM_CONTEXT_ROOT_N AME <ApplicationUsername> Application login username MDMUSER <ApplicationPassword> Application login password MDMPWD SOA Information <config> <SOA> Admin Server Information <AdminServer> <hostname> <portnumber> <servername> <username> Host name of the server where admin server hosting SOA suite is installed. Port number the admin server (hosting SOA suite) is listening to. Admin server name (hosting SOA suite) User name used to log in as an Admin server (hosting SOA suite) administrator. adminserver.example.oracle.com 7001 AdminServer weblogic Installation 2-5

Installation Steps Property Description Example <password> <domainname> Managed Server Information <ManagedServer> <hostname> <portnumber> <servername> <username> <password> Password used to log in as an Admin server (hosting SOA suite) administrator. WebLogic domain name hosting SOA suite. Host name of the server where managed server (hosting SOA suite) is installed. Port number the managed server (hosting SOA suite) is listening to. Managed server name (hosting SOA suite) User name used to log in to managed server (hosting SOA suite) as an administrator. Password used to log in to managed server (hosting SOA suite) as an administrator. soa_domain managedserver.example.oracle.c om 8001 Managedserver1 weblogic Oracle HTTP Server Information <OHS> In case of non-cluster environment these properties would be same as <ManagedServer> values <hostname> Give a HTTP server host name Oracle http server where cluster is managed <Portnumber> <servernames> MDS DB Information <mdsconfig> <mdsdbusername> <mdsdbuserpassword> <mdsdbhostname> Give a HTTP server port number Provide the list of managed server(s) User name used to log in to MDS schema. Password used to log in to MDS schema. Host name of the server hosting the database containing MDS schema. Port number of the Oracle http server In case of multiple managed servers, provide comma separated values. Example: soa_server1, soa_server2 XXX_MDS Db.hostname.oracle.com Installation 2-6

Installation Steps Property Description Example <mdsdbportnumber> <mdsdbsid> JMS Information <JMS> Port number of the database containing MDS schema. SID of the database containing MDS schema. 1521 SID <servername> JMS server name Default: CCB2MDM2JS Note: Do not change this value <ModuleName> JMS module name Default: CCB2MDM2JM Note: Do not change this value <SubDeploymentName> Sub deployment name for JMS queues Default: CCB2MDM2SD Note: Do not change this value <JMSServerTarget> WebLogic managed server name For cluster environment, give only one managed server name under the cluster <JMSModuleTargets> WebLogic managed server name For cluster environment give comma separated managed server names under the cluster or multiple cluster names <PersitentStoreName> JMS persistent store name Default: CCB2MDM2FS <PersitentStoreType> <PersistentStoreFilename> JMS persistent store type (FileStores or DBStore). Deployment script supports a file Directory path name where the file based persistent store should be created. Default: FileStores Product_Homes/CCB2- MDM2/bin <JMSCFName> JMS connection factory name OUCCB2OUMDM2Connectio nfactory <JMSCFJNDI> Email Information <MailAccessProtocol> <OutgoingDefaultFromAddr> <OutgoingMailServer> <OutgoingMailServerPort> JMS Connection factoy JNDI name E-mail receiving protocol. The possible values are IMAP and POP3. Required only if e-mail is supported on the driver instance. The default FROM address (if one is not provided in the outgoing message) The name of the SMTP server. Mandatory only if an e-mail needs to be sent. The port number of SMTP server. jms/ OUCCB2OUMDM2Connectio nfactory IMAP mail.id@yourdomain.com host.yourdomain.com 465 Installation 2-7

Installation Steps Property Description Example <OutgoingMailServerSecurity> <OutgoingUsername> <Outgoingpassword> <IncomingUserIDs> <IncomingUserPasswords> <applicationname> The security used by SMTP server. Possible values are None, TLS, and SSL. Default value is None. The user name used for SMTP authentication. Required only if SMTP authentication is supported by the SMTP server The password used for SMTP authentication. Required only if SMTP authentication is supported by the SMTP server. The list of user names of the mail accounts the driver instance is polling from. Each name must be separated by a comma. Required only if e-mail receiving is supported on the driver instance. The list of passwords corresponding to the user names. Each password is separated by a comma and must reside in the same position in the list as their corresponding user name appears on the user names list. Required only if e-mail receiving is supported on the driver instance. This is the application name for the user messaging service SSL mail.id@ yourdomain.com Yourpassword mail.id@ yourdomain.com Yourpassword usermessaging driver-email Error Handling Database Information <config> <EH> <dba.dbusername> <dba.dbuserpassword> <dbusername> User name used to log in as a database administrator (DBA). This database hosts the schema required for CCB2-MDM2 integration. Password used to log in as a database administrator (DBA). This database hosts the schema required for CCB2-MDM2 integration. User name used to log in to CCB2-MDM2 schema for CCB2-MDM2 integration. This user can be automatically created by the install (set dbuser.createflag to true) or manually outside the install process. System CCB2MDM2User Installation 2-8

Installation Steps Property Description Example <dbuserpassword> <dbuser.createflag> <dbhostname> <dbportnumber> <dbsid> Password used to log in to CCB2-MDM2 schema for CCB2-MDM2 integration. Flag specifying whether to create a new schema or use the existing schema for CCB2-MDM2 integration. If the schema is created manually outside of the installation process, then set this value to false. Else, set the value to true, if the installation script should automatically create the schema. Valid values: true or false (this is case sensitive) Database host name used for CCB2-MDM2 integration. Database port number used for CCB2-MDM2 integration. Database SID used for CCB2- MDM2 integration. true Db.sample.oracle.com 1521 SID NOTE: If the dbuser.createflag is set to false, the schema needed for CCB2-MDM2 integration error handling will not be automatically created by the install. The schema needs to be created manually before running the install. When creating the user manually, grant connect and resource to the user. Also note the following: $PRODUCT_HOME/Install/util/ant folder contains all the ant build scripts. $PRODUCT_HOME/bin/InstallBuild.xml is used to install CCB2-MDM2 integration code. $PRODUCT_HOME/bin/UnInstallBuild.xml is used to uninstall CCB2- MDM2 integration code. $PRODUCT_HOME/bin/DeployUndeployUtility.xml is used to deploy/ undeploy individual composite/ MDS folder and then restart the managed server. Note: The installation and uninstallation process may take several minutes or more to complete. Stand by until the install and uninstall processes are complete. 2.3.1 Installing the Integration After setting the environment variables, open a Command prompt and execute the following installation scripts in Linux and Windows respectively. Note that the installation process is divided into three steps. 1. Step 1: Execute the following commands to create the database objects required for the Error Handling module and the database artifacts required for the integration. Installation 2-9

Installation Steps Linux: cd $PRODUCT_HOME/bin ant -f InstallBuild.xml installdb - DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml l installdb.log Windows: cd %PRODUCT_HOME%\bin ant -f InstallBuild.xml installdb - DInstallProperties=%PRODUCT_HOME%/config/InstallProperties.xml l installdb.log 2. Step 2: Execute the following commands at the command prompt: Linux cd $PRODUCT_HOME/bin ant -f InstallBuild.xml installwl - DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml - l installwl.log Windows cd %PRODUCT_HOME%\bin ant -f InstallBuild.xml installwl - DInstallProperties=%PRODUCT_HOME%/config/InstallProperties.xml -l installwl.log These commands perform the following tasks: Creates the JDBC DataSource for the ErrorHandling Module. Creates an outbound connection pool instance for the database by updating the DBAdapter_CCB2-MDM2.rar file. Creates JMS server/jms module/jms connection pool/jms persistence store/ JMS queues and assigns the error queues to the interface queues. Creates 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. Creates the csf key for Oracle Utilities Meter Data Management by creating CCB2-MDM2_MDM2. After executing the commands mentioned above, bounce the managed server and admin server manually. 3. Step 3: Execute these commands at the command prompt: Linux cd $PRODUCT_HOME/bin ant -f InstallBuild.xml installsoa - DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml - l installsoa.log Windows cd %PRODUCT_HOME%\bin ant -f InstallBuild.xml installsoa - DInstallProperties=%PRODUCT_HOME%/config/InstallProperties.xml -l installsoa.log Installation 2-10

Post-Installation Checklist These 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 2.4 Post-Installation Checklist After running the installation scripts, follow these steps to complete the installation. 1. Verify that all the JMS and JDBC resources were created. See Verifying JMS and JDBC Configuration for the instructions. 2. Check if the csf-keys are generated. See Verifying the csf-key Generation for the instructions. 3. Review the logs under $MW_HOME/user_projects/domains/soa_domain/ servers/<managed-server-name>/logs to check for deployment errors. 4. Verify if all the composites in Enterprise Manager are deployed. See Verifying Composites in Enterprise Manager for the steps. 5. Verify if the user messaging service is active. See Verifying the User Messaging Service List for more details. 2.4.1 Verifying JMS and JDBC Configuration Perform the following steps to verify JMS and JDBC Configuration: 1. Open a WebLogic Admin console and navigate to Home JMS Modules CCB2MDM2JM. 2. Verify if the queues and the OUCCB2OUMDM2ConnectionFactory are created successfully. Queues OUCCB2SPSyncRequest OUCCB2SPSyncRequestError OUCCB2SPSyncResponse OUCCB2SPSyncResponseError OUCCB2SASyncRequest OUCCB2SASyncRequestError OUCCB2SASyncResponse OUCCB2SASyncResponseError OUCCB2BatchBDRequest OUCCB2BatchBDRequestError OUCCB2BatchBDResponse OUCCB2BatchBDResponseError Installation 2-11

Post-Installation Checklist Queues OUCCB2OnlineBDRequest OUCCB2OnlineBDRequestError OUCCB2OnlineBDResponse OUCCB2OnlineBDResponseError OUCCB2ReplReadRequest OUCCB2ReplReadRequestError OUCCB2PersonSyncRequest OUCCB2PersonSyncRequestError OUCCB2PersonSyncResponse OUCCB2PersonSyncResponseError OUCCB2MeterSyncRequest OUCCB2MeterSyncRequestError OUCCB2MeterSyncResponse OUCCB2MeterSyncResponseError OUCCB2MeterConfigSyncRequest OUCCB2MeterConfigSyncRequestError OUCCB2MeterConfigSyncResponse OUCCB2MeterConfigSyncResponseError OUCCB2SPMeterHistSyncRequest OUCCB2SPMeterHistSyncRequestError OUCCB2SPMeterHistSyncResponse OUCCB2SPMeterHistSyncResponseError OUMDM2SPSyncRequest OUMDM2SPSyncRequestError OUMDM2SPSyncResponse OUMDM2SPSyncResponseError OUMDM2SASyncRequest OUMDM2SASyncRequestError OUMDM2SASyncResponse OUMDM2SASyncResponseError OUMDM2BatchBDRequest OUMDM2BatchBDRequestError OUMDM2BatchBDResponse OUMDM2BatchBDResponseError OUMDM2OnlineBDRequest Installation 2-12

Post-Installation Checklist Queues OUMDM2OnlineBDRequestError OUMDM2OnlineBDResponse OUMDM2OnlineBDResponseError OUMDM2ReplReadRequest OUMDM2ReplReadRequestError OUMDM2PersonSyncRequest OUMDM2PersonSyncRequestError OUMDM2PersonSyncResponse OUMDM2PersonSyncResponseError OUMDM2MeterSyncRequest OUMDM2MeterSyncRequestError OUMDM2MeterSyncResponse OUMDM2MeterSyncResponseError OUMDM2MeterConfigSyncRequest OUMDM2MeterConfigSyncRequestError OUMDM2MeterConfigSyncResponse OUMDM2MeterConfigSyncResponseError OUMDM2SPMeterHistSyncRequest OUMDM2SPMeterHistSyncRequestError OUMDM2SPMeterHistSyncResponse OUMDM2SPMeterHistSyncResponseError OUCCB2MeterReadSyncRequest OUCCB2MeterReadSyncRequestError OUCCB2MeterReadSyncResponse OUCCB2MeterReadSyncResponseError OUMDM2MeterReadSyncRequest OUMDM2MeterReadSyncRequestError OUMDM2MeterReadSyncResponse OUMDM2MeterReadSyncResponseError OUCCB2OUMDM2ConnectionFactory Note: If JMSMODULENAME!JMSQUEUENAME doesn t exist in the rows of the Destinations table, it means there are problems with the installation. 3. Navigate to Services > Persistent Stores > CCB2MDM2FS. 4. Verify that the JMSFileStorePath is correct and the directory has write permissions. Installation 2-13

Post-Installation Checklist To verify the JDBC configuration, follow these steps: 1. Navigate to Home > Deployments. 2. Verify that DbAdapter_CCB2-MDM2.rar is deployed, and is in Active state. 3. Verify the eis/db/ccb2-mdm2errorhandling connection factory details to ensure the connection-factory location matches with that defined in the JCA files. Follow these steps: a. Click DbAdapter_CCB2-MDM2 on the Deployments table. b. On the Configuration tab, click Outbound Connection Pools. c. Expand javax.resource.cci.connectionfactory to check the eis/db/ccb2- MDM2ErrorHandling connection factory instance. 4. Ensure the database details are as required: a. On the left pane, navigate to Services > Data Sources. b. Click the CCB2-MDM2EHDS data source to check the JNDI Name: jdbc/ccb2- MDM2EHDS. 3. Click Connection Pool to check the URL and properties. 4. Click Monitoring, click Testing, select the target server, and then click Test Data Source. Check if the data source has been configured successfully. 2.4.2 Verifying Composites in Enterprise Manager Verify that the CCB2-MDM2 partition was created with all the composites deployed. Perform the following steps to verify composites in Enterprise Manager: 1. Login to Enterprise Manager. 2. Expand SOA soa-infra CCB2-MDM2 partition. 3. Verify that all the composites are deployed and are in an active state. Composites List: ErrorHandling ErrorHandlingHumanIntervention ErrorProcessingDetail ErrorProcessingMaster OUCCB2OUMDM2BatchBDReqEBF OUCCB2OUMDM2HighLowReadReqEBF OUCCB2OUMDM2MeterConfigSyncReqEBF OUCCB2OUMDM2MeterReadSyncReqEBF OUCCB2OUMDM2MeterSyncReqEBF OUCCB2OUMDM2OnlineBDReqEBF OUCCB2OUMDM2PersonSyncReqEBF OUCCB2OUMDM2SASyncReqEBF OUCCB2OUMDM2SPMeterHistSyncReqEBF OUCCB2OUMDM2SPSyncReqEBF Installation 2-14

Post-Installation Checklist OUCCB2OUMDM2UsageAdjustmentReqEBF OUCCB2OUMDM2SSUsageReqEBF OUMDM2OUCCB2BatchBDRespEBF OUMDM2OUCCB2MeterConfigSyncRespEBF OUMDM2OUCCB2MeterReadSyncRespEBF OUMDM2OUCCB2MeterSyncRespEBF OUMDM2OUCCB2OnlineBDRespEBF OUMDM2OUCCB2PersonSyncRespEBF OUMDM2OUCCB2ReplReadReqEBF OUMDM2OUCCB2SASyncRespEBF OUMDM2OUCCB2SPMeterHistSyncRespEBF OUMDM2OUCCB2SPSyncRespEBF PurgeIntegrationErrorStore UpdateIntegrationErrorLookupTable 2.4.3 Verifying the csf-key Generation To verify if the csf-key is created successfully, perform the following steps: 1. Login to the Enterprise Manager console. 2. Navigate to WebLogic_Domain > soa_domain. 3. Right-click soa_domain, and then select Security > Credentials. 4. Expand the oracle.wsm.security map. 5. Check if the CCB2-MDM2_MDM2 key is available. 2.4.4 Verifying the User Messaging Service List To verify the user messaging service list, follow these steps: 1. In the WebLogic Administration console, navigate to Deployments. 2. Verify if the usermessagingdriver-email email driver is Active. 3. If not, click usermessagingdriver-email > Targets > <managed server>. For example: soa_server1 Then, select Yes and click Activate Changes. 4. In the WebLogic Enterprise Manager console, navigate to soa-infra (<managed server>). 5. Right-click the soa-infra (<managed server>) node, select SOA Administration, and then select Workflow Properties. 6. Ensure that the Notification Mode under Workflow Properties is set to Email. 7. Navigate to the User Messaging Service node, and select the usermessagingserver (<managed server>) entry. For example: usermessagingserver (soa_server1) You can see that the email driver is already enabled. Installation 2-15

Configuring Edge Applications 8. Click Configure Driver to check the e-mail driver properties and view the specific configuration details as shown in the figure below. 2.5 Configuring Edge Applications Configure Oracle Utilities Customer Care and Billing and Oracle Utilities Meter Data Management according to the guidelines in the Oracle Utilities Customer Care and Billing Integration to Oracle Utilities Meter Data Management Release 12.1 Media Pack Implementation Guide. Installation 2-16

Chapter 3 Deploying/Undeploying Individual Composites This section describes how to deploy/ undeploy individual composites for incremental builds or patches. It includes the following sections: Undeploying Composites Deploying Individual Composites Connection Mapping 3.1 Undeploying Composites If the composite being deployed involves changes made to the MDS artifacts, you must first undeploy the composite. 1. Open a Command prompt and execute the following commands for Linux and Windows respectively: Linux: cd $PRODUCT_HOME/bin ant -f DeployUndeployUtility.xml - DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml UnDeployComposite Windows: cd %PRODUCT_HOME%\bin ant -f DeployUndeployUtility.xml - DInstallProperties=%PRODUCT_HOME%/ config/installproperties.xml UnDeployComposite 2. Validate the following parameters when prompted with default values during deployment. Press ENTER to use the default prompted value. Composite Name: Name of the composite to be undeployed to SOA server. This parameter does not have a default value. Composite folder location: The folder name should be an absolute path, beginning with <PRODUCT_HOME>/services/industry/Utilities/ <EBF/utility>. For example: If you are planning to undeploy the composite from <PRODUCT_HOME>/services/industry/Utilities/EBF, then pass <PRODUCT_HOME>/services/industry/Utilities/EBF to this property. Deploying/Undeploying Individual Composites 3-1

Deploying Individual Composites The default value for this property is %PRODUCT_HOME%/services/ industry/utilities/ebf, as most of the business-specific composites reside in this folder. SOA Partition Name: The SOA partition name from where the composite should be undeployed. 3. Press Enter to use the default prompted value. 3.2 Deploying Individual Composites Perform the following steps to deploy individual composites: 1. Execute the following commands in the Command prompt for Linux and Windows respectively: Linux: cd $PRODUCT_HOME/bin ant -f DeployUndeployUtility.xml - DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml DeployComposite Windows: cd %PRODUCT_HOME%\bin ant -f DeployUndeployUtility.xml - DInstallProperties=%PRODUCT_HOME%/ config/installproperties.xml DeployComposite 2. Validate the following parameters when prompted with default values during deployment. Press ENTER to use the default prompted value. Composite Name: Name of the composite to be deployed to SOA server. This parameter does not have a default value. For example: OUCCB2OUMDM2OnlineBDRequestEBF Composite folder location: The folder name should be an absolute path beginning with %PRODUCT_HOME%/services/industry/Utilities/ <EBF/utility>. For example: Deploy the composite from%product_home%/services/ industry/utilities/ebf, then pass %PRODUCT_HOME%/services/ industry/utilities/ebf to this property. The default value for this property is %PRODUCT_HOME%/services/ industry/utilities/ebf, as most of the business-specific composites reside in this folder. Partition Name: The SOA partition name to which the composite should be deployed. 3. Press Enter to use the default prompted value. Note: Refer to Verifying Composites in Enterprise Manager to see the composites for this integration. 3.3 Connection Mapping All connections are mapped/ grouped by the edge applications in the <PRODUCT_HOME>/config/ConnectionMappings.xml file. Deploying/Undeploying Individual Composites 3-2

Connection Mapping The ConnectionMapping.xml file is used for internal reference purposes only and hence the entries should not be modified. This helps to de-tokenize the Oracle Utilities Meter Data Management URLs in the $PRODUCT_HOME/MDS-Artifacts/CCB2-MDM2/ AIAMetaData/config/ConfigurationProperties.xml file Deploying/Undeploying Individual Composites 3-3

Chapter 4 MDS Folders This section describes how to deploy and undeploy individual MDS folders for incremental builds or patches, including: Undeploying MDS Folder Deploying MDS Folder 4.1 Undeploying MDS Folder To undeploy a particular folder from MDS, execute the following commands and then pass the folder name to be undeployed. 1. Open a Command prompt and execute the following commands for Linux and Windows respectively. These commands undeploy a folder under $PRODUCT_HOME/MDS-Artifacts from the MDS repository. Linux: cd $PRODUCT_HOME/bin ant -f DeployUndeployUtility.xml - DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml UnDeployMDS Windows: cd %PRODUCT_HOME%\bin ant -f DeployUndeployUtility.xml - DInstallProperties=%PRODUCT_HOME%/config/InstallProperties.xml UnDeployMDS 2. Validate the following parameters when prompted with default values during undeployment. Press ENTER to use the default prompted value. MDS Folder Name: Name of the folder to be undeployed from MDS repository. The folder name should be a relative path inside %PRODUCT_HOME%/MDS-Artifacts, beginning with CCB2-MDM2. For example: To undeploy %PRODUCT_HOME%/MDS-Artifacts/CCB2- MDM2/AIAMetaData/dvm pass CCB2-MDM2/AIAMetaData/dvm as the MDS folder name. Note: Use this command to perform only folder-level undeployment. The command does not support file-level undeployment. MDS Folders 4-1

4.2 Deploying MDS Folder Perform the following steps to deploy MDS folder: Deploying MDS Folder 1. Open a Command prompt and execute the following commands in Linux and Windows respectively: Linux: cd $PRODUCT_HOME/bin ant -f DeployUndeployUtility.xml - DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml DeployMDS Windows: cd %PRODUCT_HOME%\bin ant -f DeployUndeployUtility.xml - DInstallProperties=%PRODUCT_HOME%/config/InstallProperties.xml DeployMDS Validate the following parameters when prompted with default values during deployment. Press ENTER to use the default prompted value. MDS Folder Name: Name of folder to be deployed from MDS repository. The folder name should be a relative path inside %PRODUCT_HOME%/MDS- Artifacts, beginning CCB2-MDM2. Examples of deploying MDS are shown below: Under the CCB2-MDM2 folder is the MDS-Artifacts subfolder which contains all the files that can be deployed to MDS. DVM changes: When new DVM values are added to a DVM file(s), the DVM folder must be updated in MDS. This command will not only deploy the file(s) that were changed but the whole DVM folder. Pass CCB2-MDM2/AIAMetaData/dvm as the MDS folder name and it will deploy the whole DVM folder to MDS. Note: When the DVMs are updated from the SOA composer, ensure that the values are updated in the /MDS-Artifacts/CCB2-MDM2/ AIAMetaData/dvm folder. Else, the changes made from the composer will be overridden by the PRODUCT_HOME values. MDS Folders 4-2

Deploying MDS Folder Custom schema changes: If custom elements are added to the CCB or MDM schemas or both, the ApplicationObjectLibrary folder must be updated in MDS. Pass CCB2-MDM2/AIAMetaData/ApplicationObjectLibrary to deploy the schema folders or pass CCB2-MDM2/AIAMetaData/ ApplicationObjectLibrary/OUCCB2 to deploy only the CCB schema folder or change OUCCB2 and put OUMDM2 to deploy only the MDM schema folder. Concrete WSDL changes for extensions If extension service needs to be called by a process and the concrete WSDL is updated, the ExtensionServiceLibrary folder must be updated in MDS. Pass CCB2-MDM2/AIAMetaData/ExtensionServiceLibrary to deploy the extension service library folders or pass CCB2-MDM2/AIAMetaData/ ApplicationObjectLibrary/OUCCB2 to deploy only the CCB extension library folder or change OUCCB2 and put OUMDM2 to deploy only the MDM extension service library. Note: Use this command to perform only folder-level deployment. The command does not support file-level deployment. MDS Folders 4-3

Chapter 5 Uninstalling the Integration To uninstall the integration, complete the following steps: 1. Restart the WebLogic Admin server and the SOA server. 2. Set the environment variables as mentioned above in the installation steps. 3. The uninstallation process is divided into three steps. Execute the commands in each of those steps a. Step 1: Execute the following commands at the command prompt: Linux: cd $PRODUCT_HOME/bin ant -f UnInstallBuild.xml uninstallsoa - DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml - l uninstallsoa.log Windows: cd %PRODUCT_HOME%\bin ant -f UnInstallBuild.xml uninstallsoa - DInstallProperties=%PRODUCT_HOME%/config/InstallProperties.xml l uninstallsoa.log These commands perform the following tasks: Undeploys all the composites from the Enterprise Manager partition. Deletes the partition. Undeploys MDS artifacts. b. Step 2: Execute the following commands at the command prompt: Linux: cd $PRODUCT_HOME/bin ant -f UnInstallBuild.xml uninstallwl - DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml - l uninstallwl.log Windows: cd %PRODUCT_HOME%\bin ant -f UnInstallBuild.xml uninstallwl - DInstallProperties=%PRODUCT_HOME%/config/InstallProperties.xml -l uninstallwl.log These commands perform the following tasks: Delete the JMS resources (JMS module/ JMS persistent store/ JMS server). Uninstalling the Integration 5-1

Undeploy the JMS outbound connection pool. Undeploy the database outbound connection pool. Delete the JDBC data source for the Error Handling module. Remove the work flow notification that is created. Delete the csf-keys generated. After executing the commands mentioned above, bounce the managed server and admin server manually. c. Step 3: Execute the following commands at the command prompt: Linux: cd $PRODUCT_HOME/bin ant -f UnInstallBuild.xml uninstalldb - DInstallProperties=$PRODUCT_HOME/config/InstallProperties.xml - l uninstalldb.log Windows: cd %PRODUCT_HOME%\bin ant -f UnInstallBuild.xml uninstalldb - DInstallProperties=%PRODUCT_HOME%/config/InstallProperties.xml -l uninstalldb.log These commands drop the database objects created for the Error Handling module created for the integration. After a successful uninstall, all JMS, JDBC resources, and the CCB2-MDM2 partition created during installation are deleted. Uninstalling the Integration 5-2

Chapter 6 Troubleshooting the Integration This chapter describes the issues that may arise during the deployment/ undeployment of composites and provides the respective workaround to address them. It includes the following: 6.1 Password Expiry for Database 6.2 Security Policies If a password expires or is changed, then connection issues arise with the Meta Data Store, Error Handling Data Store, or integration specific database. To address this issue, follow these steps: 1. Reset the password or unlock the corresponding database (MDS, EH database, or integration specific database). 2. Change the password for the data source through the WebLogic Administration Console for the database instance where the password is changed/locked. 3. Change the password in the InstallationProperties.xml for that database instance. (This helps only when reinstalling.) 4. Locate the adf-config.xml file that is generated during the installation. It is generally located at $PRODUCT_HOME/install/config/.adf/META-INF. a. Identify the correct metadata-store-usage from the meta-data-namespaces element by the path. b. In the metadata-store-usage element, find the property with jdbcpassword as the attribute value for name attribute. c. Change the password for the value attribute in the property element. Except for the policies used for invoking the edge application services (for example: oracle/wss_http_token_client_policy), ensure that all the composites have appropriate policies or no policies at all. Troubleshooting the Integration 6-1