17 Extending the Domain with Oracle B2B

This chapter describes the procedures for extending the domain to include Oracle B2B.

Note:

This revision of the Enterprise Deployment Guide does not provide instructions for configuring Oracle SOA for Healthcare in a highly available enterprise deployment.

For information about installing and configuring Oracle SOA for Healthcare for high availability, see the following sections of the Healthcare Integration User's Guide for Oracle SOA Suite:

This chapter contains the following sections:

17.1 Variables Used in This Chapter

As you perform the tasks in this chapter, you will be asked to enter the following values for several directory variables defined in Section 7.4, "File System and Directory Variables Used in This Guide".

  • ORACLE_HOME

  • ASERVER_HOME

  • MSERVER_HOME

  • JAVA_HOME

In addition, you'll be referencing the following virtual IP (VIP) addresses defined in Section 5.2.3, "Physical and Virtual IP Addresses Required by the Enterprise Topology":

  • ADMINVHN

  • SOAHOST1VHN1

  • SOAHOST2VHN1

Actions in this chapter will be performed on the following host computers:

  • SOAHOST1

  • SOAHOST2

  • WEBHOST1

  • WEBHOST2

17.2 Prerequisites for Extending the SOA Domain to Include Oracle B2B

Before extending the current domain, ensure that your existing deployment meets the following prerequisites:

  • Back up the installation - If you have not yet backed up the existing Fusion Middleware Home and domain, Oracle recommends backing it up now.

    To back up the existing Fusion Middleware Home and domain, see Section 18.2.6, "Performing Backups and Recoveries in the SOA Enterprise Deployments."

  • There is an existing WL_HOME and SOA ORACLE_HOME (binaries) installed in previous chapters on a shared storage and available from SOAHOST1 and SOAHOST2.

  • Node Manager, Admin Server, SOA Servers and WSM Servers exist and have been configured as described in previous chapters to run a SOA system.

  • You do not need to run RCU to load additional schemas for B2B, these are part of the SOA repository and were loaded into the DB in the SOA chapter.

17.3 Installing Oracle B2B for an Enterprise Deployment

To start the installation program, perform the following steps.

  1. Log in to the target system, SOAHOST1.

  2. Go to the directory in which you downloaded the installation program.

  3. Set the path for the java executable:

    export JAVA_HOME=JAVA_HOME
export PATH=$JAVA_HOME/bin:$PATH

    In this example, replace JAVA_HOME with the value this variable listed in Section 7.4, "File System and Directory Variables Used in This Guide" and entered in the Enterprise Deployment Workbook.

  4. Launch the installation program by entering the following command:

    java -d64 -jar fmw_12.1.3.0.0_b2bhealthcare.jar

    When the installation program appears, you are ready to begin the installation.

17.3.1 Navigating the Oracle B2B Installation Screens

Table 17-1 provides description of each installation program screen.

Table 17-1 Oracle B2B Install Screens

Screen Description

Installation Inventory Setup

On UNIX operating systems, this screen will appear if this is the first time you are installing any Oracle product on this host. Specify the location where you want to create your central inventory. Make sure that the operating system group name selected on this screen has write permissions to the central inventory location.

For more information about the central inventory, see "Understanding the Oracle Central Inventory" in Installing Software with the Oracle Universal Installer.

Welcome

This screen introduces you to the product installer.

Installation Location

Use this screen to specify the location of your Oracle home directory.

For more information about Oracle Fusion Middleware directory structure, see "Selecting Directories for Installation and Configuration" in Planning an Installation of Oracle Fusion Middleware.

Installation Type

Use this screen to select the type of installation and consequently, the products and feature sets you want to install.

  • Select Oracle B2B

NOTE: The topology in this document does not include the examples, Oracle strongly recommends that you do not install the examples into a production environment.

Prerequisite Checks

This screen verifies that your system meets the minimum necessary requirements.

If there are any warning or error messages, you can refer to one of the following documents in Section 1.4.

Specify Security Updates

If you already have an Oracle Support account, use this screen to indicate how you would like to receive security updates.

If you do not have one and are sure you want to skip this step, clear the check box and verify your selection in the follow-up dialog box.

Installation Summary

Use this screen to verify the installation options you selected. If you want to save these options to a response file, click Save Response File and provide the location and name of the response file. Response files can be used later in a silent installation situation.

For more information about silent or command line installation, see "Using the Oracle Universal Installer in Silent Mode" in Installing Software with the Oracle Universal Installer.

Click Install to begin the installation.

Installation Progress

This screen allows you to see the progress of the installation.

Click Next when the progress bar reaches 100% complete.

Installation Complete

Review the information on this screen, then click Finish to dismiss the installer.

17.3.2 Verifying the Installation

After you complete the installation, you can verify it by successfully completing the following tasks:

17.3.2.1 Reviewing the Installation Log Files

Review the contents of the installation log files to make sure that no problems were encountered. For a description of the log files and where to find them, see "Understanding Installation Log Files" in Installing Software with the Oracle Universal Installer.

17.3.2.2 Checking the Directory Structure

The contents of your installation vary based on the options you selected during the installation.

The addition of Oracle B2B will add the following directory and sub-directories:

ls  /u01/oracle/products/fmwnnnn/soa/soa/thirdparty/edifecs/

Common  XEngine

For more information about the directory structure you should see after installation, see "What are the Key Oracle Fusion Middleware Directories?" in Understanding Oracle Fusion Middleware.

17.3.2.3 Viewing the Contents of Your Oracle Home

You can also view the contents of your Oracle home using the viewInventory script. For more information, see "Viewing the contents of an Oracle home" in Installing Software with the Oracle Universal Installer.

17.4 Running the Configuration Wizard on SOAHOST1 to Extend a SOA Domain to Include B2B

To extend the domain to include Oracle BAM, refer to the following sections:

17.4.1 Starting the Configuration Wizard

Note:

If you added any customizations directly to the start scripts in the domain, those will be overwritten by the configuration wizard. To customize server startup parameters that apply to all servers in a domain, you can create a file called setUserOverrides.sh and configure it, for example, add custom libraries to the WebLogic Server classpath, specify additional java command line options for running the servers, or specify additional environment variables. Any customizations you add to this file are preserved during domain upgrade operations, and are carried over to remote servers when using the pack and unpack commands.

To begin domain configuration:

  1. Shut down the Administration Server to prevent any configuration locks, saves, or activations from occurring during the configuration of the domain.

    For more information, see the instructions for shutting down the Administration Server with Node Manager in Section 11.3.1.

  2. Navigate to the following directory and start the WebLogic Server Configuration Wizard.

    ORACLE_HOME/oracle_common/common/bin
./config.sh

17.4.2 Navigating the Configuration Wizard Screens to Create the Domain

Follow the instructions in this section to extend the domain for B2B.

Note:

You can use the same procedure described in this section to extend an existing domain. If your needs do not match the instructions given in the procedure, be sure to make your selections accordingly, or refer to the supporting documentation for additional details.

Domain creation and configuration includes the following tasks:

Task 1   Selecting the Domain Type and Domain Home Location

On the Configuration Type screen, select Update an existing domain.

In the Domain Location field, select the value of the ASERVER_HOME variable, which represents the complete path to the Administration Server domain home you created in Chapter 10, "Creating the Initial Infrastructure Domain for an Enterprise Deployment".

For more information about the directory location variables, see Section 7.4, "File System and Directory Variables Used in This Guide"

Tip:

More information about the other options on this screen can be found in Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.
Task 2   Selecting the Configuration Template

On the Templates screen, make sure Update Domain Using Product Templates is selected, then select the following templates:

  • Oracle B2B - 12.1.3.0 [soa]

In addition, the following additional templates should already be selected, because they were used to create the initial domain and extend it to SOA:

  • Basic Weblogic Server Domain - 12.1.3.0 [wlserver]

  • Oracle SOA Suite 12.1.3.0 [soa]

  • Oracle HTTP Server (Collocated) 12.1.3.0 [ohs]

  • Oracle Enterprise Manager Plugin for WEBTIER 12.1.3.0 [em]

  • Oracle Enterprise Manager - 12.1.3.0 [em]

  • Oracle WSM Policy Manager - 12.1.3.0 [oracle_common]

  • Oracle JRF - 12.1.3.0 [oracle_common]

  • WebLogic Coherence Cluster Extension - 12 1.3.0 [wlserver]

Tip:

More information about the options on this screen can be found in Templates in Creating WebLogic Domains Using the Configuration Wizard.
Task 3   Specifying the Datasource Configuration Type

All fields are pre-populated, because you already configured the domain to reference the Fusion Middleware schemas that are required for the Infrastructure domain. B2B uses the existing DataSources for SOA and no new Datasources need to be added to the domain.

Note:

Any custom data sources that were created before the extension (like LEASING data sources) will show up before this screen. Check the Datasources row and click Next. The test data source screen will verify its validity. Click Next.
Task 4   Selecting Advanced Configuration

To complete domain configuration for the topology, do not select any additional options on the Advanced Configuration screen and Click Next. B2B applications and required artifacts will be targeted automatically to the existing SOA servers

Task 5   Reviewing Your Configuration Specifications and Configuring the Domain

The Configuration Summary screen contains the detailed configuration information for the domain you are about to create. Review the details of each item on the screen and verify that the information is correct.

You can go back to any previous screen if you need to make any changes, either by using the Back button or by selecting the screen in the navigation pane.

Domain creation will not begin until you click Domain Update.

Tip:

More information about the options on this screen can be found in Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.
Task 6   Writing Down Your Domain Home and Administration Server URL

The Configuration Success screen will show the following items about the domain you just configured:

  • Domain Location

  • Administration Server URL

You must make a note of both items as you will need them later; the domain location is needed to access the scripts used to start the Node Manager and Administration Server, and the URL is needed to access the Administration Server.

Click Finish to dismiss the configuration wizard.

Task 7   Start the Administration Server

Start the Administration Server to ensure the changes you have made to the domain have been applied.

17.5 Starting the B2B Suite Components

For configuration changes and start scripts to be effective, you must restart the WLS_SOA server to which B2B has been added. Since B2B extends an already existing SOA system, the Administration Server and respective Node Managers are already running in SOAHOST1 and SOAHOST2.

To start the added B2B components:

  1. Restart the WLS_SOA1 managed server:

    1. Log into the Oracle WebLogic Server Administration Console at:

      http://ADMINVHN:7001/em

      In this example:

      Replace ADMINVHN with the host name assigned to the ADMINVHN Virtual IP address in Section 5.3, "Identifying and Obtaining Software Downloads for an Enterprise Deployment".

      Port 7001 is the typical port used for the Administration Server console and Fusion Middleware Control. However, you should use the actual URL that was displayed at the end of the Configuration Wizard session when you created the domain.

    2. In the Domain Structure window, expand the Environment node, then select Servers.

      The Summary of Servers page appears.

    3. Click the Control tab.

    4. Select WLS_SOA1 from the Servers column of the table.

    5. Click Shutdown. Wait for the shutdown to complete (refresh the WebLogic Server Console page to verify shutdown status).

    6. Click Start.

  2. Repeat steps a-f for WLS_SOA2.

17.6 Updating the B2B Instance Identifier for Transports

To set up File, FTP, or Email transports in a high availability environment, set the b2b.HAInstance property to true.

To do this follow these steps:

  1. Log in to Oracle Enterprise Manager Fusion Middleware Control with the user name and password specified for the domain administration.

  2. On the navigation tree on the left, expand SOA, and then right click on the soa-infra(server_name), and select the SOA Administration, and then B2B Server Properties.

    If there are multiple soa-infra (server_name), add the property only once.

  3. Click on More B2B Configuration Properties... on the right.

  4. Click the B2B MBean. B2BConfig b2b should already be selected.

  5. Click the Operations tab.

  6. Click addProperty in the list on the right.

  7. In the Key field enter b2b.HAInstance.

  8. In the value field enter true.

    This property is stored in MDS and needs to be created only once for the cluster.

  9. Click Invoke.

17.7 Configuring Oracle HTTP Server for Oracle B2B

Make the following modifications to the Oracle HTTP Server instance configuration files to ensure that the Oracle HTTP Server instances in the Web tier can route Oracle B2B requests correctly to the Oracle B2B software on the Oracle SOA Suite cluster.

To enable Oracle HTTP Server to route requests to Oracle B2B Console and to Oracle B2B services:

  1. Log in to SOAHOST1 and change directory to the configuration directory for the first Oracle HTTP Server instance (OHS_1):

    cd ASERVER_HOME/config/fmwconfig/components/OHS/OHS_1/

  2. Add the following directives inside the <VirtualHost> tag in the soa_vh.conf file:

    # B2B
<Location /b2bconsole>
SetHandler weblogic-handler
WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001
</Location>

# B2B
<Location /b2b/services>
SetHandler weblogic-handler
WebLogicCluster SOAHOST1VHN1:8001,SOAHOST2VHN1:8001
</Location>

  3. Change directory to the following location so you can update the configuration file for the second Oracle HTTP Server instance (OHS_2):

    cd ASERVER_HOME/config/fmwconfig/components/OHS/OHS_2/

  4. Open the soa_vh.conf file and add the B2B directives to the <VirualHost> tag.

  5. Restart the Administration Server.

  6. After the Administration Server is running, review the files in the following directories on both WEBHOST1 and WEBHOST2 to be sure they contain the modifications made in the Administration Server domain directory:

    MSERVER_HOME/config/fmwconfig/components/OHS/instances/OHS_1/

    MSERVER_HOME/config/fmwconfig/components/OHS/instances/OHS_2/

  7. Restart the Oracle HTTP Server instances on WEBHOST1 and WEBHOST2.

17.8 Adding the B2BAdmin Role to the SOA Administrators Group

Before you validate the Oracle B2B configuration on the Managed Servers, add the B2BAdmin administration role to the enterprise deployment administration group (SOA Administrators).

To perform this task, refer to Section 18.2.1, "Configuring Roles for Administration of Oracle SOA Suite Products".

17.9 Validating Access to Oracle B2B Through the Load Balancer

Use the following steps to verify that the appropriate routing and failover is working from the load balancer to the HTTP Server instances to the B2B Suite Components on the Oracle SOA Suite Managed Server

  1. Enter the following URL to access the Oracle B2B Console through the load balancer:

    https://soa.example.com/b2bconsole

  2. Log in using weblogic_soa user. You should see the Oracle B2B Partner, Agreement, and Profile screen, as shown in Figure 17-1.

    Figure 17-1 Oracle B2B Partner, Agreement, and Profile Screen

    Description of Figure 17-1 follows
    Description of ''Figure 17-1 Oracle B2B Partner, Agreement, and Profile Screen''

  3. Enter the following URL to access the Oracle B2B Web services endpoint:

    https://soa.example.com/b2b/services

    You should see the links to the different B2B endpoints test.

    Figure 17-2 Oracle B2B Services

    Description of Figure 17-2 follows
    Description of ''Figure 17-2 Oracle B2B Services''

17.10 Backing Up the Oracle B2B Configuration

It is an Oracle best practices recommendation to create a backup after successfully extending a domain or at another logical point. Create a backup after verifying that the installation so far is successful. This is a quick backup for the express purpose of immediate restoration in case of problems in later steps.

The backup destination is the local disk. You can discard this backup when the enterprise deployment setup is complete. After the enterprise deployment setup is complete, you can initiate the regular deployment-specific Backup and Recovery process.

For information about backing up your configuration, see Section 18.2.6, "Performing Backups and Recoveries in the SOA Enterprise Deployments."

17.11 Enabling Whole Server Migration for Oracle B2B

In the enterprise topology, Oracle B2B is configured on the existing Oracle SOA Suite Managed Servers. If you have already configured Whole Server Migration for the SOA_Cluster, then the Oracle B2B software is already protected by Whole Server Migration.

If you have not configured Whole Server Migration for the Managed Servers where Oracle B2B is configured, then see Chapter 19, "Using Whole Server Migration and Service Migration in an Enterprise Deployment".