Configuration Tasks for the Adapter for Networked Energy Services
This section describes the tasks that should be taken after installing Oracle Utilities Smart Grid Gateway Adapter for Networked Energy Services, 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 Networked Energy Services
This section describes how to deploy the OSB Adapter.
To Deploy on the Example WebLogic Instance
1. Create the following directories under <OSB_LOG_DIR>:
d4-event
d4-event-arch
d4-event-error
d4-usage
d4-usage-arch
d4-usage-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 the admin server.
b. Create a JMS module “D4-SystemModule”
c. Under “D4-SystemModule” create a sub-deployment “D4-JMSFAServer” and target it to “OSB-JMSServer”
d. Create the following JMS queues:
Queue Name: DestinationQueue-D4
JNDI Name: DestinationQueue-D4
Sub-deployment: D4-JMSFAServer
Targets: OSB-JMSServer
Queue Name: IMDDestinationQueue-D4
JNDI Name: IMDDestinationQueue-D4
Sub-deployment: D4-JMSFAServer
Targets: OSB-JMSServer
Queue Name: NotificationQueue-D4
JNDI Name: NotificationQueue-D4
Sub-deployment: D4-JMSFAServer
Targets: OSB-JMSServer
4. Deploy the OSB adapter on the example 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_D4.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_D4.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.
Windows
cd %SPLEBASE%\osbapp
%SPLEBASE%\product\apache-ant\bin\ant -buildfile deploy-osb_D4.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_D4.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 “D4-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-D4" 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-D4
Local JNDI Name: ForegnDestinationQueue-D4
Remote JNDI Name: DestinationQueue-D4
• Name: IMDDestinationQueue-D4
Local JNDI Name: ForegnIMDDestinationQueue-D4
Remote JNDI Name: IMDDestinationQueue-D4
• Name: NotificationQueue-D4
Local JNDI Name: ForegnNotificationQueue-D4
Remote JNDI Name: NotificationQueue-D4
5. Under Connection Factories, create the following foreign connection factories:
• Name: DestinationQueueConnectionFactory-D4
Local JNDI Name: ForegnDestinationQueueConnectionFactory-D4
Remote JNDI Name: weblogic.jms.XAConnectionFactory
• Name: IMDDestinationQueueConnectionFactory-D4
Local JNDI Name: ForegnIMDDestinationQueueConnectionFactory-D4
Remote JNDI Name: weblogic.jms.XAConnectionFactory
• Name: NotificationQueueConnectionFactory-D4
Local JNDI Name: ForegnNotificationQueueConnectionFactory-D4
Remote JNDI Name: weblogic.jms.XAConnectionFactory
To Deploy on a Separate WebLogic Instance
1. Create the following directories under <OSB_LOG_DIR>.
d4-event
d4-event-arch
d4-event-error
d4-usage
d4-usage-arch
d4-usage-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:
• Create a JMS server “OSB-JMSServer” and target it to the admin server
• Create a JMS module “D4-SystemModule”
• Under “D4-SystemModule” create a sub-deployment “D4-JMSFAServer” and target it to “OSB-JMSServer”
• Create the following JMS queues:
Queue Name: DestinationQueue-D4
JNDI Name: DestinationQueue-D4
Sub-deployment: D4-JMSFAServer
Targets: OSB-JMSServer
Queue Name: IMDDestinationQueue-D4
JNDI Name: IMDDestinationQueue-D4
Sub-deployment: D4-JMSFAServer
Targets: OSB-JMSServer
Queue Name: NotificationQueue-D4
JNDI Name: NotificationQueue-D4
Sub-deployment: D4-JMSFAServer
Targets: OSB-JMSServer
5. Deploy the OSB adapter on the separate WebLogic instance by running the following command from the Oracle Utilities application server:
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_D4.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_D4.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
Windows
cd %SPLEBASE%\osbapp
%SPLEBASE%\product\apache-ant\bin\ant -buildfile deploy-osb_D4.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_D4.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 “D4-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-D4" 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-D4
Local JNDI Name: ForegnDestinationQueue-D4
Remote JNDI Name: DestinationQueue-D4
• Name: IMDDestinationQueue-D4
Local JNDI Name: ForegnIMDDestinationQueue-D4
Remote JNDI Name: IMDDestinationQueue-D4
• Name: NotificationQueue-D4
Local JNDI Name: ForegnNotificationQueue-D4
Remote JNDI Name: NotificationQueue-D4
5. Under Connection Factories, create the following foreign connection factories:
• Name: DestinationQueueConnectionFactory-D4
Local JNDI Name: ForegnDestinationQueueConnectionFactory-D4
Remote JNDI Name: weblogic.jms.XAConnectionFactory
• Name: IMDDestinationQueueConnectionFactory-D4
Local JNDI Name: ForegnIMDDestinationQueueConnectionFactory-D4
Remote JNDI Name: weblogic.jms.XAConnectionFactory
• Name: NotificationQueueConnectionFactory-D4
Local JNDI Name: ForegnNotificationQueueConnectionFactory-D4
Remote JNDI Name: weblogic.jms.XAConnectionFactory
Deploying the SOA Adapter for Networked Energy Services
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, use the following procedures.
To Deploy on the Example WebLogic Instance
1. Edit the startWeblogic script located at below locations for JAVA_OPTIONS:
UNIX
cd $SPLEBASE/soaapp
./startWebLogic.sh
Windows
cd %SPLEBASE%\soaapp 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. Deploy the SOA adapter on the example WebLogic instance.
UNIX
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_D4.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_D4.xml
-Dserver.user=<SOA_USER> -Dserver.password=<SOA_PASSWORD> -DsysPropFile=soa.properties
To Deploy on a Separate WebLogic Instance
1. 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
2. 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
3. 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
4. Start the separate WebLogic instance.
5. Deploy the SOA adapter on the separate WebLogic instance by running the following command from the Oracle Utilities application server:
UNIX
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_D4.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_D4.xml
-Dserver.user=<ADMIN_USER> -Dserver.password=<ADMIN_PASSWORD> -DsysPropFile=soa.properties
Deploying the Test Harness
The test harness is a set of mock web services that can be used to test the SOA configuration setup and functionality in the absence of an actual physical head-end system. This is an optional task.
Note: The test harness is not a supported feature of the application.
Use the following procedures to deploy the test harness SOA adapter:
To Deploy on the Example WebLogic Instance
1. Deploy the test harness on the example WebLogic instance.
UNIX
cd $SPLEBASE/soaapp
$SPLEBASE/product/apache-ant/bin/ant -buildfile deploy-soa_D4.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_D4.xml deployTestHarness -Dserver.password=<SOA_USER>
-Dserver.password=<SOA_PASSWORD> -DsysPropFile=soa.properties
To Deploy on a Separate WebLogic Instance
1. Deploy the SOA adapter on the separate WebLogic instance.
UNIX
cd $SPLEBASE/soaapp
For WebLogic 14.1.2.x:
$SPLEBASE/product/apache-ant/bin/ant -buildfile deploy-soa_D4.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_D4.xml
deployTestHarness -Dserver.user=<ADMIN_USER>
-Dserver.password=<ADMIN_PASSWORD> -DsysPropFile=soa.properties
Configuring the Networked Energy Services Head-End System to Report Events
This section describes how to configure the Networked Energy Services head-end system to report events to the Networked Energy Services. Configuring the head-end system requires using the NES Diagnostic Tool to specify the following system properties:
• Event Delivery Type
• Event Receiver URL
• Event Receiver Namespace
• API Key Timeout Period
Configuring the Event Delivery Type
To configure the event delivery type:
1. In the NES Diagnostic Tool navigation tree, navigate to NES System Data, Event Configuration.
2. In the tree, select the Add Device Failure event to view its properties.
3. Set the DELIVERYTYPEID property to EventDeliveryType.SOAP.
Repeat this task for each of the following events:
• Add Device Failure
• Add Device Success
• Connect Device Load Command Complete
• Disconnect Device Load Command Complete
• Move Device Success
• Move Device Failure
• Read Device Load Profile On-Demand Command Complete
• Read Device Full Load Profile Command Complete
• Read Device Load Status Command Complete
• Read Device Billing Data On-Demand Command Complete
• Set Device ATM Configuration Command Complete
Configuring the Event Receiver URL
To configure the event receiver URL:
1. In the NES Diagnostic Tool navigation tree, navigate to NES System Data, Settings, Solution Settings.
2. Select Event Receiver URL to view its properties.
3. Set the VALUE property to the URL that is specified for the web service ReceivePanoramixEvents. For example:
http://<NES_HOST>:<PORT_NUMBER>/soa-infra/services/Echelon_NES/HandleReceiveEvents/ReceivePanoramixEvents
4. Restart the application server that hosts the Networked Energy Services head-end system. (The World Wide Web and Networked Energy Services Local Task Manager services).
Configuring the Event Receiver Namespace
To configure the event receiver namespace:
1. In the NES Diagnostic Tool navigation tree, navigate to NES System Data, Settings, Solution Settings.
2. Select Event Receiver Namespace.
3. Set the VALUE property to http://tempuri.org. This is the namespace for the Networked Energy Services Adapter web service that will receive the events.
Configuring the API Key Timeout Period
Note: This task is optional. By default the API Key Timeout Period is set to 60 minutes.
To configure the API Key Timeout Period:
1. In the NES Diagnostic Tool navigation tree, navigate to NES System Data, Settings, Solution Settings.
2. In the tree, select the API Key Timeout Period to view its properties.
3. Change the VALUE property to set the timeout period for the API key.
4. Restart the application server that hosts the Networked Energy Services head-end system.
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 Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite, Chapter 10: Configuring Policies.
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 on the domain, and choose 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.d4.credentials
• Type: Password
• Username: A valid WebLogic user name
• 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.d4.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. Right-click the domain and navigate to Security, Credentials.
3. Click Create Map to set up a new credentials store.
4. In the Create Map dialog box, enter a unique value in the Map Name field.
For example, nes.credentials.
5. Click OK.
6. Select the new map in the Credentials list and click Create Key.
For example: nes-key
7. In the Create Key dialog box, enter the appropriate values in the fields.
8. In the Type field, select Password.
9. Click OK.
Importing the Policy Templates
To import the policy assertion templates:
1. Import the policy template jar using Enterprise Manager.
a. For Linux:
cd $SPLEBASE/soaapp
$SPLEBASE/product/apache-ant/bin/ant -buildfile package-soa-policy.xml –Dproduct=d1
For Windows:
cd %SPLEBASE%/soaapp
$SPLEBASE/product/apache-ant/bin/ant -buildfile package-soa-policy.xml –Dproduct=d1
b. In Oracle Enterprise Manager, navigate to WebLogic Domain and select the required SOA domain.
c. Right-click the domain and navigate to Web Services, WSM Policies.
d. Click Web Services Assertion Templates at the top of the page.
e. Click Import 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
2. Import the policy template jar using Enterprise Manager.
a. Linux:
cd $SPLEBASE/soaapp
$SPLEBASE/product/apache-ant/bin/ant -buildfile package-soa-policy.xml –Dproduct=d4
Windows
cd %SPLEBASE%/soaapp
$SPLEBASE/product/apache-ant/bin/ant -buildfile package-soa-policy.xml –Dproduct=d4
b. In Oracle Enterprise Manager, navigate to WebLogic Domain and select the required SOA domain.
c. Right-click the domain and navigate to Web Services, WSM Policies.
d. Click Web Services Assertion Templates at the top of the page.
e. Click Import and import the sgg-d4-policy.jar zip.
This file is located in the following directory:
UNIX:
$SPLEBASE/soaapp/policies/jars
Windows:
%SPLEBASE%\soaapp\policies\jars
Creating the Web Service Policy for the Security Credentials
To create a web service policy for the security credentials:
1. In Oracle Enterprise Manager, navigate to WebLogic Domain and select the required SOA domain.
2. Right-click the domain and navigate to Web Services, Policies.
3. In the Applies To field, select either All or Service Clients.
4. Select the policy oracle/wss_http_token_client_policy.
5. Click Create Like.
a. Give the policy a unique name and an appropriate description.
b. Under Assertions, remove the Log Message and the HTTP Security policies.
c. Click Add.
d. Enter a name for the new assertion.
e. In the Assertion Template field, select sgg/d1_csf_access_client_xpath_template and click Save.
f. Click OK.
6. In the Assertion Content field, edit property values in the XML according to the example below. The following table lists the property values that should be edited:
<orasp:SGGCredentialStoreInsertionXPath xmlns:orawsp="http://schemas.oracle.com/ws/2006/01/policy" orawsp:Silent="true" orawsp:name="CSF_Echelon" orawsp:description="Properties to add CSF credentials to a SOAP message" orawsp:Enforced="true" orawsp:category="security/authentication" xmlns:orasp="http://schemas.oracle.com/ws/2006/01/securitypolicy">
<orawsp:bindings>
<orawsp:Implementation>com.splwg.d1.sgg.soa.common.security.policy.CredentialStorageFacilityAccessAssertationExecutor</orawsp:Implementation>
<orawsp:Config orawsp:name="CSFKeyInsertionConfig" orawsp:configType="declarative">
<orawsp:PropertySet orawsp:name="CSFKeyProperties">
<orawsp:Property orawsp:type="string" orawsp:contentType="required" orawsp:name="csf-map">
<orawsp:Description>Which CSF map to use</orawsp:Description>
<orawsp:Value>CSF_map_name</orawsp:Value>
</orawsp:Property>
<orawsp:Property orawsp:type="string" orawsp:contentType="required" orawsp:name="csf-key">
<orawsp:Description>Which key in the map to use</orawsp:Description>
<orawsp:Value>CSF_Key</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
<orawsp:PropertySet orawsp:name="XPathProperties">
<orawsp:Property orawsp:type="string" orawsp:contentType="required" orawsp:name="soapElement">
<orawsp:Description>The segment of the soap message to which to write. Legal Values are "header" & "body"</orawsp:Description>
<orawsp:Value>body</orawsp:Value>
</orawsp:Property>
<orawsp:Property orawsp:type="string" orawsp:contentType="optional" orawsp:name="namespaceDefinitions">
<orawsp:Description>A space-separated list of prefix-namespace pairs. For example: ns1=http://myurl.com/ns1 ns2=http://oracle.com xsd=http://www.w3.org/2001/XMLSchema</orawsp:Description>
<orawsp:Value/> <!-- NOTE: nothing entered in this space -->
</orawsp:Property>
<orawsp:Property orawsp:type="string" orawsp:contentType="required" orawsp:name="userid.xpath">
<orawsp:Description>The xpath relative to the soapElement property at which to insert the user id.</orawsp:Description>
<orawsp:Value>./sUserLogin</orawsp:Value>
</orawsp:Property>
<orawsp:Property orawsp:type="string" orawsp:contentType="required" orawsp:name="password.xpath">
<orawsp:Description>The xpath relative to the soapElement property at which to insert the password.</orawsp:Description>
<orawsp:Value>./sPassword</orawsp:Value>
</orawsp:Property>
</orawsp:PropertySet>
<orawsp:PropertySet orawsp:name="DebugProperties">
<orawsp:Property orawsp:type="boolean" orawsp:contentType="optional" orawsp:name="isDebuggingActive">
<orawsp:Description>controls debugging output</orawsp:Description>
<orawsp:Value>false</orawsp:Value>
<orawsp:DefaultValue>false</orawsp:DefaultValue>
</orawsp:Property>
</orawsp:PropertySet>
</orawsp:Config>
</orawsp:bindings>
</orasp:SGGCredentialStoreInsertionXPath>
7. Save the policy.
8. Attach the policy to the User Manger reference.
a. In Oracle Enterprise Manager, Navigate to the AuthenticationMgr composite. The full path is SOA/soa-infra/Echelon/AuthenticationMgr.
b. On the Policies tab, from the Attach To/Detach From menu, select UserManager.
c. In the Available Policies window, select the policy that you just created.
d. Click Attach to attach the policy to the UserManager reference.
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) document 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.