Configuration Tasks for the Adapter for Silver Spring Networks
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 Silver Spring Networks
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>.
d7-csv
d7-csv-arch
d7-csv-error
d7-ssnxml
d7-ssnxml-arch
d7-ssnxml-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 D7-SystemModule.
c. Under D7-SystemModule create a sub-deployment D7-JMSFAServer and target it to OSB-JMSServer.
d. Create the following JMS queues.
Queue Name: DestinationQueue-D7
JNDI Name: DestinationQueue-D7
Sub-deployment: D7-JMSFAServer
Targets: OSB-JMSServer
 
Queue Name: IMDDestinationQueue-D7
JNDI Name: IMDDestinationQueue-D7
Sub-deployment: D7-JMSFAServer
Targets: OSB-JMSServer
 
Queue Name: NotificationQueue-D7
JNDI Name: NotificationQueue-D7
Sub-deployment: D7-JMSFAServer
Targets: OSB-JMSServer
4. Deploy the OSB adapter on the example WebLogic instance.
For SSL deployment, please refer to Deploying Oracle Service Bus Adapters on SSL.
UNIX
cd $SPLEBASE/osbapp
 
$SPLEBASE/product/apache-ant/bin/ant -buildfile deploy-osb_D7.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_D7.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>
 
This will not override any OSB custom changes.
Windows
cd %SPLEBASE%\osbapp
%SPLEBASE%\product\apache-ant\bin\ant -buildfile deploy-osb_D7.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_D7.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>
 
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 “D7-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-D7
Local JNDI Name: ForegnDestinationQueue-D7
Remote JNDI Name: DestinationQueue-D7
• Name: IMDDestinationQueue-D7
Local JNDI Name: ForegnIMDDestinationQueue-D7
Remote JNDI Name: IMDDestinationQueue-D7
• Name: NotificationQueue-D7
Local JNDI Name: ForegnNotificationQueue-D7
Remote JNDI Name: NotificationQueue-D7
5. Under Connection Factories, create the following foreign connection factories:
• Name: DestinationQueueConnectionFactory-D7
Local JNDI Name: ForegnDestinationQueueConnectionFactory-D7
Remote JNDI Name: weblogic.jms.XAConnectionFactory
• Name: IMDDestinationQueueConnectionFactory-D7
Local JNDI Name: ForegnIMDDestinationQueueConnectionFactory-D7
Remote JNDI Name: weblogic.jms.XAConnectionFactory
• Name: NotificationQueueConnectionFactory-D7
Local JNDI Name: ForegnNotificationQueueConnectionFactory-D7
Remote JNDI Name: weblogic.jms.XAConnectionFactory
To Deploy on a Separate WebLogic Instance
Refer to Configuring Oracle Fusion Middleware Components on a Separate Server from Oracle Utilities Meter Data Management for more information about deploying OSB components on a separate WebLogic server.
1. Create the following directories under <OSB_LOG_DIR>.
d7-csv
d7-csv-arch
d7-csv-error
d7-ssnxml
d7-ssnxml-arch
d7-ssnxml-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 in 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 admin server.
• Create a JMS module D7-SystemModule.
• Under D7-SystemModule create a sub-deployment D7-JMSFAServer and target it to OSB-JMSServer.
• Create the following JMS queues.
Queue Name: DestinationQueue-D7
JNDI Name: DestinationQueue-D7
Sub-deployment: D7-JMSFAServer
Targets: OSB-JMSServer
 
Queue Name: IMDDestinationQueue-D7
JNDI Name: IMDDestinationQueue-D7
Sub-deployment: D7-JMSFAServer
Targets: OSB-JMSServer
 
Queue Name: NotificationQueue-D7
JNDI Name: NotificationQueue-D7
Sub-deployment: D7-JMSFAServer
Targets: OSB-JMSServer
5. Deploy the OSB adapter on the separate WebLogic instance.
For SSL deployment, refer to Deploying Oracle Service Bus Adapters on SSL.
UNIX
cd $SPLEBASE/osbapp
 
$SPLEBASE/product/apache-ant/bin/ant -buildfile deploy-osb_D7.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_D7.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_D7.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. It will not override any OSB custom changes.
%SPLEBASE%/product/apache-ant/bin/ant -buildfile deploy-osb_D7.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>
 
Create the following JMS configuration in the Oracle Utilities Meter Data Management application Admin Server:
1. Create a JMS module “D7-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-D7
Local JNDI Name: ForegnDestinationQueue-D7
Remote JNDI Name: DestinationQueue-D7
• Name: IMDDestinationQueue-D7
Local JNDI Name: ForegnIMDDestinationQueue-D7
Remote JNDI Name: IMDDestinationQueue-D7
• Name: NotificationQueue-D7
Local JNDI Name: ForegnNotificationQueue-D7
Remote JNDI Name: NotificationQueue-D7
5. Under Connection Factories, create the following foreign connection factories:
• Name: DestinationQueueConnectionFactory-D7
Local JNDI Name: ForegnDestinationQueueConnectionFactory-D7
Remote JNDI Name: weblogic.jms.XAConnectionFactory
• Name: IMDDestinationQueueConnectionFactory-D7
Local JNDI Name: ForegnIMDDestinationQueueConnectionFactory-D7
Remote JNDI Name: weblogic.jms.XAConnectionFactory
Name: NotificationQueueConnectionFactory-D7
Local JNDI Name: ForegnNotificationQueueConnectionFactory-D7
Remote JNDI Name: weblogic.jms.XAConnectionFactory
Deploying the SOA Adapter for Silver Spring Networks
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.
For the SSL deployment procedure, refer to the Deploying Service Oriented Architecture Composites on SSL section.
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_D7.xml
-Dserver.user=<SOA_USER> -Dserver.password=<SOA_PASSWORD> -DsysPropFile=soa.properties
 
Windows
%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_D7.xml
-Dserver.user=<SOA_USER> -Dserver.password=<SOA_PASSWORD> -DsysPropFile=soa.properties
5. Deploy the TestHarness SOA composites on example WebLogic instance.
For the SSL deployment procedure, refer to the Deploying Service Oriented Architecture Composites on SSL section.
UNIX
cd $SPLEBASE/soaapp
$SPLEBASE/product/apache-ant/bin/ant -buildfile deploy-soa_D7.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_D7.xml deployTestHarness -Dserver.password=<SOA_USER>
-Dserver.password=<SOA_PASSWORD> -DsysPropFile=soa.properties
 
To Deploy on a Separate WebLogic Instance
Note: Refer to Configuring Oracle Fusion Middleware Components on a Separate Server from Oracle Utilities Meter Data Management for more information about deploying SOA components on a separate WebLogic server.
1. Create WebLogic SOA Domain and select Enterprise Manager option also.
2. Copy the following jar file to the lib folder under the WebLogic domain directory, spl-d1-soa-security.jar
This jar is present in the following location:
UNIX: $SPLEBASE/etc/lib
Windows: %SPLEBASE%\etc\lib
3. Add system permissions for Smart Grid Gateway security policies as follows:
a. Log on 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:
Field
Value
Permission Class
oracle.security.jps.service.credstore.CredentialAccessPermission
Resource Name
context=SYSTEM,mapName=*,keyName=*
Permission Actions
*
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.
This SGGLogin.config is present under the following location:
UNIX: $SPLEBASE/soaapp/config
Windows: %SOA_HOME%\soaapp\config
Copy the file.
Unix :<Weblogic_SOA_domain>/config
Windows: <Weblogic_SOA_domain>\config
5. Start the separate WebLogic instance.
6. Create JMS queues and target them to the SOA managed server:
a. Create a JMS Server:
a. Under Domain Structure, navigate to Services > Messaging > JMS Servers.
b. On the JMS Servers page, click on New.
c. On the Create a New JMS Server page:
• Provide a name for your JMS Server. For example: SSN-JMSServer
• Select a Persistent Store to SOAJMSFileStore. Click Next.
• On the next screen, select the SOA_Server as Target Server instance where you would like to deploy this JMS Server.
• Select the Target Server from the dropdown list and click Finish to complete the JMS server creation. Make sure you activate the changes.
• You should now find your new JMS Server in the JMS Servers List.
b. Create a JMS Module.
a. On the Create JMS System Module page, enter the name. For example: SSN-SystemModule (other fields can remain empty).
b. Select the SOA Server you would like to target (ideally, this would be the same server that is hosting the JMS server you created above).
For example: soa_server1
c. On the next screen, click Finish and Activate changes.
c. Create Queues.
a. Click on New in JMS Module to create the Queue.
b. Provide a name (for example: SSNTestSSNODRQ) and a JNDI name (for example, queue/SSNTestSSNODRQ).
c. Select a subdeployment (for example: SSN-JMSFAServer) if you already created or follow below steps to create a new subdeployment. (A subdeployment is a convenient way for grouping and targeting JMS module resources.)
d. Provide a name for the subdeployment (for example: SSN-JMSFAServer) and click OK.
• Select the target JMS Server we created (for example: SSN-JMSServer) and click finish.
• Click New in JMS Module to create the queue.
• Provide a name (for example: SSNODRQ) and a JNDI name (for example: queue/SSNODRQ).
• Select a subdeployment (for example: SSN-JMSFAServer) if you already created or follow below steps to create a New Subdeployment.(A subdeployment is a convenient way for grouping and targeting JMS module resources.)
• Provide a name for the subdeployment (for example: SSN-JMSFAServer) and click OK.
• Select the target JMS Server we created (for example: SSN-JMSServer) and Click finish.
d. Create JMS Connection Factory.
a. Click on New in JMS Module to create the Connection factory.
b. Give the Connection factory a name (for example, SSNTestHarnessConnectionFactory and JNDI name (for example, jms/SSNTestHarnessConnectionFactory ). Click Next.
c. Select Advance Targeting and on the next page select the subdeployment you created above (SSN-JMSFAServer). Wait for the page to refresh and click on Finish.
d. Click on New in JMS Module to create the Connection factory.
e. Give the Connection factory a name (for example, SSNConnectionFactory) and JNDI name (for example, jms/SSNConnectionFactory). Click Next.
f. Select Advance Targeting and on the next page select the subdeployment you created above (SSN-JMSFAServer). Wait for the page to refresh and click Finish.
e. Create a Source JMS Bridge Destination.
a. Under Domain Structure, navigate to Services > Messaging > Bridge > JMS Bridge Destinations.
b. On the JMS Bridge Destinations page, click New.
c. On the create a New JMS Bridge Destination page:
• Provide a name for your JMS Bridge destination SSNTestHarnessBridgeDestination.
• Select Adapter JNDI named eis.jms.WLSConnectionFactoryJNDINoTX.
• Provide Initial Context Factory as weblogic.jndi.WLInitialContextFactory.
• Provide Connection URL as t3://@SSN_UIQ_HOST@:@SSN_UIQ_PORT@.
• Provide Connection Factory JNDI name as jms/SSNTestHarnessConnectionFactory.
• Provide Destination JNDI name as queue/SSNTestSSNODRQ.
• Select Destination type as queue.
• Provide username.
• Provide password.
• Confirm the password.
Note: After creating JMS Bridge Destination, click Services > Messaging > Bridge > JMS Bridge Destinations > SSNSOABridgeDestination.
• On the SSNSOABridgeDestination page, enter the username and password values. Click Save.
f. Create a Target JMS Bridge Destination.
a. Under Domain Structure, navigate to Services > Messaging > Bridge > JMS Bridge Destinations.
b. On the JMS Bridge Destinations page, click New.
c. On the Create a New JMS Bridge Destination page:
• Provide a name for your JMS Bridge destination SSNSOABridgeDestination.
• Select Adapter JNDI name as eis.jms.WLSConnectionFactoryJNDINoTX.
• Provide Initial Context Factory as weblogic.jndi.WLInitialContextFactory.
• Provide Connection URL as t3:// @SOA_HOST@:@SOA_PORT_NUMBER.
• Provide Connection Factory JNDI name as jms/SSNConnectionFactory"
• Provide Destination JNDI name as queue/SSNODRQ.
• Select Destination type as queue.
Note: After creating JMS Bridge Destination, navigate to Services > Messaging > Bridge > JMS Bridge Destinations > SSNSOABridgeDestination.
• On the SSNSOABridgeDestination page, enter username and password values, click Save.
g. Create a Bridge.
Under Domain Structure, navigate to Services > Messaging > Bridges On the Bridges page. Click New. On the Create a New Bridge page:
• Provide a name for Bridge as SSNODRQBridge.
• Select Quality of Service as At most-Once.
• Check Started.
• Click Next.
• Select Source Bridge Destination as SSNTestHarnessBridgeDestination.
• Select Messaging Provider as WebLogic Server 7.0 or Higher.
Note: In real time depending on SSN environment this should be changed
• Select Target Bridge Destination as SSNSOABridgeDestination.
• Select Messaging Provider as WebLogic Server 7.0 or Higher.
• Select server as soa_server1.
Note: Any web logic managed server.
• Click Finish.
7. Deploy the SOA adapter on the separate WebLogic instance.
Note: Modify the SOA Host Server, SOA Port Number, SOA WebLogic User Name, SOA WebLogic User Password menu items according to separate domain using SOA Configuration Menu item 9.
For the SSL deployment procedure, refer to the Deploying Service Oriented Architecture Composites on SSL section.
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_D7.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_D7.xml
-Dserver.user=<ADMIN_USER> -Dserver.password=<ADMIN_PASSWORD>-DsysPropFile=soa.properties
 
8. Deploy the TestHarness SOA composites on the separate WebLogic instance.
For the SSL deployment procedure, refer to the Deploying Service Oriented Architecture Composites on SSL section.
UNIX
cd $SPLEBASE/soaapp
 
For WebLogic 14.1.2.x:
$SPLEBASE/product/apache-ant/bin/ant -buildfile deploy-soa_D7.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_D7.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 Configuring Policies in the 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 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.d7.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.d7.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 establishing a secure socket layer communications channel to the head end system.
These configuration tasks are described in the following sections:
Creating the Security Credentials
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.d7.ssn.credentials
• Type: Password
• Username: A valid WebLogic user name
• Password: A valid WebLogic password
5. Click OK.
Importing the Policy Templates and Policies
Follow the procedure below to import the policy templates and policies:
a. Import the policy template jar using Enterprise Manager.
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 on the domain and navigate to Web Services, WSM Policies.
d. Click on Web Services Assertion Templates at the top of the page
e. Click on 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
Attaching Secure Socket Layer (SSL) Policies
Silver Springs Networks accepts SSL transmissions to secure web service calls to their head-end system. Oracle web service references communicating with the head-end system include OWSM policies that implement HTTPS over SSL. The following services are all contained in the Common composite:
• JobManager
• DeviceManager
• DataAggregation
• DeviceResults
Each of these is configured to use the credential created above that uses the “sgg.d7.ssn.credentials” key.
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.