Configuration Tasks for the Adapter for Sensus RNI
This section describes the tasks that should be taken after installing Oracle Utilities Smart Grid Gateway, including:
Note: Oracle Enterprise Manager may be required for some of the security setups and for monitoring SOA. If Oracle Enterprise Manager is required, you need to extend the example SOA WebLogic domain and enable Enterprise Manager using WebLogic's configuration utility.
Deploying the OSB Adapter for Sensus RNI
The OSB adapter can be deployed on the bundled WebLogic example server instance or on a separate WebLogic server instance. To deploy the OSB adapter, use the following procedures.
To Deploy on the Example WebLogic Instance
1. Create the following directories under <OSB_LOG_DIR>:
d6-usage
d6-usage-arch
d6-usage-error
d6-event
d6-event-arch
d6-event-error
2. Start the example OSB WebLogic instance.
UNIX
cd $SPLEBASE/osbapp
./startWebLogic.sh
Windows
cd %SPLEBASE%\osbapp
startWebLogic.cmd
3. Create JMS queues and target them to the OSB admin server.
a. Create a JMS server “OSB-JMSServer” and target it to admin server.
b. Create a JMS module “D6-SystemModule”.
c. Under “D6-SystemModule” create a sub-deployment “D6-JMSFAServer” and target it to “OSB-JMSServer”.
d. Create the following JMS queues.
Queue Name: DestinationQueue-D6
JNDI Name: DestinationQueue-D6
Sub-deployment: D6-JMSFAServer
Targets: OSB-JMSServer
Queue Name: IMDDestinationQueue-D6
JNDI Name: IMDDestinationQueue-D6
Sub-deployment: D6-JMSFAServer
Targets: OSB-JMSServer
Queue Name: NotificationQueue-D6
JNDI Name: NotificationQueue-D6
Sub-deployment: D6-JMSFAServer
Targets: OSB-JMSServer
UNIX
cd $SPLEBASE/osbapp
$SPLEBASE/product/apache-ant/bin/ant -buildfile deploy-osb_D6.xml
-Dadmin.user=<ADMIN_USER> -Dadmin.password=<OSB_ADMIN_PASSWORD> -Douaf.user=<JMS_USER> -Douaf.password=<JMS_PASSWORD> -Dprocessing.archive=true -Dosb.user=<OSB_USER> -Dosb.password=<OSB_PASSWORD> -Douaf.filter.user=<JMS_USER> -Douaf.filter.password=<JMS_PASSWORD>
Note: Use the following command if this is an upgrade from a previous version:
cd $SPLEBASE/osbapp
$SPLEBASE/product/apache-ant/bin/ant -buildfile deploy-osb_D6.xml update_osb -Dadmin.user=<ADMIN_USER>
-Dadmin.user=<ADMIN_USER> -Dadmin.password=<OSB_ADMIN_PASSWORD> -Douaf.user=<JMS_USER> -Douaf.password=<JMS_PASSWORD> -Dprocessing.archive=true -Dosb.user=<OSB_USER> -Dosb.password=<OSB_PASSWORD> -Douaf.filter.user=<JMS_USER> -Douaf.filter.password=<JMS_PASSWORD>
This will not override any OSB custom changes.
Windows
cd %SPLEBASE%\osbapp
%SPLEBASE%\product\apache-ant\bin\ant -buildfile deploy-osb_D6.xml
-Dadmin.user=<ADMIN_USER> -Dadmin.password=<OSB_ADMIN_PASSWORD> -Douaf.user=<JMS_USER> -Douaf.password=<JMS_PASSWORD> -Dprocessing.archive=true -Dosb.user=<OSB_USER> -Dosb.password=<OSB_PASSWORD> -Douaf.filter.user=<JMS_USER> -Douaf.filter.password=<JMS_PASSWORD>
Note: Use the following command if this is an upgrade from a previous version:
cd %SPLEBASE%\osbapp
%SPLEBASE%\product\apache-ant\bin\ant -buildfile deploy-osb_D6.xml update_osb -Dadmin.user=<ADMIN_USER>
-Dadmin.user=<ADMIN_USER> -Dadmin.password=<OSB_ADMIN_PASSWORD> -Douaf.user=<JMS_USER> -Douaf.password=<JMS_PASSWORD> -Dprocessing.archive=true -Dosb.user=<OSB_USER> -Dosb.password=<OSB_PASSWORD> -Douaf.filter.user=<JMS_USER> -Douaf.filter.password=<JMS_PASSWORD>
This will not override any OSB custom changes.
Create the following JMS configuration in the Oracle Utilities Meter Data Management application Admin Server:
1. Create a JMS module “D6-SystemModule” and target it to the Managed Server where the Oracle Utilities Meter Data Management application is running.
2. Under the JMS module, create a new Foreign Server "OSBForeignServer-D3" and accept the default targets.
3. Under the Foreign Server, navigate to the General tab and configure the following:
a. JNDI Initial Context Factory: weblogic.jndi.WLInitialContextFactory
b. JNDI Connection URL: URL for OSB Sever in the format - t3://<osb hostname>:<osb port number> (Use t3s for SSL)
c. JNDI Properties Credential: Credentials for user with access to OSB server
d. Confirm JNDI Properties Credential: Same as JNDI Properties Credential
e. JNDI Properties: java.naming.security.principal=<User with access to OSB server for which credentials were provided>
4. Under Destinations, create the following foreign destinations:
• Name: DestinationQueue-D6
Local JNDI Name: ForegnDestinationQueue-D6
Remote JNDI Name: DestinationQueue-D6
• Name: IMDDestinationQueue-D6
Local JNDI Name: ForegnIMDDestinationQueue-D6
Remote JNDI Name: IMDDestinationQueue-D6
• Name: NotificationQueue-D6
Local JNDI Name: ForegnNotificationQueue-D6
Remote JNDI Name: NotificationQueue-D6
5. Under Connection Factories, create the following foreign connection factories:
• Name: DestinationQueueConnectionFactory-D6
Local JNDI Name: ForegnDestinationQueueConnectionFactory-D6
Remote JNDI Name: weblogic.jms.XAConnectionFactory
• Name: IMDDestinationQueueConnectionFactory-D6
Local JNDI Name: ForegnIMDDestinationQueueConnectionFactory-D6
Remote JNDI Name: weblogic.jms.XAConnectionFactory
• Name: NotificationQueueConnectionFactory-D6
Local JNDI Name: ForegnNotificationQueueConnectionFactory-D6
Remote JNDI Name: weblogic.jms.XAConnectionFactory
To Deploy on a Separate WebLogic Instance
1. Create the following directories under <OSB_LOG_DIR>.
d6-usage
d6-usage-arch
d6-usage-error
d6-event
d6-event-arch
d6-event-error
2. Copy the following jars to the lib folder under the WebLogic's domain directory.
spl-d1-osb-25.4.jar
This jar is present under the following location:
UNIX: $SPLEBASE/etc/lib
Windows: %SPLEBASE%\etc\lib
3. Start the separate WebLogic instance.
4. Create JMS queues and target them to the OSB admin server.
a. Create a JMS server “OSB-JMSServer” and target it to admin server.
b. Create a JMS module “D6-SystemModule”.
c. Under “D6-SystemModule” create a sub-deployment “D6-JMSFAServer” and target it to “OSB-JMSServer”.
d. Create the following JMS queues:
Queue Name: DestinationQueue-D6
JNDI Name: DestinationQueue-D6
Sub-deployment: D6-JMSFAServer
Targets: OSB-JMSServer
Queue Name: IMDDestinationQueue-D6
JNDI Name: IMDDestinationQueue-D6
Sub-deployment: D6-JMSFAServer
Targets: OSB-JMSServer
Queue Name: NotificationQueue-D6
JNDI Name: NotificationQueue-D6
Sub-deployment: D6-JMSFAServer
Targets: OSB-JMSServer
5. Deploy the OSB adapter on the separate WebLogic instance.
For SSL deployment, please refer to the section Deploying OSB adapter on SSL.
UNIX
cd $SPLEBASE/osbapp
$SPLEBASE/product/apache-ant/bin/ant -buildfile deploy-osb_D6.xml
-Dadmin.user=<ADMIN_USER> -Dadmin.password=<OSB_ADMIN_PASSWORD> -Douaf.user=<JMS_USER> -Douaf.password=<JMS_PASSWORD> -Dprocessing.archive=true -Dosb.user=<OSB_USER> -Dosb.password=<OSB_PASSWORD> -Douaf.filter.user=<JMS_USER> -Douaf.filter.password=<JMS_PASSWORD>
Note: Use the following command if this is an upgrade from a previous version:
cd $SPLEBASE/osbapp
$SPLEBASE/product/apache-ant/bin/ant -buildfile deploy-osb_D6.xml update_osb -Dadmin.user=<ADMIN_USER> -Dadmin.password=<OSB_ADMIN_PASSWORD> -Douaf.user=<JMS_USER> -Douaf.password=<JMS_PASSWORD> -Dprocessing.archive=true -Dosb.user=<OSB_USER> -Dosb.password=<OSB_PASSWORD> -Douaf.filter.user=<JMS_USER> -Douaf.filter.password=<JMS_PASSWORD>
Windows
cd %SPLEBASE%\osbapp
%SPLEBASE%\product\apache-ant\bin\ant -buildfile deploy-osb_D6.xml
-Dadmin.user=<ADMIN_USER> -Dadmin.password=<OSB_ADMIN_PASSWORD> -Douaf.user=<JMS_USER> -Douaf.password=<JMS_PASSWORD> -Dprocessing.archive=true -Dosb.user=<OSB_USER> -Dosb.password=<OSB_PASSWORD> -Douaf.filter.user=<JMS_USER> -Douaf.filter.password=<JMS_PASSWORD>
Note: Use the following command if this is an upgrade from a previous version:
cd %SPLEBASE%\osbapp
%SPLEBASE%\product\apache-ant\bin\ant -buildfile deploy-osb_D6.xml update_osb -Dadmin.user=<ADMIN_USER> -Dadmin.password=<OSB_ADMIN_PASSWORD> -Douaf.user=<JMS_USER> -Douaf.password=<JMS_PASSWORD> -Dprocessing.archive=true -Dosb.user=<OSB_USER> -Dosb.password=<OSB_PASSWORD> -Douaf.filter.user=<JMS_USER> -Douaf.filter.password=<JMS_PASSWORD>
This will not override any OSB custom changes.
Create the following JMS configuration in the Oracle Utilities Meter Data Management application Admin Server:
1. Create a JMS module “D6-SystemModule” and target it to the Managed Server where the Oracle Utilities Meter Data Management application is running.
2. Under the JMS module, create a new Foreign Server "OSBForeignServer-D3" and accept the default targets.
3. Under the Foreign Server, navigate to the General tab and configure the following:
a. JNDI Initial Context Factory: weblogic.jndi.WLInitialContextFactory
b. JNDI Connection URL: URL for OSB Sever in the format - t3://<osb hostname>:<osb port number> (Use t3s for SSL)
c. JNDI Properties Credential: Credentials for user with access to OSB server
d. Confirm JNDI Properties Credential: Same as JNDI Properties Credential
e. JNDI Properties: java.naming.security.principal=<User with access to OSB server for which credentials were provided>
4. Under Destinations, create the following foreign destinations:
• Name: DestinationQueue-D6
Local JNDI Name: ForegnDestinationQueue-D6
Remote JNDI Name: DestinationQueue-D6
• Name: IMDDestinationQueue-D6
Local JNDI Name: ForegnIMDDestinationQueue-D6
Remote JNDI Name: IMDDestinationQueue-D6
• Name: NotificationQueue-D6
Local JNDI Name: ForegnNotificationQueue-D6
Remote JNDI Name: NotificationQueue-D6
5. Under Connection Factories, create the following foreign connection factories:
• Name: DestinationQueueConnectionFactory-D6
Local JNDI Name: ForegnDestinationQueueConnectionFactory-D6
Remote JNDI Name: weblogic.jms.XAConnectionFactory
• Name: IMDDestinationQueueConnectionFactory-D6
Local JNDI Name: ForegnIMDDestinationQueueConnectionFactory-D6
Remote JNDI Name: weblogic.jms.XAConnectionFactory
• Name: NotificationQueueConnectionFactory-D6
Local JNDI Name: ForegnNotificationQueueConnectionFactory-D6
Remote JNDI Name: weblogic.jms.XAConnectionFactory
Deploying the SOA Adapter for Sensus RNI
The SOA adapter can be deployed on the bundled WebLogic example server instance or on a separate WebLogic server instance.
Note: Oracle Enterprise Manager may be required for some of the security setups and for monitoring SOA. If Oracle Enterprise Manager is required, you need to extend the example SOA WebLogic domain and enable Enterprise Manager using WebLogic's configuration utility.
To deploy the SOA adapter, follow the procedures below.
To Deploy on the Example WebLogic Instance
1. Edit the startWeblogic script located at below locations for JAVA_OPTIONS:
UNIX
$SPLEBASE/soaapp/bin/startWebLogic.sh
Windows
%SPLEBASE%\soaapp\bin\startWebLogic.cmd
2. Add “-Djava.security.auth.login.config=${DOMAIN_HOME}/config/SGGLogin.config -Djavax.net.ssl.trustStore=<<JAVA_TRUST_STORE_LOCATION>>” to the JAVA_OPTIONS
3. Start the example SOA WebLogic instance:
UNIX
cd $SPLEBASE/soaapp
./startWebLogic.sh
Windows
cd %SPLEBASE%\soaapp
startWebLogic.cmd
4. Import the Policy Templates and Policies.
a. Import the policy template jar using Enterprise Manager.
Linux
cd $SPLEBASE/soaapp
-DsysPropFile=soa.properties package-soa-policy.xml –Dproduct=d1
Windows
cd %SPLEBASE%/soaapp
-DsysPropFile=soa.properties package-soa-policy.xml –Dproduct=d1
In Oracle Enterprise Manager, navigate to WebLogic Domain and select the required SOA domain.
a. Right-click on the domain and navigate to Web Services, WSM Policies.
b. Click Web Services Assertion Templates at the top of the page.
c. Click Import and import the sgg-d1-policy.jar file.
This file is located in the following directory:
UNIX: $SPLEBASE/soaapp/policies/jars
Windows: %SPLEBASE%\soaapp\policies\jars
b. Next, import the policy template jar using Enterprise Manager.
Linux
cd $SPLEBASE/soaapp
-DsysPropFile=soa.properties package-soa-policy.xml –Dproduct=d6
Windows
cd %SPLEBASE%/soaapp
-DsysPropFile=soa.properties package-soa-policy.xml –Dproduct=d6
In Oracle Enterprise Manager, navigate to WebLogic Domain and select the required SOA domain.
a. Right click on the domain and navigate to Web Services, WSM Policies.
b. Click Web Services Assertion Templates at the top of the page.
c. Click Import and import the sgg-d6-policy.jar zip.
This file is located in the following directory.
UNIX: $SPLEBASE/soaapp/policies/jars
Windows: %SPLEBASE%\soaapp\policies\jars
5. Deploy the SOA adapter on the example WebLogic instance.
UNIX
$SPLEBASE/product/apache-ant/bin/ant -buildfile deploy-soa_MDF.xml
-Dserver.user=<SOA_USER> -Dserver.password=<SOA_PASSWORD> -DsysPropFile=soa.properties
$SPLEBASE/product/apache-ant/bin/ant -buildfile deploy-soa_D6.xml
-Dserver.user=<SOA_USER> -Dserver.password=<SOA_PASSWORD> -DsysPropFile=soa.properties
Windows
cd %SPLEBASE%\soaapp
%SPLEBASE%\product\apache-ant\bin\ant -buildfile
deploy-soa_MDF.xml
-Dserver.user=<SOA_USER> -Dserver.password=<SOA_PASSWORD> -DsysPropFile=soa.properties
%SPLEBASE%\product\apache-ant\bin\ant -buildfile deploy-soa_D6.xml
-Dserver.user=<SOA_USER> -Dserver.password=<SOA_PASSWORD> -DsysPropFile=soa.properties
6. Deploy the Test Harness SOA composites on example WebLogic instance.
UNIX
cd $SPLEBASE/soaapp
$SPLEBASE/product/apache-ant/bin/ant -buildfile deploy-soa_D6.xml deployTestHarness -Dserver.password=<SOA_USER>
-Dserver.password=<SOA_PASSWORD> -DsysPropFile=soa.properties
Windows
Note: Open the command prompt as Administrative mode and then select the environment to deploy soa
cd %SPLEBASE%/soaapp
%SPLEBASE%\product\apache-ant\bin\ant -buildfile
deploy-soa_D6.xml deployTestHarness -Dserver.password=<SOA_USER>
-Dserver.password=<SOA_PASSWORD> -DsysPropFile=soa.properties
To Deploy on a Separate WebLogic Instance
1. Create WebLogic SOA Domain and select Enterprise Manager option.
2. Copy the following jar file to the lib folder under the WebLogic domain directory, spl-d1-soa- security.jar.
This jar is present under the following location:
UNIX: $SPLEBASE/etc/lib
Windows: %SPLEBASE%\etc\lib
3. Add system permissions for Smart Grid Gateway security policies as follows.
a. Login to Oracle Enterprise Manager as an administrative user.
b. Select WebLogic Domain, then Security, then System Policies.
The System Policies page opens.
c. Search for an existing permission for the Smart Grid Gateway security jar as follows:
a. Select “Codebase” from the Type drop-down list (you should not have to change this).
b. Select "Includes" from the Name drop-down list.
c. Enter "spl-d1-soa-security.jar" into the search field.
d. Click the arrow button.
e. No policies should be found:
d. Click Create.
The Create System Grant page opens.
e. Select "Codebase" from the Grant To drop-down list.
f. Enter the complete path to the security jar in the Codebase field as follows:
"file:${domain.home}/lib/spl-d1-soa-security.jar"
g. Click Add (under Permissions).
The Add Permission window opens.
h. Select the "Select here to enter details for a new permission checkbox.
The following fields appear:
• Permission Class
• Resource Name
• Permission Actions
i. Enter the following details into the three fields:
j. Click OK to close the Add Permission window.
k. Click OK (on the Create System Grant page) to save the system grant.
l. Repeat the search from step 2 to confirm the new system policy exists:
This search should return the system policy you just added.
4. Copy the SGGLogin.config file from below location to the config directory of Weblogic SOA domain and edit the startWeblogic script located of Weblogic SOA domain-> bin for JAVA_OPTIONS.
a. This SGGLogin.config is present under the following location:
UNIX: $SPLEBASE/soaapp/config
Windows: %SOA_HOME%\soaapp\config
b. Copy the file.
Unix :<Weblogic_SOA_domain>/config
Windows :<Weblogic_SOA_domain>\config
c. Add “-Djava.security.auth.login.config=${DOMAIN_HOME}/config/SGGLogin.config
-Djavax.net.ssl.trustStore=<<JAVA_TRUST_STORE_LOCATION>>” to the JAVA_OPTIONS to
Unix :<Weblogic_SOA_domain>/bin/startWeblogic.sh
Windows :<Weblogic_SOA_domain>\bin\startWeblogic.cmd
5. Start the separate WebLogic instance.
6. Before SOA composites deployment, import the Policy Templates and Policies.
a. Import the policy template jar using Enterprise Manager.
Linux
cd $SPLEBASE/soaapp
$SPLEBASE/product/apache-ant/bin/ant -buildfile package-soa-policy.xml –Dproduct=d1
Windows
cd %SPLEBASE%/soaapp
$SPLEBASE/product/apache-ant/bin/ant -buildfile package-soa-policy.xml –Dproduct=d1
i. In Oracle Enterprise Manager, navigate to WebLogic Domain and select the required SOA domain.
ii. Right-click the domain and navigate to Web Services > WSM Policies.
iii. Click Web Services Assertion Templates at the top of the page.
iv. Click Import From File and import the sgg-d1-policy.jar zip.
This file is located in the following directory:
UNIX: $SPLEBASE/soaapp/policies/jars
Windows: %SPLEBASE%\soaapp\policies\jars
b. First, import the policy template jar using Enterprise Manager.
Linux
cd $SPLEBASE/soaapp
$SPLEBASE/product/apache-ant/bin/ant -buildfile package-soa-policy.xml –Dproduct=d6
Windows
cd %SPLEBASE%/soaapp
$SPLEBASE/product/apache-ant/bin/ant -buildfile package-soa-policy.xml –Dproduct=d6
a. In Oracle Enterprise Manager, navigate to WebLogic Domain and select the required SOA domain.
b. Right-click the domain and navigate to Web Services, WSM Policies.
c. Click Web Services Assertion Templates at the top of the page.
d. Click Import From File and import the sgg-d6-policy.jar file.
This file is located in the following directory:
UNIX: $SPLEBASE/soaapp/policies/jars
Windows: %SPLEBASE%\soaapp\policies\jars
7. Deploy the SOA cartridge on the separate WebLogic instance.
Note: Modify the SOA Host Server, SOA Port Number, SOA WebLogic User Name, SOA WebLogic User Password and Endpoint URLs menu items according to separate domain using "SOA Configuration Menu item 9".
UNIX
cd $SPLEBASE/soaapp
For WebLogic 14.1.2.x:
$SPLEBASE/product/apache-ant/bin/ant -buildfile deploy-soa_MDF.xml
-Dserver.user=<ADMIN_USER> -Dserver.password=<ADMIN_PASSWORD> -DsysPropFile=soa.properties
$SPLEBASE/product/apache-ant/bin/ant -buildfile deploy-soa_D6.xml
-Dserver.user=<ADMIN_USER> -Dserver.password=<ADMIN_PASSWORD> -DsysPropFile=soa.properties
Windows
cd %SPLEBASE%\soaapp
For WebLogic 14.1.2.x:
%SPLEBASE%\product\apache-ant\bin\ant -buildfile deploy
-soa_MDF.xml
-Dserver.user=<ADMIN_USER> -Dserver.password=<ADMIN_PASSWORD> -DsysPropFile=soa.properties
%SPLEBASE%\product\apache-ant\bin\ant
-buildfile deploy-soa_D6.xml
-Dserver.user=<ADMIN_USER> -Dserver.password=<ADMIN_PASSWORD> -DsysPropFile=soa.properties
8. Deploy the Test Harness SOA composites on the separate WebLogic instance.
UNIX
cd $SPLEBASE/soaapp
For WebLogic 14.1.2.x:
$SPLEBASE/product/apache-ant/bin/ant -buildfile deploy-soa_D6.xml
deployTestHarness -Dserver.user=<ADMIN_USER>
-Dserver.password=<ADMIN_PASSWORD> -DsysPropFile=soa.properties
Windows
cd %SPLEBASE%\soaapp
For WebLogic 14.1.2.x:
%SPLEBASE%\product\apache-ant\bin\ant -buildfile deploy-soa_D6.xml
deployTestHarness -Dserver.user=<ADMIN_USER>
-Dserver.password=<ADMIN_PASSWORD> -DsysPropFile=soa.properties
Configuring Security for the SOA System
Security is managed through policies attached to the input and output points of each composite. More information on policies and their configuration can be found in the Configuring Policies chapter in Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite.
This section describes how to configure security credentials for the SOA system, including:
Configuring Security for the SOA System to Communicate with the Application Framework
Configuring security for the SOA system involves using Oracle Enterprise Manager to create the following security credentials:
• A Credential Map
• A Credential Key for the WebLogic Server
• A Credential Key for the Oracle Utilities Application Framework
Use the following procedure to create the security credentials:
1. In Oracle Enterprise Manager, expand the WebLogic domain, right-click the domain, and select Security > Credentials.
2. On the Credentials page, click Create Map.
3. In the Create Map dialog, name the map oracle.wsm.security, then click OK.
4. Click Create Key and enter the following values:
• Select Map: oracle.wsm.security
• Key: sgg.d6.credentials
• Type: Password
• Username: A valid WebLogic user name with acces to the SOA Suite server
• Password: A valid WebLogic password
5. Click OK.
6. Click Create Key again and enter the following values:
• Select Map: oracle.wsm.security
• Key: sgg.d6.ouaf.credentials
• Type: Password
• Username: A valid OUAF user name
• Password: A valid OUAF password
7. Click OK.
Configuring Security for the SOA System to Communicate with the Head-End System
Configuring security for the SOA system involves creating the security credentials in Oracle Enterprise Manager, and then creating a web service policy that uses the credentials to communicate with the head-end system. These configuration tasks are described in the following sections:
Creating the Security Credentials
To create the security credential in the Credential File Store (CFS):
1. In Oracle Enterprise Manager, navigate to WebLogic Domain and select the required SOA domain.
2. In the WebLogic Domain menu, navigate to Security > Credentials.
3. Click Create Map to set up a new credentials store.
4. In the Create Map dialog box, enter “rni.security” in the Map Name field.
5. Click OK.
6. Select the new map in the Credentials list and click Create Key.
7. In the Create Key dialog box, enter the appropriate values in the fields. In the Key field, enter “rni.credentials”. In the Type field, select Password.
8. Click OK.
By default, the sgg_d6_cfs_multispeak_header_client_policy policy imported previously uses a Credential Map named "rni.security" and a Credential Key called “rni.credentials." Use these values unless making changes to the template values.
Test Harness Note: The test harness is equipped with service policies that authenticate users with credentials in the MultiSpeakMsgHeader. That means the credentials configured in the map and key above should be valid WebLogic users.
Starting the Application
The OSB WebLogic server instance should be up and running before starting the main application.
Creating WebLogic Domain
Create the WebLogic native domain and deploy the application. For instructions refer to the Native Installation Oracle Utilities Application Framework (Doc ID: 1544969.1) white paper on My Oracle Support.
The MDB user configured in Menu 3 during the Oracle Utilities Application Framework installation has to be created in the Oracle Utilities Application Framework application and WebLogic console, and should be part of the “cisusers” group.
Note: The first time you start Oracle Utilities Meter Data Management, you need to log into the WebLogic console and give system access to cisusers role. The WebLogic console application can be accessed through the following URL: http://<hostname>:<portname>/ console.