Extending a SOA Domain to Include BAM

This post includes instructions and screen shots on how to extend a SOA domain to include BAM. We follow the SOA 11g EDG guide:

     Oracle® Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite 11g Release 1 (11.1.1)
     Section 7.3 Extending the Domain to Include BAM
     http://docs.oracle.com/cd/E21764_01/core.1111/e12036/extend_bam.htm#CCHJFACD

The environment used had 2 physical hosts: BAMHOST1 and BAMHOST2. The steps were performed on BAMHOST1. Please refer to the following section in the EDG for instructions on how to propagate the domain to the other BAM server.

     Oracle® Fusion Middleware Enterprise Deployment Guide for Oracle SOA Suite 11g Release 1 (11.1.1)
     Section 7.7 Propagating the Domain Configuration to BAMHOST1 and BAMHOST2 Using the
     pack/unpack Utility
     http://docs.oracle.com/cd/E21764_01/core.1111/e12036/extend_bam.htm#CFHBJGJJ


    1. Change directory to the location of the Configuration Wizard. It should be under the $ORACLE_COMMON_HOME/common/bin directory:

          Example: cd /u01/app/oracle/product/soa/common/bin
    	

    2. Start the Configuration Wizard:

           ./config.sh
    	

    3. In the Welcome screen, select Extend an existing WebLogic domain, and click Next.

    4. In the WebLogic Domain Directory screen, select the following WebLogic domain directory, $ORACLE_BASE/admin/domain_name/aserver/domain_name Example: /u01/app/oracle/product/admin/aserver/edg_domain.

    Click Next.


    (click image for full view)

    5. In the Select Extension Source screen, do the following:

      5.1 Select Extend my domain automatically to support the following added products
      • Oracle Business Activity Monitoring 11.1.1.0 [soa]

      Click Next.


      (click image for full view)

    6. The warning message CFGFWMK-64061 may appear. Select Replace existing component and click OK


    (click image for full view)

    7. In the Configure JDBC Component Schema screen do the following:

      7.1. Select BAM Schema.

      7.2. Select Configure selected component schemas as RAC multi data source schemas in the next panel.

      Enter values for the following fields:

      • Driver: Oracle driver (Thin) for RAC Service-Instance connections, Versions:10, 11.
      • Service Name: Enter the service name of the database; for example, ORCL
      • User Name: Enter the BAM complete user name for the schema; example DEV_ORABAM
      • Password: Enter the password to use to access the schema

      7.3. Click Add and enter the details for the first and second RAC instance. For example:

      • HostName: 10.0.10.89 (used SCAN address)
      • Instance Name: ORCL1
      • HostName: 10.0.10.89 (used SCAN address)
      • Instance Name: ORCL2

    Click Next.


    (click image for full view)

    8. In the Test JDBC Data Sources screen, the connections should be tested automatically. The Status column displays the results. Ensure that all connections were successful. Click Next.


    (click image for full view)

    9. In the Select Optional Configuration screen, select the following:

    • Managed Servers, Clusters, and Machines
    • Deployments and Services
    • JMS File Store

    Click Next.


    (click image for full view)

    10. In the Select JMS Distributed Destination Type screen, select UDD from the drop-down list for all Fusion Middleware Components' JMS Modules.

    11. In the Configure Managed Servers screen, rename the bam_server1 server to WLS_BAM1.


    (click image for full view)

    12. Click on Add and add a new server called WLS_BAM2. Give these servers the attributes shown in the picture.


    (click image for full view)

    13. In the Configure Clusters screen, add the following cluster:

    • Name: BAM_Cluster
    • Cluster Address: leave it empty


    (click image for full view)

    14. In the Assign Servers to Clusters screen, add WLS_BAM1 and WLS_BAM2 to the BAM_Cluster. Do not modify the other assignments that display in this screen; leave them as they are.


    (click image for full view)

    15. In the Configure Machines screen, do the following:

      15.1 Delete the LocalMachine that appears by default.

      15.2 Click the Unix Machine tab. You should add the BAMHOST1 and BAMHOST2 machines and have the following entries:


    (click image for full view)

    16. In the Assign Servers to Machines screen, do the following:

    • Assign WLS_BAM1 to BAMHOST1
    • Assign WLS_BAM2 to BAMHOST2

    Click Next.

    17. In the Target Deployments to Clusters or Servers screen, ensure the following targets:

    • usermessagingserver and usermessagingdriver-email should be targeted only to SOA_Cluster and BAM_Cluster. (The usermessaging-xmpp, usermessaging-smpp, and usermessaging-voicexml applications are optional.)
    • WSM-PM should be targeted only to WSM-PM_Cluster.
    • The DMS Application should be targeted to BAM_Cluster, SOA_Cluster, WSM-PM_Cluster and Admin Server.
    • Target the oracle.sdp.* library only to SOA_Cluster and BAM_Cluster. Target the oracle.soa.* library only to SOA_Cluster.
    • Target the oracle.rules.* library to SOA_Cluster, BAM_Cluster and Admin Server.
    • The oracle.wsm.seedpolicies library should be targeted only to the WSM-PM_Cluster.
    • oracle.bam* is targeted only to BAM_Cluster.

    Click Next.


    (click image for full view)

    18. In the Target Services to Clusters or Servers screen, ensure the following targets:

    • mds-owsm, mds-owsm-rac0, and mds-owsm-rac1 should be targeted to both WSM-PM_Cluster and AdminServer.
    • mds-soa, mds-soa-rac0, and mds-soa-rac1 should be targeted to both SOA_Cluster and AdminServer.
    • OraSDPMDatasource, OraSDPMDatasource-rac0, and OraSDPMDatasource-rac1 should be targeted to both SOA_Cluster and BAM_Cluster.

    Click Next.


    (click image for full view)

    19. In the Configuration Summary screen, click Extend.


    (click image for full view)

    20. In the Configure JMS File Stores screen, enter the shared directory location example: u01/app/oracle/admin/shared /jms

    21. In the Creating Domain screen, click Done.


    (click image for full view)

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

This is the official blog of the SOA Proactive Support Team. Here we will provide information on our activities, publications, product related information and more. Additionally we look forward to your feedback to improve what we do.

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today