18 Extending the Domain with Oracle SOA Suite for Healthcare Integration

The following topics describe the procedures for extending the domain to include Oracle SOA Suite for healthcare integration (Oracle Healthcare).

Parent topic: Configuring the Enterprise Deployment

18.1 Variables Used When Extending the Domain for Oracle Healthcare

As you perform the tasks in this chapter, you will be referencing the directory variables listed in this section.

The values for several directory variables are defined in File System and Directory Variables Used in This Guide.

  • ORACLE_HOME

  • ASERVER_HOME

  • MSERVER_HOME

  • OHS_DOMAIN_HOME

  • JAVA_HOME

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

  • ADMINVHN

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

  • SOAHOST1

  • SOAHOST2

  • WEBHOST1

  • WEBHOST2

18.2 About Oracle SOA Suite for Healthcare Integration in an Enterprise Deployment

Oracle SOA Suite for healthcare integration uses several features of Oracle SOA Suite to help you design, create, and manage applications that process healthcare data.

For more information about Oracle SOA Suite for Healthcare Integration, see “Introduction to Oracle SOA Suite for Healthcare Integration” in the Healthcare Integration User’s Guide for Oracle SOA Suite.

When you configure Oracle SOA Suite for Healthcare Integration in an enterprise deployment, Oracle recommends that you configure Healthcare in its own domain. For more information about this recommendation, see “B2B and Healthcare Domain Topology Best Practices” in the Healthcare Integration User’s Guide for Oracle SOA Suite.

Typically, you configure a single domain for Oracle SOA Suite for Healthcare Integration, and a separate domain for Oracle B2B. Both these domain topologies are described and supported in this enterprise deployment guide. For more information, see the following:

18.3 Prerequisites for Extending the Domain to Include Oracle Healthcare

Before extending the domain with Oracle Healthcare, note the following important prerequisites that are specific Oracle Healthcare.

  • You can extend an existing domain with the Oracle Healthcare software only if the domain was configured using the Oracle SOA Suite domain configuration template. You cannot extend an Oracle BPM, Oracle BAM, or Oracle OSB domain with Oracle Healthcare.

    This chapter assumes you have performed the steps in Extending the Domain with Oracle SOA Suite .

  • When you installed the Oracle SOA Infrastructure schema, as part of the Oracle SOA Suite installation and configuration, you should have set the Healthcare Integration RCU custom variable to YES. When you enter YES as the value for the Healthcare Integration custom variable, RCU creates additional materialized views in the database, which are required by the Healthcare Integration User Interface.

    If you entered NO, you can perform these additional schema configuration tasks later by running the following SQL script on the database. This script is installed in the Oracle Fusion Middleware Oracle home when you select the Healthcare with B2B installation type:

    ORACLE_HOME/soa/common/sql/soainfra/sql/oracle/b2b_mv.sql

In addition, ensure that your existing deployment meets the following general prerequisites for extending the domain

  • 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 Performing Backups and Recoveries in the SOA Enterprise Deployments.

  • Verify that you have installed the Infrastructure and SOA software binaries in an Oracle home on shared storage and they are available from SOAHOST1 and SOAHOST2.

  • You have already configured Node Manager, Administration Server, SOA Servers, and WSM Servers as described in previous chapters to run a SOA system. Optionally, you may have already configured Server migration, transaction logs, coherence, and all other configuration steps for the SOA System.

  • If you haven't done so already, verify that the system clocks on each host computer are synchronized. You can do this by running the date command as simultaneously as possible on the hosts in each cluster.

    Alternatively, there are third-party and open-source utilities you can use for this purpose.

18.4 Installing Oracle Healthcare for an Enterprise Deployment

Use the following sections to install the Oracle Fusion Middleware Infrastructure software in preparation for configuring a new domain for an enterprise deployment.

18.4.1 Starting the Oracle B2B and Healthcare Installer on SOAHOST1

To start the installation program, perform the following steps.

  1. Log in to SOAHOST1.
  2. Go to the directory where you downloaded the installation program.
  3. Launch the installation program by invoking the java executable from the JDK directory on your system, as shown in the example below. 
    JAVA_HOME/bin/java -d64 -jar distribution_file_name.jar

    In this example:

    • Replace JAVA_HOME with the environment variable or actual JDK location on your system.

    • Replace distribution_file_name with the actual name of the distribution jar file.

      Note that if you download the distribution from the Oracle Technology Network (OTN), then the jar file is typically packaged inside a downloadable ZIP file.

      To install the software required for the initial Infrastructure domain, the distribution you want to install is fmw_12.2.1.0.0_b2bhealthcare.jar.

      For more information about the actual file names of each distribution, see Identifying and Obtaining Software Downloads for an Enterprise Deployment.

When the installation program appears, you are ready to begin the installation. See Navigating the Installation Screens for a description of each installation program screen.

18.4.2 Navigating the Installation Screens for Oracle Healthcare Installation

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

Table 18-1 Oracle B2B and Healthcare InstallScreens

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.

Auto Updates

Use this screen to automatically search My Oracle Support for available patches or automatically search a local directory for patches that you’ve already downloaded for your organization.

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 Healthcare

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.

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.

18.4.3 Verifying the B2B or Healthcare Installation

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

18.4.3.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.

18.4.3.2 Checking the Directory Structure

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

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

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

Common
STANDARDS
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.

18.4.3.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.

18.5 Running the Configuration Wizard for Oracle Healthcare

To extend the domain to include Oracle Healthcare, refer to the following sections.

18.5.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 Starting the Configuration Wizard on SOAHOST1.

  2. Navigate to the following directory and start the WebLogic Server Configuration Wizard. 
    ORACLE_HOME/oracle_common/common/bin
./config.sh

18.5.2 Navigating the Configuration Wizard Screens for Oracle Healthcare

Follow the instructions in this section to extend the domain for Oracle Healthcare.

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 Creating the Initial Infrastructure Domain for an Enterprise Deployment.

For more information about the directory location variables, see 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 SOA Suite for healthcare integration — 12.2.1.0 [soa]

    Selecting this template automatically selects the following as a dependency:

    Oracle B2B — 12.2.1.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.2.1.0 [wlserver]

  • Oracle SOA Suite 12.2.1.0 [soa]

  • Oracle Enterprise Manager - 12.2.1.0 [em]

  • Oracle WSM Policy Manager - 12.2.1.0 [oracle_common]

  • Oracle JRF - 12.2.1.0 [oracle_common]

  • WebLogic Coherence Cluster Extension - 12.2.1.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. Oracle Healthcare 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. Oracle Healthcare 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 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.

18.6 Starting the Healthcare Components

This topic explains how to start the Oracle Healthcare components you have configured in the domain. The procedure requires you to restart the Managed Server where Oracle Healthcare has been configured. This ensures that the configuration changes and startup scripts are updated and validated correctly. Because you are extending an existing domain, the Administration Server and respective Node Managers are already running in on both application server hosts.

To start the Healthcare components, restart the Managed Servers:
  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 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 Console page to verify shutdown status.
  6. Select WLS_SOA1 from the Servers column of the table.
  7. Click Start.
  8. Repeat steps 4 through 7 for the WLS_SOA2 Managed Server.

18.7 Updating the B2B Instance Identifier and MLLP High Availability Mode

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

  1. Log in to Oracle Enterprise Manager Fusion Middleware Control with the user name and password specified for the domain administration.
  2. If not already displayed, click the Target Navigation icon Target Navigation icon in Fusion Middleware Control in the top left corner of the page to display the Target Navigation pane.
  3. 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 instances, then add the property only once.
  4. Click More B2B Configuration Properties... .
    When you click this link, Fusion Middleware Control displays the MBean browser, so you can make modifications to specific B2B MBean properties.
  5. Click the b2b MBean.
    B2BConfig b2b should already be selected.
  6. Click the Operations tab.
  7. Click addProperty in the list of operations.
  8. In the Key field enter b2b.HAInstance.
  9. In the Value field enter true.
    This property is stored in the MDS repository and must be created only once for the cluster.
  10. Click Invoke.
    A message should display, confirming that the property has been added.
  11. Click Return to return to the B2B Properties list.
  12. Click the Operations tab.
  13. Click addProperty to add another property.
  14. In the Key field enter b2b.MLLP_HA_Mode.
  15. In the Value field enter true.
  16. Click Invoke.
After you define high availability properties, you can view them on the Attributes tab. To view the properties, click the Attributes tab and then click Properties. Expand the Element nodes in the Value table to verify the property names and values.

18.8 Disabling Connection Factory Affinity for Optimum Load Balancing

To avoid the possibility of all the load affecting one Oracle Healthcare server, Oracle recommends that you perform the following steps.

  1. Log in to the WebLogic Administration Console Control with the user name and password specified for the domain administration.
  2. In the left navigation tree, expand Services, and then Messaging.
  3. Click JMS Modules.
  4. Click SOAJMSModule on the table.
  5. Click B2BEventQueueConnectionFactory.
  6. Click the Load Balance tab.
  7. Click Lock and Edit on the Change Center Menu.
  8. Clear the Server Affinity Enabled check box.
  9. Click Save and Activate the changes.

18.9 Configuring Oracle HTTP Server for Oracle Healthcare

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 Healthcare requests correctly to the Oracle SOA Suite cluster.

To enable Oracle HTTP Server to route requests to Oracle Healthcare:

  1. Log in to WEBHOST1 and change directory to the configuration directory for the first Oracle HTTP Server instance (ohs1): 
    cd OHS_DOMAIN_HOME/config/fmwconfig/components/OHS/ohs1/moduleconf
  2. Add the following directives inside the <VirtualHost> tag in the soa_vh.conf file: 
    <Location /healthcare>
    SetHandler weblogic-handler
    WebLogicCluster SOAHOST1:8001,SOAHOST2:8001
    WLProxySSL ON
    WLProxySSLPassThrough ON
</Location>
  3. Update the soainternal_vh.conf file with the following directive: 
    <Location /healthcare>
    SetHandler weblogic-handler
    WebLogicCluster SOAHOST1:8001,SOAHOST2:8001
    WLProxySSL ON
    WLProxySSLPassThrough ON
</Location>
  4. Restart the ohs1 instance:
    1. Change directory to the following location: 
      cd OHS_DOMAIN_HOME/bin
    2. Enter the following commands to stop and start the instance: 
      ./stopComponent.sh ohs1
./startComponent.sh ohs1
  5. Log in to WEBHOST2 and copy the soa_vh.conf file and soainternal_vh.conf file to the configuration directory for the second Oracle HTTP Server instance (ohs_2): 
    OHS_DOMAIN_HOME/config/fmwconfig/components/OHS/ohs2/moduleconf
  6. Edit the soa_vh.conf and soainternal_vh.conf files to change any references to WEBHOST1 to WEBHOST2.
  7. Restart the ohs2 instance:
    1. Change directory to the following location: 
      cd OHS_DOMAIN_HOME/bin
    2. Enter the following commands to stop and start the instance: 
      ./stopComponent.sh ohs2
./startComponent.sh ohs2

18.10 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 Configuring Roles for Administration of Oracle SOA Suite Products.

18.11 Validating Access to Oracle Healthcare 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 Oracle Healthcare Components on the Oracle SOA Suite Managed Server.

Note:

When you previously configured the Oracle SOA Suite Managed Servers, you should have enabled the WebLogic Plug-in. If have not performed this task, then see Configuring the WebLogic Proxy Plug-In.

  1. Enter the following URL to access the Oracle Healthcare User Interface through the load balancer: 
    https://soa.example.com/healthcare

    You should see the Oracle Healthcare User Interface screen.

    Description of GUID-B88BA296-80AD-4CFC-9CDB-85643246E69A-default.png follows
    Description of the illustration GUID-B88BA296-80AD-4CFC-9CDB-85643246E69A-default.png
  2. Log in using weblogic_soa user.

    For more information, see “Using the Oracle SOA Suite for Healthcare Integration User Interface” in the Healthcare Integration User’s Guide for Oracle SOA Suite.

18.12 Backing Up the Configuration

It is an Oracle best practices recommendation to create a backup after successfully configuring 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 Performing Backups and Recoveries for an Enterprise Deployment.

18.13 Enabling Automatic Service Migration for Oracle Healthcare

In the enterprise topology, Oracle Healthcare is configured on the existing Oracle SOA Suite Managed Servers. If you have already configured automatic service migration for the SOA_Cluster, then the Oracle Healthcare software is already protected by automatic service migration.

If you have not configured automatic service migration for the Managed Servers where Oracle Healthcare is configured, then see Configuring Automatic Service Migration in an Enterprise Deployment.

For additional high availability, you can also configure your transaction logs store and JMS store in a database. For more information, see Using JDBC Persistent Stores for TLOGs and JMS in an Enterprise Deployment.