Property (XPath Representation) | Description | Example |
|---|---|---|
<config> | ||
<modulename> | Name of the integration module. | Default: CCB2-MDM2 Do not change this value. |
CCB Application Information | ||
<CCB-MDM2><CCB><Protocol> | The protocol on which the application is accessible. | http or https |
<CCB-MDM2><CCB><Host> | The host name of Oracle Utilities Customer Care and Billing server application. | CCB_HOST.yourdomain.com |
<CCB-MDM2><CCB><Port> | The port number of Oracle Utilities Customer Care and Billing application. | CCB_PORT_NO (Example: 1961) |
<CCB-MDM2><CCB><ContextRoot> | The context root of the application. | CCB_CONTEXT_ROOT _NAME ouaf/XAIApp/xaiserver (for XAI services) ouaf/webservices (for IWS services) |
<CCB-MDM2><CCB><ApplicationUsername> | The login user name of the application. | CCBUSER |
<CCB-MDM2><CCB><ApplicationPassword> | The login password of the application. | CCBPWD |
<CCB-MDM2><CCB><policy> | The security policy that CCB accepts when invoking it’s webservice. | Use oracle/ wss_http_token_client_policy for XAI services or refer to the Security Policies section for more information when invoking IWS services. |
MDM Application Information | ||
<CCB-MDM2><MDM><Protocol> | The protocol on which the application is accessible. | http or https |
<CCB-MDM2><MDM><Host> | The host name of Oracle Utilities Meter Data Management application. | MDM_HOST.yourdomain.com |
<CCB-MDM2><MDM><Port> | The port number of Oracle Utilities Meter Data Management application. | MDM_PORT_NO (Example: 1961) |
<CCB-MDM2><MDM><ContextRoot> | The context root of the application. | CCB_CONTEXT_ROOT _NAME ouaf/XAIApp/xaiserver (for XAI services) ouaf/webservices (for IWS services) |
<CCB-MDM2><MDM><ApplicationUsername> | The login user name of the application. | MDMUSER |
<CCB-MDM2><MDM><ApplicationPassword> | The login password of the application. | MDMPWD |
<CCB-MDM2><MDM><policy> | The security policy that MDM accepts when invoking it’s webservice. | Use oracle/ wss_http_token_client_policy for XAI services or refer to the Security Policies section for more information when invoking IWS services. |
Workflow Notification Properties | ||
<CCB-MDM2><WorkFlow.Notification><from.emailid> | Email ID which should be set in the “From” property of Workflow Notification bean. | Admin.user@yourdomain.com |
<CCB-MDM2><WorkFlow.Notification>]<mode> | Type of notification mode | EMAIL |
SOA Admin Server | ||
<SOA><AdminServer><hostname> | Host name of the server where admin server hosting SOA suite is installed. | adminserver.example.oracle.com |
<SOA><AdminServer><portnumber> | Port number the admin server (hosting SOA suite) is listening to. | 7001 |
<SOA><AdminServer><servername> | Admin server name (hosting SOA suite) | Admin Server |
<SOA><AdminServer><username> | User name used to log in as an Admin server (hosting SOA suite) administrator. | weblogic |
<SOA><AdminServer><password> | Password used to log in as an Admin server (hosting SOA suite) administrator. | xxxxxx |
<SOA><AdminServer><domainname> | WebLogic domain name hosting SOA suite. | soa_domain |
SOA Managed Server | ||
<SOA><ManagedServer><hostname> | Host name of the server where managed server (hosting SOA suite) is installed. | managedserver.example.oracle.com |
<SOA><ManagedServer><portnumber> | Port number the managed server (hosting SOA suite) is listening to. | 8001 |
<SOA><ManagedServer><servername> | Managed server name (hosting SOA suite) | Managedserver1 |
<SOA><ManagedServer><username> | User name used to log in to managed server (hosting SOA suite) as an administrator. | weblogic |
<SOA><ManagedServer><password> | Password used to log in to managed server (hosting SOA suite) as an administrator. | xxxx |
Oracle HTTP Server Information | In a non-cluster environment these properties would be same as the <ManagedServer> values. | |
<SOA><OHS><hostname> | The host name of the Oracle HTTP Server. | Oracle http server where cluster is managed |
<SOA><OHS><portnumber> | The port number of the Oracle HTTP Server. | Example: 7777 |
<SOA><OHS><servernames> | The list of server names that are defined as Managed Servers/Clusters. | In multiple managed servers, provide comma separated values. Example: soa_server1, soa_server2 |
<SOA><OHS>< Protocol> | The protocol on which Oracle HTTP Server can be accessed. | http or https |
MDS DB Information | ||
<SOA><mdsconfig><mdsdbusername> | User name used to log in to MDS. | XXX_MDS |
<SOA><mdsconfig><mdsdbuserpassword> | Password used to log in to MDS. | **** |
<SOA><mdsconfig><mdsdbhostname> | Host name of the server hosting the database containing the MDS schema. | Db.hostname.oracle.com |
<SOA><mdsconfig><mdsdbportnumber> | Port number of the database containing the MDS schema. | 1521 |
<SOA><mdsconfig><mdsdbsid> | SID of the database containing MDS. | SID |
JMS Information | ||
<SOA><JMS><serverName> | The JMS server name. | Default:: CCB2MDM2JS Do not change. |
<SOA><JMS><ModuleName> | The JMS module name. | Default:: CCB2MDM2JM |
<SOA><JMS><SubDeploymentName> | The Subdeployment name. | Default: CCB2MDM2SD Do not change. |
<SOA><JMS><JMSServerTarget> | The SOA Managed Server Target for JMS server. | For cluster environment, give only one managed server name under the cluster |
<SOA><JMS><JMSModuleTargets> | The JMS Module targeted SOA managed servers/Clusters. | For cluster environment give comma separated managed server names under the cluster or multiple cluster names |
<SOA><JMS><PersitentStoreName> | The file store persistence details. | Default: CCB2MDM2FS |
<SOA><JMS><PersitentStoreType> | JMS persistent store type (FileStores or DBStore). Deployment script supports a file | Default: FileStores |
<SOA><JMS><PersistentStoreFilename> | Directory path name where the file based persistent store should be created. | PRODUCT_HOME/CCB2-MDM2/bin |
<SOA><JMS><JMSCFName> | The file name of the ConnectionFactory. | OUCCB2OUMDM2ConnectionFactory |
<SOA><JMS><JMSCFJNDI> | The JNDI file name of the ConnectionFactory. | jms/OUCCB2OUMDM2ConnectionFactory |
Email Information | ||
<SOA><EMAIL><MailAccessProtocol> | The protocol of the Mail Access. | IMAP |
<SOA><EMAIL> <OutgoingDefaultFromAddr> | The email address from which the outgoing mails are sent. | mail.id@yourdomain.com |
<SOA><EMAIL><OutgoingMailServer> | The mail server name from where the mails are sent. | host.yourdomain.com |
<SOA><EMAIL><OutgoingMailServerPort> | The port number of the outgoing mail server. | 465 |
<SOA><EMAIL> <OutgoingMailServerSecurity> | The security for the outgoing mail server. | SSL |
<SOA><EMAIL><OutgoingUsername> | The user name of the outgoing email. | mail.id@ yourdomain.com |
<SOA><EMAIL><Outgoingpassword> | The password of the outgoing email. | Your password |
<SOA><EMAIL><incomingMailServer> | The mail server name where mail is received. | host.yourdomain.com |
<SOA><EMAIL><IncomingUserIDs> | Incoming user IDs. | mail.id@ yourdomain.com |
<SOA><EMAIL><IncomingUserPasswords> | Incoming passwords. | Your password |
<SOA><EMAIL><applicationName> | The application for which the UMS configuration is considered. | usermessaging driver-email |
<SOA><EMAIL><capability> | Sets the driver's capability to send or receive messages. | Values are SEND, RECEIVE, and BOTH. |
Error Handling Database Information | ||
<EH><dba.dbusername> | User name used to log in as a database administrator (DBA). This database hosts the schema required for the integration. | system |
<EH><dba.dbuserpassword> | Password used to log in as a database administrator (DBA). This database hosts the schema required for the integration. | xxxxxx |
<EH><dbusername> | User name to log in to the error handling schema for the integration. This User can be automatically created by the install (set dbuser.createflag to true) or manually outside the install process. | CCBMDMUSER |
<EH>dbuserpassword> | Password to log in to the error handling schema for the integration. | xxxxxx |
<EH><dbuser.createflag> | If set to true, the db user can be automatically created by the install. If this value is set to false, the schema needed for integration error handling will not be automatically created by the install and will need to be created manually prior to running the installation. When creating the user manually, grant connect and resource to the user. | true |
<EH><dbhostname> | The DB Hostname of the error handling schema for the integration. | host.yourdomain.com |
<EH><dbportnumber> | The DB Port of the error handling schema for the integration. | 1521 |
<EH><dbsid> | The DB SID of the error handling schema for the integration. | SID |