Post-Installation Checklist
After running the installation scripts, you must complete the following tasks to finalize the installation:
1. Review the logs under $MW_HOME/user_projects/domains/soa_domain/servers/<managed_server>/logs to check for deployment errors.
2. Verify that all the composites in the Enterprise Manager are deployed. Refer to the Verifying Composites in Enterprise Manager section for instructions.
3. Verify that the user messaging service is active.
4. Verify that the security policies are attached. Refer to the Verifying the Attached Policies from Enterprise Manager section for details.
JMS Configuration Checklist
This section includes the components to be verified as part of verifying the configuration checklist.
Verifying JMS Server
1. Verify whether C2MNMSFJS JMS Server is created.
On the Left pane, select Services > Messaging > JMS Servers and check for the presence of CCBNMSFJS server.
Verifying JMS Persistent Store
1. Verify whether the C2MNMSFileStore Persistent Store is created.
a. On the Left pane, select the Services > Persistent Store and check for the presence of C2MNMSFileStore.
b. Verify that the JMSFileStorePath is correct and the directory exists with this name with write permission by clicking on C2MNMSFileStore.
Directory: Product_Home/C2M-NMS
Synchrounous Write Policy: Direct-Write
Verifying JMS Module
Verify whether the C2MNMSFJM JMS module and destinations are created:
a. On the Left pane, select Services > Messaging > JMS Modules.
b. Click the C2MNMSFJM JMS module to verify that all the below four queues are created and they are associated to the correct subdeployment and the correct target (CCBNMSFJS JMS server).
• OUC2MCustomerDataSyncRequest
• OUC2MCustomerDataSyncRequestError
• OUC2MCustomerDataSyncResponse
• OUC2MCustomerDataSyncResponseError
c. Make sure all queues are populated with the server option assigned to it and target server mapped.
JMS Queues Details
a. On the Left pane, select Services > Messaging >JMS Modules > C2MNMSFJM >OUC2MCUstomerDataSyncRequest or any other queue.
b. Select the Monitoring tab.
If the JMSMODULENAME!JMSQUEUENAME row is not present in the Destinations table, there were problems with the installation.
JMS Error Queue Assignment
There are two destination queues and another two corresponding error queues associated for the destination queues. Here C2MNMSCustomerDataSyncRequest is the regular destination queue and C2MNMSCustomerDataSyncRequestError is the corresponding error queue.
Perform the following steps:
a. On the Left pane, select Services >Messaging > JMS Modules > C2MNMSFJM -> OUC2MCustomerDataSyncRequest.
b. Check for the RedeliveryLimit set to 0, ExpirationPolicy to Redirect and Error Destination to corresponding Error Queue.
c. Select the Delivery Failure option with the redirect and ErrorQueue assigned in it.
JMS Adapter Outbound Connection Pool
Complete the following steps:
a. On the Left pane, select the Deployments, click JMS Adapter and select the Configuration tab.
b. Under the Outbound Connection Pools tab, in the Outbound Connection Pool Configuration table, expand oracle.tip.adapter.jms.IJmsConnectionFactory and verify for the presence of eis/wls/OUC2MQueue connection pool instance.
Verifying Composites in Enterprise Manager
To verify that all composites are deployed and in the active state:
1. Verify the C2M-NMS partition was created with all the composites are deployed.
2. Login to the Enterprise Manager.
3. On the Left pane, expand SOA > soa-infra > C2M-NMS partition and check all the below composites are deployed, and are in the active state.
• OUC2MOUNMSCustomerSyncEBF [1.0]
• OUC2MOUNMSJobHistoryQueryEBF [1.0]
• OUC2MOUNMSPlannedOutagesQueryEBF [1.0]
• OUC2MOUNMSTroubleCallInterfaceEBF [1.0]
• OUC2MOUNMSTroubleCallsQueryEBF [1.0]
• OUC2MOUNMSCustomerSyncJMSWriteSvc
• OUC2MOUNMSCustomerSyncJMSReadSvc
Verifying the Attached Policies from Enterprise Manager
To verify the policies attached to the web services that each BPEL process is using:
1. Login to Enterprise Manager.
2. Expand SOA > soa-infra > C2M-NMS partition.
Example: Select OUC2MOUNMSCustomerSyncJMSReadSvc, scroll down to the Services and References section in the Dashboard tab.
3. Click the service and select the Policies tab.
4. Verify that the web service reference is calling a C2M web service and is linked to an appropriate client policy.
5. Verify that the service policy is attached where appropriate.
6. Repeat this process for other composites randomly to verify that the appropriate policies are attached as mentioned in the Installation Properties file. Refer to the Security Policies section for more information.