1 Planning Your B2B and Healthcare Installation

This chapter helps to prepare you for installing and configuring B2B and Healthcare.

Various topics are covered that should be reviewed thoroughly to help ensure that you do not encounter any problems either during or after the product installation and domain configuration.

This chapter contains the following sections:

1.1 Using This Document

This section contains the following topics:

1.1.1 Using the Standard Installation Topology as a Starting Point

This guide will help you create the standard installation topology for B2B and Healthcare (Figure 1-1 and Figure 1-2). These topologies can be extended to be highly available and secure, making them suitable for a production system.

The standard installation topology represents a sample topology for this product; it is not the only topology that is supported. For more information, see "Understanding the Standard Installation Topology" in Planning an Installation of Oracle Fusion Middleware.

1.1.2 Using this Document in an Upgrade Scenario

If you are installing B2B and Healthcare as part of an upgrade procedure, follow the instructions in this book to install the software, but do not run the Configuration Wizard to create a WebLogic domain.

After the software is installed, see Upgrading Oracle SOA Suite and Business Process Management.

1.1.3 Using this Document to Extend a Domain

The instructions in this document describe how to create a new domain, and assumes that no other Oracle Fusion Middleware products are installed on your system. All of the instructions for installation and domain creation are based on this assumption.

In the event that you already have other Oracle Fusion Middleware products installed on your system (for example, you already have Oracle Fusion Middleware Infrastructure or SOA Suite installed with a domain that is up and running), the same instructions can be used to extend your existing domain. If you choose to do this, ensure that you read "Installing Multiple Products in the Same Domain" in Planning an Installation of Oracle Fusion Middleware for important information.

If you are creating a new domain, but your needs do not match the instructions given in the procedure, ensure that you make your selections accordingly and refer to the supporting documentation for additional details.

1.1.4 Understanding the Configuration Options

You can use this document to configure Oracle B2B and Healthcare in the following options:

  • Oracle B2B in a WebLogic Domain

    You select the B2B Install type and then select the B2B template while configuring to create a standard WebLogic domain.

  • Healthcare in a WebLogic Domain

    You select the Healthcare Install type and then select the Healthcare template while configuring to create a standard WebLogic domain for Healthcare.

  • HIPAA Compliant Healthcare

    You select the B2B Install type and also select the B2B template while configuring. After configuring the domain, you can still use the B2B user interface to exchange HIPAA (healthcare) documents. You can use this configuration option if you want to configure just B2B, but still take advantage of Healthcare without configuring the Healthcare libraries.

For more information, see Section 1.8.

1.2 Understanding the Standard Installation Topologies

This section contains the following topics:

1.2.1 Understanding the B2B Standard Installation Topology

Figure 1-1 shows the standard installation topology for B2B.

Figure 1-1 B2B Standard Installation Topology

Description of Figure 1-1 follows
Description of "Figure 1-1 B2B Standard Installation Topology"

1.2.2 Understanding the Healthcare Standard Installation Topology

Figure 1-2 shows the standard installation topology for Healthcare.

Figure 1-2 Healthcare Standard Installation Topology

Description of Figure 1-2 follows
Description of "Figure 1-2 Healthcare Standard Installation Topology"

1.2.3 Understanding the Elements in the Standard Installation Topology Illustrations

Table 1-1 describes all elements of the topology illustration from Figure 1-1 and Figure 1-2.

Table 1-1 Description of the Elements in the B2B and Healthcare Standard Installation Topologies

Element Description and Links to Additional Documentation

APPHOST

Standard term used in Oracle documentation referring to the machine that is hosting the application tier.

DBHOST

Standard term used in Oracle documentation referring to the machine that is hosting the database.

WebLogic Domain

A logically related group of Java components (in this case, the administration Server, Managed Servers, and other related software components).

For more information, see "What is an Oracle WebLogic Server Domain" in Understanding Oracle Fusion Middleware.

Administration Server

The central control entity of a domain which maintains the domain's configuration objects and distributes configuration changes to Managed Servers.

For more information, see "What is the Administration Server" in Understanding Oracle Fusion Middleware.

Enterprise Manager

Oracle Enterprise Manager Fusion Middleware Control. This is the main tool that can be used to manage your domain.

For more information, see "Oracle Enterprise Manager Fusion Middleware Control" in Understanding Oracle Fusion Middleware.

Cluster

A collection of multiple WebLogic Server instances running simultaneously and working together.

For more information, see "Understanding Managed Servers and Managed Server Clusters" in Understanding Oracle Fusion Middleware.

Machine

Logical representation of the computer that hosts one or more WebLogic Server instances (servers). Machines are also the logical glue between WebLogic Managed Servers and the Node Manager; in order to start or stop a Managed Server with Node Manager, the Managed Server must be associated with a machine.

Managed Server

Host for your applications, application components, Web services, and their associated resources.

For more information, see "Understanding Managed Servers and Managed Server Clusters" in Understanding Oracle Fusion Middleware.

Infrastructure

Collection of services that include the following:

  • Metadata repository (MDS)

    This contains metadata for Oracle Fusion Middleware components, such as the Oracle Application Developer Framework.

    For more information, see "What is the Metadata Repository" in Understanding Oracle Fusion Middleware.

  • Oracle Application Developer Framework (Oracle ADF)

  • Oracle Web Services Manager (OWSM)

SOA

Collection of Oracle SOA Suite services that include the following:

  • SOA Core Components

  • Oracle Enterprise Scheduler

  • BAM Components

  • Foundation Pack

  • Managed File Transfer Interface

  • Event Processing

  • Enterprise manager Plugin for SOA

  • Enterprise manager Plugin for BAM

  • Enterprise manager Plugin for ESS

1.3 Roadmap for Installing and Configuring the Standard Installation Topologies

This guide provides all the steps required to install and configure the standard installation topologies. Within the procedures, the guide also provides references to additional information you can use if you want to create a modified version of this topology.

Table 1-2 shows the steps required to install and configure the topology.

Table 1-2 B2B and Healthcare Installation Roadmap

Task Description Documentation

Verify your system environment

Before beginning the installation, verify that the minimum system and network requirements are met.

See Section 1.4.

Obtain the appropriate distribution

Both B2B and Healthcare require an existing Oracle Fusion Middleware Infrastructure installation and Oracle SOA Suite; B2B and Healthcare must be installed in the same Oracle home as Oracle Fusion Middleware Infrastructure and Oracle SOA Suite.

You have a separate distribution for B2B and Healthcare, and the distribution is called fmw_12.1.3.0.0_b2b.jar.

See Section 1.5.

Determine your installation directories

Verify that the directories that will need to be created can be created or accessed by the installer, and exist on systems that meet the minimum requirements.

B2B and Healthcare must be installed into an existing Oracle home directory containing Oracle Fusion Middleware Infrastructure and Oracle SOA Suite.

See "What are the Key Oracle Fusion Middleware Directories?" in Understanding Oracle Fusion Middleware.

Install Oracle Fusion Middleware Infrastructure

Install Oracle Fusion Middleware Infrastructure to create the Oracle home directory for B2B and Healthcare.

See Installing and Configuring the Oracle Fusion Middleware Infrastructure.

Install Oracle SOA Suite

Oracle SOA Suite must be installed before you can begin installing B2B and Healthcare.

See Installing and Configuring Oracle SOA Suite Foundation and Business Process Management.

Install the software

Run the Oracle Universal Installer to install B2B and Healthcare.

Installing software transfers the software to your system and creates the Oracle home directory.

See Chapter 2.

Select a database profile and review any requirements for Oracle SOA Suite and Healthcare Integration

Before you install the required schemas in the database, review the information about the custom variables you will need to set for the Oracle SOA Suite and Oracle B2B and Healthcare schemas.

See Section 1.9.

Create the schemas

Run the Repository Creation Utility (RCU) to create the schemas required for configuration.

See Section 3.1.

Create a WebLogic domain

Use the configuration wizard to create and configure the WebLogic domain.

See Section 3.2 if you are creating the topology for B2B or HIPAA.

See Chapter 4 if you are creating the topology for Healthcare.

Administer and prepare your domain for high availability

Discover additional tools and resources to administer your domain and configure your domain to be highly available.

See Chapter 5.

1.4 Roadmap for Verifying Your System Environment

Table 1-3 contains important information that you must read and understand prior to beginning the installation and configuration process. It identifies important tasks and checks that you must perform to make sure that your environment is properly prepared for installing and configuring B2B and Healthcare.

Table 1-3 Roadmap for Verifying Your System Environment

Task Description Documentation

Verify certification and system requirements

Verify that your operating system is certified and properly configured for installation and configuration.

See "Verifying Certification and System Requirements" in Planning an Installation of Oracle Fusion Middleware.

Identify a proper installation user

Verify that the installation user has the proper permissions to install and configure the software.

See "Selecting an Installation User" in Planning an Installation of Oracle Fusion Middleware.

Select the installation and configuration directories on your system

Verify that you are able to create the necessary directories for installation and configuration, according to the recommended directory structure.

See "Selecting Directories for Installation and Configuration" in Planning an Installation of Oracle Fusion Middleware.

Install a certified JDK

The installation program for the distribution requires a certified JDK present on your system.

See "Installing a JDK" in Planning an Installation of Oracle Fusion Middleware.

Install and configure an Oracle database

To configure your WebLogic domain, you must have access to a certified database that is properly configured for schemas required by B2B and Healthcare.

See "Installing and Configuring a Certified Database" in Planning an Installation of Oracle Fusion Middleware.

1.5 Understanding and Obtaining the Product Distributions

The distributions for Oracle Fusion Middleware Infrastructure, Oracle SOA, and Oracle B2B and Healthcare are available as .jar files. You must have a certified JDK already installed on your system in order to install and configure this distribution.

Tip:

For more information about distributions, see "Understanding and Obtaining Product Distributions" in Planning an Installation of Oracle Fusion Middleware.

For information on how to obtain the distribution, see "Obtaining Product Distributions" in Planning an Installation of Oracle Fusion Middleware.

1.6 Verifying the Installation Checklist

Table 1-4 lists important items that you must know before or decide during Oracle B2B or Healthcare installation.

Table 1-4 Installation Checklist

Information Example Value Description

JAVA_HOME

/home/Oracle/jdk7_55/jdk1.7.0_55

Environment variable that points to the Java JDK 1.7 home directory.

Database hostname

examplehost.exampledomain

Name and domain of the host where the database is running.

Database port

1521

Port number on which the database listens. The default Oracle database listen port is 1521.

Database service name

orcl

Oracle databases require a unique service name. The default service name is orcl.

DBA username

SYS

Name of user with database administration privileges. The default DBA user on Oracle databases is SYS.

DBA password

ExamplePassword1

Password of the user with database administration privileges.

ORACLE_HOME

/home/Oracle/product/Oracle_Home

The directory in which you will install your software. This directory will include Oracle Fusion Middleware Infrastructure, Oracle B2B or Healthcare, as well as Oracle SOA Suite and Oracle Business Process Management Suite, as needed.

WebLogic Server hostname

examplehost.exampledomain.com

Hostname for Oracle WebLogic Server and Oracle B2B and Healthcare consoles.

Console port

7001

Port for Oracle WebLogic Server and Oracle B2B and Healthcare consoles.

DOMAIN_HOME

/home/Oracle/config/domains/b2b_domain

Location in which your domain data is stored.

APPLICATION_HOME

/home/Oracle/config/applications/b2b_domain

Location in which your application data is stored.

Administrator user name for your WebLogic domain

weblogic

Name of user with Oracle WebLogic Server administration privileges. The default administrator user is weblogic.

Administrator user password

ExamplePassword1

Password of the user with Oracle WebLogic Server administration privileges.

$FTP_ROOT

${ORACLE_HOME}/b2b/ftp_root

Embedded FTP server root directory.

FTP Port

7021

Port for embedded FTP server.

RCU utility

ORACLE_HOME/oracle_common/bin

Path to the Repository Creation Utility (RCU).

RCU schema prefix

b2b or hc

The prefix for names of database schemas used by Oracle B2B and Healthcare.

RCU schema password

ExamplePassword1

The password for database schemas used by Oracle B2B and Healthcare.

Config utility

ORACLE_HOME/oracle_common/common/bin

Path to the configuration wizard for domain creation and configuration.

1.7 About Oracle B2B

Oracle B2B is an e-commerce gateway that enables the secure and reliable exchange of business documents between an enterprise and its trading partners. See "Protocols Supported in B2B" in User's Guide for B2B for a list of the industry-standard e-commerce protocols supported in Oracle B2B.

However, some Oracle B2B capabilities are included in a standard installation, so you can activate a limited version of Oracle B2B without installing Oracle B2B and configuring a compact domain. With these limited Oracle B2B capabilities, you can exchange only Custom Documents.

1.8 About Oracle SOA Suite for Healthcare Integration

Oracle SOA Suite for Healthcare Integration utilizes several features of Oracle SOA Suite to help you design, create, and manage applications that process healthcare data.For X12 HIPAA use cases, you can use the full Oracle B2B installation described in Section 1.7. However, if you are a healthcare provider using HL7 documents, you need to install the Oracle SOA Suite for Healthcare Integration software. This software consists of the Healthcare Integration, JDeveloper adapter, and the Healthcare Integration User Interface, which provides a customized, web-based console for designing, monitoring, and managing HL7 documents.The Oracle B2B user interface is the default when you finish installing Oracle SOA Suite for Healthcare Integration into your Oracle home. If you want to use the Oracle SOA Suite for Healthcare Integration user interface, you must complete both of the following tasks post-installation and during configuration:

  1. Use the RCU to set a custom variable before running the domain configuration wizard.

  2. Select an Oracle SOA Suite for Healthcare Integration-specific template during domain configuration.

The Oracle SOA Suite for Healthcare Integration user interface will not function properly if you do not do both tasks. These configurations are detailed further in Section 1.9.2.

1.9 About the Custom Variables Required for the Oracle B2B and Healthcare Schemas

After you install the Oracle B2B and Healthcare software, you must create database schemas in order to configure your Oracle WebLogic domain. When you install the Oracle B2B or Healthcare schemas, you are prompted to set two custom variables, which affect the way in which these schemas are created in the database. As a result, you should review the following information before you install the schemas. Both of these topics are relevant for Task 6, "Specifying Custom Variables" in Chapter 3.

1.9.1 About the Database Profile Custom Variable

The Database Profiles custom variable on the Repository Creation Utility (RCU) Custom Variables screen allows you to identify the predicted size or "profile" of the database on which you are installing the SOA Infrastructure schema. To estimate the size of the database required for your Oracle SOA Suite configuration, consider the information in "Developing a Database Growth Management Strategy" in Administering Oracle SOA Suite and Oracle Business Process Management Suite.

If you enter SMALL or MEDIUM as the database profile, RCU performs no special actions when the schema is created. The SMALL and MEDIUM options should be entered for informational purposes only.

If you enter LARGE as the database profile, RCU creates the SOA Infrastructure schema using an Oracle database feature called Interval Partitioning. Interval partitioning improves the efficiency of the database when large numbers of composite applications must be processed. When you enter the LARGE database profile, RCU creates the interval partitioned tables in a manner supported by the Oracle SOA Suite purging scripts and guidelines.

For more information about database partitioning, see the following sections of Oracle Database VLDB and Partitioning Guide:

1.9.2 About the Healthcare Integration Custom Variable

If you are not planning to use the Healthcare Integration User Interface, then enter NO as the value for the Healthcare Integration Custom variable. If you are planning to use the Healthcare Integration User Interface, select YES; otherwise, the Healthcare Integration User Interface will not function properly after it is installed and configured. For more information, see "Using the Oracle SOA Suite for Healthcare Integration User Interface" in Healthcare Integration User's Guide for Oracle SOA Suite.

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 have 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/common/sql/soainfra/sql/oracle/b2b_mv.sql