installing and configuring oracle b2b and soa suite for … · 2020. 4. 3. · oracle® fusion...

Oracle® Fusion MiddlewareInstalling and Configuring Oracle B2B andSOA Suite for Healthcare Integration

12c (12.2.1.4.0)E95091-02August 2020

Oracle Fusion Middleware Installing and Configuring Oracle B2B and SOA Suite for Healthcare Integration,12c (12.2.1.4.0)

E95091-02

Copyright © 2014, 2020, Oracle and/or its affiliates.

Primary Author: Oracle Corporation

This software and related documentation are provided under a license agreement containing restrictions onuse and disclosure and are protected by intellectual property laws. Except as expressly permitted in yourlicense agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverseengineering, disassembly, or decompilation of this software, unless required by law for interoperability, isprohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. Ifyou find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it onbehalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software,any programs embedded, installed or activated on delivered hardware, and modifications of such programs)and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Governmentend users are "commercial computer software" or “commercial computer software documentation” pursuantto the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such,the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works,and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programsembedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oraclecomputer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in thelicense contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloudservices are defined by the applicable contract for such services. No other rights are granted to the U.S.Government.

This software or hardware is developed for general use in a variety of information management applications.It is not developed or intended for use in any inherently dangerous applications, including applications thatmay create a risk of personal injury. If you use this software or hardware in dangerous applications, then youshall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure itssafe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of thissoftware or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks oftheir respective owners.

Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks areused under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc,and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registeredtrademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products,and services from third parties. Oracle Corporation and its affiliates are not responsible for and expresslydisclaim all warranties of any kind with respect to third-party content, products, and services unless otherwiseset forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will notbe responsible for any loss, costs, or damages incurred due to your access to or use of third-party content,products, or services, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

Audience viii

Documentation Accessibility viii

Related Documents viii

Conventions ix

1 About the Oracle B2B and SOA Suite for Healthcare IntegrationInstallation

About Oracle B2B and SOA Suite for Healthcare Integration 1-1

About the Configuration Options for Oracle B2B and SOA Suite for HealthcareIntegration 1-2

Using the Standard Installation Topology as a Starting Point 1-3

About the Oracle B2B Standard Installation Topology 1-4

About the Oracle SOA Suite for Healthcare Integration Standard InstallationTopology 1-5

About Elements in the Standard Installation Topology Illustration 1-6

About Secondary Topologies 1-7

Using This Document to Extend an Existing Domain 1-8

2 Preparing to Install and Configure Oracle B2B and SOA Suite forHealthcare Integration

Roadmap for Installing and Configuring a Standard Installation Topology 2-1

Roadmap for Verifying Your System Environment 2-2

Verifying Certification, System, and Interoperability Requirements 2-4

Selecting an Installation User 2-4

About User Permissions 2-5

Understanding Non-Default User Permissions on UNIX Operating Systems 2-7

Verifying that the Installation User has Administrator Privileges on WindowsOperating Systems 2-7

Understanding Directories for Installation and Configuration 2-7

About the Recommended Directory Structure 2-8

About the Oracle Home Directory 2-9

iii

About the Domain Home Directory 2-10

About the Application Home Directory 2-10

Installing Multiple Products in the Same Domain 2-10

Preparing for Shared Storage 2-11

About JDK Requirements for an Oracle Fusion Middleware Installation 2-12

About Database Requirements for an Oracle Fusion Middleware Installation 2-12

About the Custom Variables Required for the SOA Suite Schemas 2-13

About Product Distributions 2-14

Obtaining the Product Distribution 2-14

3 Installing the Oracle B2B and SOA Suite for Healthcare IntegrationSoftware

Verifying the Installation Checklist 3-1

Starting the Installation Program 3-3

Navigating the Installation Screens 3-3

Verifying the Installation 3-4

Reviewing the Installation Log Files 3-5

Checking the Directory Structure 3-5

Viewing the Contents of the Oracle Home 3-5

4 Configuring Oracle B2B Domain

Creating the Database Schemas 4-1

Installing and Configuring a Certified Database 4-2

Starting the Repository Creation Utility 4-2

Navigating the Repository Creation Utility Screens to Create Schemas 4-2

Introducing the RCU 4-3

Selecting a Method of Schema Creation 4-3

Providing Database Connection Details 4-3

Specifying a Custom Prefix and Selecting Schemas for Oracle B2B andHealthcare 4-4

Specifying Schema Passwords 4-5

Specifying Custom Variables 4-5

Completing Schema Creation 4-5

Configuring the Domain 4-5

Starting the Configuration Wizard 4-5

Navigating the Configuration Wizard Screens to Create and Configure theDomain 4-6

Selecting the Domain Type and Domain Home Location 4-8

Selecting the Configuration Templates for Oracle B2B 4-8

Configuring High Availability Options 4-9

iv

Selecting the Application Home Location 4-10

Configuring the Administrator Account 4-11

Specifying the Domain Mode and JDK 4-11

Specifying the Database Configuration Type 4-11

Specifying JDBC Component Schema Information 4-12

Testing the JDBC Connections 4-12

Selecting Advanced Configuration 4-13

Configuring the Administration Server Listen Address 4-13

Configuring Node Manager 4-13

Configuring Managed Servers for Oracle B2B 4-14

Configuring a Cluster for Oracle B2B 4-15

Defining Server Templates 4-15

Configuring Dynamic Servers 4-15

Assigning Oracle B2B Managed Servers to the Cluster 4-16

Configuring Coherence Clusters 4-16

Creating a New Oracle B2B Machine 4-17

Assigning Servers to Oracle B2B Machines 4-17

Virtual Targets 4-18

Partitions 4-18

Reviewing Your Configuration Specifications and Configuring the Domain 4-18

Writing Down Your Domain Home and Administration Server URL 4-18

Starting the Servers 4-19

Starting Node Manager 4-19

Starting the Administration Server 4-19

Starting the Managed Servers 4-20

Verifying the Configuration 4-21

Configuring Healthcare in a Weblogic Domain 4-21

5 Configuring the Oracle SOA Suite for Healthcare IntegrationDomain

Creating the Database Schemas 5-1

Installing and Configuring a Certified Database 5-2

Starting the Repository Creation Utility 5-2

Navigating the Repository Creation Utility Screens to Create Schemas 5-2

Introducing the RCU 5-3

Selecting a Method of Schema Creation 5-3

Providing Database Connection Details 5-3

Specifying a Custom Prefix and Selecting Schemas for Oracle B2B andHealthcare 5-4

Specifying Schema Passwords 5-5

v

Specifying Custom Variables 5-5

Completing Schema Creation 5-5

Configuring the Domain 5-5

Starting the Configuration Wizard 5-5

Navigating the Configuration Wizard Screens to Create and Configure theDomain 5-6

Selecting the Domain Type and Domain Home Location 5-7

Selecting the Configuration Templates for Oracle SOA Suite for HealthcareIntegration 5-8

Selecting the Application Home Location 5-8

Configuring the Administrator Account 5-9

Specifying the Domain Mode and JDK 5-9

Specifying the Database Configuration Type 5-9

Specifying JDBC Component Schema Information 5-10

Testing the JDBC Connections 5-10

Selecting Advanced Configuration 5-11

Configuring the Administration Server Listen Address 5-11

Configuring Node Manager 5-11

Configuring Managed Servers for Oracle Healthcare 5-12

Configuring a Cluster for Oracle Healthcare 5-13

Defining Server Templates 5-13

Configuring Dynamic Servers 5-13

Assigning Oracle Healthcare Managed Servers to the Cluster 5-14

Configuring Coherence Clusters 5-14

Creating a New Oracle Healthcare Machine 5-15

Assigning Servers to Oracle Healthcare Machines 5-15

Virtual Targets 5-16

Partitions 5-16

Reviewing Your Configuration Specifications and Configuring the Domain 5-16

Writing Down Your Domain Home and Administration Server URL 5-16

Starting the Servers 5-17

Starting Node Manager 5-17

Starting the Administration Server 5-17

Starting the Managed Servers 5-18

Verifying the Configuration 5-19

6 Next Steps After Configuring the Domain

Performing Basic Administrative Tasks 6-1

Performing Additional Domain Configuration Tasks 6-2

Preparing Your Environment for High Availability 6-2

vi

7 Uninstalling or Reinstalling Oracle B2B and SOA Suite forHealthcare Integration

About Product Uninstallation 7-1

Stopping Oracle Fusion Middleware 7-2

Removing Your Database Schemas 7-2

Uninstalling the Software 7-3

Starting the Uninstall Wizard 7-3

Selecting the Product to Uninstall 7-3

Navigating the Uninstall Wizard Screens 7-3

Removing the Oracle Home Directory Manually 7-4

Removing the Program Shortcuts on Windows Operating Systems 7-4

Removing the Domain and Application Data 7-5

Reinstalling the Software 7-5

A Secondary Topologies for Oracle B2B

Oracle SOA Suite, Oracle B2B, and Business Activity Monitoring Topology A-1

Oracle SOA Suite, Oracle B2B, and Oracle Service Bus Topology A-5

B Updating the JDK After Installing and Configuring an Oracle FusionMiddleware Product

About Updating the JDK Location After Installing an Oracle Fusion MiddlewareProduct B-1

Updating the JDK Location in an Existing Oracle Home B-2

Updating the JDK Location in an Existing Domain Home B-3

vii

Preface

This document describes how to install and configure Oracle B2B and SOA Suite forHealthcare Integration.

• Audience

• Documentation Accessibility

• Related Documents

• ConventionsLearn about the conventions used in this document.

AudienceThis guide is intended for system administrators or application developers who areinstalling and configuring Oracle B2B and SOA Suite for Healthcare Integration. Itis assumed that readers are familiar with web technologies and have a generalunderstanding of Windows and UNIX platforms.

Documentation AccessibilityFor information about Oracle's commitment to accessibility, visit theOracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic supportthrough My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trsif you are hearing impaired.

Related DocumentsRefer to the Oracle Fusion Middleware Library for additional information.

• For B2B information, see Oracle B2B Documentation.

• For Healthcare information, see Oracle SOA for Healthcare Documentation.

• For installation information, see Fusion Middleware Installation Documentation.

• For upgrade information, see Fusion Middleware Upgrade Documentation.

• For administration-related information, see Fusion Middleware AdministrationDocumentation.

• For release-related information, see Fusion Middleware Release Notes.

Preface

viii

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs

ConventionsLearn about the conventions used in this document.

This document uses the following text conventions:

Convention Meaning

boldface Boldface type indicates graphical user interface elements associatedwith an action, or terms defined in text or the glossary.

italic Italic type indicates book titles, emphasis, or placeholder variables forwhich you supply particular values.

monospace Monospace type indicates commands within a paragraph, URLs, codein examples, text that appears on the screen, or text that you enter.

Preface

ix

1About the Oracle B2B and SOA Suite forHealthcare Integration Installation

The standard installation for Oracle B2B and SOA Suite for Healthcare Integrationdescribed in this guide creates the standard topology, which represents a samplestarting topology for this product.

• About Oracle B2B and SOA Suite for Healthcare IntegrationOracle B2B and SOA Suite for Healthcare Integration are two separate SOA-compatible products that enable document and data exchange.

• About the Configuration Options for Oracle B2B and SOA Suite for HealthcareIntegrationIn a regular Oracle SOA Quick Start installation, users can only exchange CustomDocuments, which is a limited function of Oracle B2B. If this function fulfills yourbusiness needs, you do not need to install Oracle B2B.

• Using the Standard Installation Topology as a Starting PointThe standard installation topology is a flexible topology that you can use as astarting point in production environments.

• About Secondary TopologiesSecondary topologies include configurations with components that requireadditional installation or configuration steps on top of the standard topology.

• Using This Document to Extend an Existing DomainThe procedures in this guide describe how to create a new domain. Theassumption is that no other Oracle Fusion Middleware products are installed onyour system.

About Oracle B2B and SOA Suite for Healthcare IntegrationOracle B2B and SOA Suite for Healthcare Integration are two separate SOA-compatible products that enable document and data exchange.

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

Oracle B2B and SOA Suite for Healthcare Integration use several features ofOracle SOA Suite to help you design, create, and manage applications that processhealthcare data. This software consists of the Healthcare Integration, JDeveloperadapter, and the Oracle SOA Suite for Healthcare Integration user interface, whichprovides a customized, web-based console for designing, monitoring, and managingHL7 documents.

Oracle B2B and SOA Suite for Healthcare Integration use the same installer, butusers can choose to install and configure the products separately or in combination,depending on their needs. The configuration options for these products are explained

1-1

further in About the Configuration Options for Oracle B2B and SOA Suite forHealthcare Integration.

Note:

You must install B2B from the B2B installation in order for any B2Bfunctionality to operate. After a SOA installation, the B2B UI will be active butyou must still install B2B separately if you want to use any B2B functionality(composite, B2B UI, or B2B runtime engine).

About the Configuration Options for Oracle B2B and SOASuite for Healthcare Integration

In a regular Oracle SOA Quick Start installation, users can only exchange CustomDocuments, which is a limited function of Oracle B2B. If this function fulfills yourbusiness needs, you do not need to install Oracle B2B.

See Activating a Limited Oracle B2B Interface without a Full Installation in InstallingOracle SOA Suite and Business Process Management Suite Quick Start forDevelopers.

For more functionality to exchange business documents between enterprise andbusiness partners not involved in healthcare, you should install the full Oracle B2B.

Note:

You must install B2B from the B2B installation in order for any B2Bfunctionality to operate. After a SOA installation, the B2B UI will be active butyou must still install B2B separately if you want to use any B2B functionality(composite, B2B UI, or B2B runtime engine).

Businesses in healthcare can take advantage of Oracle SOA Suite for HealthcareIntegration software to exchange sensitive medical data. Healthcare users have twoconfiguration options:

• X12 HIPAA users should install the full Oracle B2B installation configured withHealthcare Integration.

• Healthcare providers using HL7 documents should install the full Oracle SOASuite for Healthcare Integration software.

This install guide explains how to configure Oracle B2B and Healthcare in the followingways:

• Oracle B2B in a WebLogic Domain

This option is for non-healthcare businesses. You select the B2B Install type andthen select the B2B template while configuring to create a standard WebLogicdomain.

• Healthcare in a WebLogic Domain

Chapter 1About the Configuration Options for Oracle B2B and SOA Suite for Healthcare Integration

1-2

This option is for healthcare business using HL7 documents. You select theHealthcare Install type and then select the Healthcare template while configuringto create a standard WebLogic domain for Healthcare.

Note:

Healthcare in a WebLogic Domain option is deprecated in FusionMiddleware 12.2.1.4.0 and will be removed in the next release.Specifically, the Oracle Healthcare console is deprecated in FusionMiddleware 12.2.1.4.0 and will be removed in the next release.

• HIPAA Compliant Healthcare

This option is for X12 HIPAA users. You select the B2B Install type duringinstallation. During configuraiton, you select both Healthcare and B2B templateswhile configuring. After configuring the domain, you can still use the B2Buser interface to exchange HIPAA (healthcare) documents. You can use thisconfiguration option if you want to configure just B2B, but still take advantageof Healthcare without configuring the Healthcare libraries.

About the Oracle SOA Suite for Healthcare Integration Interface

The Oracle B2B user interface is the default when you finish installing Oracle SOASuite for Healthcare Integration into your Oracle home. If you want to use the OracleSOA Suite for Healthcare Integration user interface, you must complete both of thefollowing tasks post-installation and during configuration:

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

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

The Oracle SOA Suite for Healthcare Integration user interface will not functionproperly if you do not do both tasks. These configurations are detailed further in Aboutthe Healthcare Integration Custom Variable.

Using the Standard Installation Topology as a Starting PointThe standard installation topology is a flexible topology that you can use as a startingpoint in production environments.

The information in this guide helps you to create a standard installation topology forOracle B2B and SOA Suite for Healthcare Integration. If required, you can later extendthe standard installation topology to create a secure and highly available productionenvironment, see Next Steps After Configuring the Domain.

The standard installation topology represents a sample topology for this product. It isnot the only topology that this product supports. See About the Standard InstallationTopology in Planning an Installation of Oracle Fusion Middleware.

• About the Oracle B2B Standard Installation TopologyThis topology represents a standard WebLogic Server domain that contains anAdministration Server and one or more clusters containing one or more ManagedServers.

Chapter 1Using the Standard Installation Topology as a Starting Point

1-3

• About the Oracle SOA Suite for Healthcare Integration Standard InstallationTopologyThis topology represents a standard WebLogic Server domain that contains anAdministration Server and a cluster containing one Managed Server.

• About Elements in the Standard Installation Topology IllustrationThe standard installation topology typically includes common elements.

About the Oracle B2B Standard Installation TopologyThis topology represents a standard WebLogic Server domain that contains anAdministration Server and one or more clusters containing one or more ManagedServers.

The following figure shows the standard installation topology for Oracle B2B.

Note:

All Managed Servers of a component type in the domain must belong to thatcluster. For example, Oracle B2B domains support only a single Oracle B2Bcluster inside each domain.

See Table 1-1 for information on elements of this topology.


1-4

Figure 1-1 Standard Topology for Oracle B2B

For configuration instructions, see Configuring Oracle B2B Domain.

About the Oracle SOA Suite for Healthcare Integration StandardInstallation Topology

This topology represents a standard WebLogic Server domain that contains anAdministration Server and a cluster containing one Managed Server.

The following figure shows the standard installation topology for Oracle SOA Suite forHealthcare Integration.

Note:

All Managed Servers of a component type in the domain must belong to thatcluster. For example, Oracle SOA Suite for Healthcare Integration domainssupport only a single Healthcare cluster inside each domain.


1-5

Figure 1-2 Standard Installation Topology for Oracle SOA Suite for HealthcareIntegration

For configuration instructions, see Configuring the Oracle SOA Suite for HealthcareIntegration Domain.

About Elements in the Standard Installation Topology IllustrationThe standard installation topology typically includes common elements.

The following table describes all elements of the topology illustration:

Table 1-1 Description of Elements in Standard Installation Topologies

Element Description and Links to Related Documentation

APPHOST A standard term used in Oracle documentation to referto the machine that hosts the application tier.

DBHOST A standard term used in Oracle documentation to referto the machine that hosts the database.


1-6

Table 1-1 (Cont.) Description of Elements in Standard Installation Topologies

Element Description and Links to Related Documentation

WebLogic Domain A logically related group of Java components (in thiscase, the Administration Server, Managed Servers, andother related software components).See What Is an Oracle WebLogic Server Domain? inUnderstanding Oracle Fusion Middleware.

Administration Server Central control entity of a WebLogic domain. It maintainsconfiguration objects for that domain and distributesconfiguration changes to Managed Servers.See What Is the Administration Server? inUnderstanding Oracle Fusion Middleware.

Enterprise Manager The Oracle Enterprise Manager Fusion MiddlewareControl is a primary tool used to manage a domain.See Oracle Enterprise Manager Fusion MiddlewareControl in Understanding Oracle Fusion Middleware.

Cluster A collection of multiple WebLogic Server instancesrunning simultaneously and working together.See Overview of Managed Servers and ManagedServer Clusters in Understanding Oracle FusionMiddleware.

Machine A logical representation of the computer that hosts oneor more WebLogic Server instances (servers). Machinesare also the logical glue between the Managed Serversand the Node Manager. In order to start or stop theManaged Servers using the Node Manager, associatethe Managed Servers with a machine.

Managed Server A host for your applications, application components,web services, and their associated resources.See Overview of Managed Servers and ManagedServer Clusters in Understanding Oracle FusionMiddleware.

Infrastructure A collection of services that include the following:• Metadata repository (MDS) contains the metadata

for Oracle Fusion Middleware components, such asthe Oracle Application Developer Framework. SeeWhat Is the Metadata Repository? in UnderstandingOracle Fusion Middleware.

• Oracle Application Developer Framework (OracleADF).

• Oracle Web Services Manager (OWSM).

About Secondary TopologiesSecondary topologies include configurations with components that require additionalinstallation or configuration steps on top of the standard topology.

The main sections of this guide describe how to install and configure a standardinstallation topology. The secondary topologies contain several products that are notidentified or included in the standard installation topologies.

For guidelines to install and configure secondary topologies, see SecondaryTopologies for Oracle B2B.

Chapter 1About Secondary Topologies

1-7

Using This Document to Extend an Existing DomainThe procedures in this guide describe how to create a new domain. The assumption isthat no other Oracle Fusion Middleware products are installed on your system.

If you have installed and configured other Oracle Fusion Middleware products on yoursystem (for example, Fusion Middleware Infrastructure, with a domain that is up andrunning) and wish to extend the same domain to include Oracle B2B and SOA Suitefor Healthcare Integration, see Installing Multiple Products in the Same Domain.

Chapter 1Using This Document to Extend an Existing Domain

1-8

2Preparing to Install and Configure OracleB2B and SOA Suite for HealthcareIntegration

To prepare for your Oracle B2B and SOA Suite for Healthcare Integration installation,verify that your system meets the basic requirements, then obtain the correctinstallation software.

• Roadmap for Installing and Configuring a Standard Installation TopologyThis roadmap provides the steps required to install and configure a standardOracle B2B and SOA Suite for Healthcare Integration installation topology.

• Roadmap for Verifying Your System EnvironmentBefore you begin the installation and configuration process, you must verify yoursystem environment.

• About Product DistributionsYou create the initial Oracle B2B and SOA Suite for Healthcare Integration domainusing the Oracle Fusion Middleware Infrastructure distribution, which contains bothOracle WebLogic Server software and Oracle Java Required Files (JRF) software.

• Obtaining the Product DistributionYou can obtain the Oracle Fusion Middleware Infrastructure and Oracle B2Band SOA Suite for Healthcare Integration distribution on the Oracle TechnologyNetwork (OTN).

Roadmap for Installing and Configuring a StandardInstallation Topology

This roadmap provides the steps required to install and configure a standard OracleB2B and SOA Suite for Healthcare Integration installation topology.

Table 2-1 provides the high-level steps required for installing a standard installationtopology.

Table 2-1 Standard Installation Roadmap

Task Description Documentation

Verify your systemenvironment.

Before you begin the installation,verify that the minimum systemand network requirements are met.

See Roadmap for Verifying Your System Environment.

Check for anymandatory patchesthat are requiredbefore theinstallation.

Review the Oracle FusionMiddleware Infrastructure releasenotes to see if there are anymandatory patches required forthe software products that you areinstalling.

See Install and Configure in Release Notes for OracleFusion Middleware Infrastructure.

2-1

Table 2-1 (Cont.) Standard Installation Roadmap


Obtain theappropriatedistributions.

Both B2B and Healthcare requirean existing Oracle FusionMiddleware Infrastructureinstallation and Oracle SOA Suite;B2B and Healthcare must beinstalled in the same Oracle homeas Oracle Fusion MiddlewareInfrastructure and Oracle SOASuite. You have a separatedistribution for B2B andHealthcare, calledfmw_12.2.1.4.0_b2bhealthcare.jar.

See About Product Distributions.

Determine yourinstallationdirectories.

Verify that the installer can accessor create the required installerdirectories. Also, verify that thedirectories exist on systems thatmeet the minimum requirements.

See What Are the Key Oracle Fusion MiddlewareDirectories? in Understanding Oracle FusionMiddleware.

Install prerequisitesoftware.

Install Oracle Fusion MiddlewareInfrastructure to create the Oraclehome directory. Then install OracleSOA Suite into the same Oraclehome.

See Installing the Infrastructure Softwarein Installingand Configuring the Oracle Fusion MiddlewareInfrastructure.

Install the software. Run the Oracle Universal Installerto install Oracle B2B and SOASuite for Healthcare Integration.

Installing the software transfersthe software to your system andcreates the Oracle home directory.

See Installing the Oracle B2B and SOA Suite forHealthcare Integration Software.

Select a databaseprofile and reviewany required customvariables.

Before you install the requiredschemas in the database, reviewthe information about any customvariables you need to set for theOracle B2B and SOA Suite forHealthcare Integration schemas.

See About Database Requirements for an OracleFusion Middleware Installation.

Create theschemas.

Run the Repository Creation Utilityto create the schemas required forconfiguration.

See Creating the Database Schemas.

Create a WebLogicdomain.

Use the Configuration Wizard/Assistant to create and configurethe WebLogic domain.

See Configuring the Domain for creating the standardtopology for Oracle B2B and Healthcare.

Administer andprepare yourdomain for highavailability.

Discover additional tools andresources to administer yourdomain and configure your domainto be highly available.

See Next Steps After Configuring the Domain.

Roadmap for Verifying Your System EnvironmentBefore you begin the installation and configuration process, you must verify yoursystem environment.

Chapter 2Roadmap for Verifying Your System Environment

2-2

Table 2-2 identifies important tasks and checks to perform to ensure that yourenvironment is prepared to install and configure Oracle B2B and SOA Suite forHealthcare Integration.

Table 2-2 Roadmap for Verifying Your System Environment


Verify certification and systemrequirements.

Verify that your operating systemis certified and configured forinstallation and configuration.

See Verifying Certification, System,and Interoperability Requirements.

Identify a proper installation user. Verify that the installation user hasthe required permissions to installand configure the software.

See Selecting an Installation User.

Select the installation andconfiguration directories on yoursystem.

Verify that you can create thenecessary directories to install andconfigure the software, accordingto the recommended directorystructure.

See Understanding Directories forInstallation and Configuration.

Install a certified JDK. The installation program for thedistribution requires a certified JDKpresent on your system.

See About JDK Requirementsfor an Oracle Fusion MiddlewareInstallation.

Install and configure a database formid-tier schemas.

To configure your WebLogic domain,you must have access to a certifieddatabase that is configured forthe schemas required by OracleB2B and SOA Suite for HealthcareIntegration.

See About Database Requirementsfor an Oracle Fusion MiddlewareInstallation.

• Verifying Certification, System, and Interoperability RequirementsOracle recommends that you use the certification matrix and system requirementsdocuments with each other to verify that your environment meets the requirementsfor installation.

• Selecting an Installation UserThe user who installs and configures your system must have the requiredpermissions and privileges.

• Understanding Directories for Installation and ConfigurationDuring the installation and domain configuration process, you must plan onproviding the locations for these directories: Oracle home, Domain home, and theApplication home.

• About JDK Requirements for an Oracle Fusion Middleware InstallationMost Fusion Middleware products are in .jar file format. These distributions donot include a JDK. To run a .jar distribution installer, you must have a certifiedJDK installed on your system.

• About Database Requirements for an Oracle Fusion Middleware InstallationMany Oracle Fusion Middleware products require database schemas prior toconfiguration. If you do not already have a database where you can install theseschemas, you must install and configure a certified database.


2-3

Verifying Certification, System, and Interoperability RequirementsOracle recommends that you use the certification matrix and system requirementsdocuments with each other to verify that your environment meets the requirements forinstallation.

1. Verifying that your environment meets certification requirements:

Make sure that you install your product on a supported hardware and softwareconfiguration. See the certification document for your release on the Oracle FusionMiddleware Supported System Configurations page.

Oracle has tested and verified the performance of your product on all certifiedsystems and environments. Whenever new certifications are released, theyare added to the certification document right away. New certifications can bereleased at any time. Therefore, the certification documents are kept outside thedocumentation libraries and are available on Oracle Technology Network.

2. Using the system requirements document to verify certification:

Oracle recommends that you use the Oracle Fusion Middleware SystemRequirements and Specifications document to verify that the certificationrequirements are met. For example, if the certification document indicates thatyour product is certified for installation on 64-Bit Oracle Linux 6.5, use thisdocument to verify that your system meets the required minimum specifications.These include disk space, available memory, specific platform packages andpatches, and other operating system-specific requirements. System requirementscan change in the future. Therefore, the system requirement documents are keptoutside of the documentation libraries and are available on Oracle TechnologyNetwork.

3. Verifying interoperability among multiple products:

To learn how to install and run multiple Fusion Middleware products from thesame release or mixed releases with each other, see Oracle Fusion Middleware12c Interoperability and Compatibility in Understanding Interoperability andCompatibility.

Selecting an Installation UserThe user who installs and configures your system must have the required permissionsand privileges.

• About User PermissionsThe user who installs a Fusion Middleware product owns the files and has certainpermissions on the files.

• Understanding Non-Default User Permissions on UNIX Operating SystemsChanging the default permissions setting reduces the security of the installationand possibly your system. Oracle does not recommend changing defaultpermission settings.

• Verifying that the Installation User has Administrator Privileges on WindowsOperating SystemsTo update the Windows Registry, you must have administrator privileges.


2-4

About User PermissionsThe user who installs a Fusion Middleware product owns the files and has certainpermissions on the files.

• Read and write permissions on all non-executable files (forexample, .jar, .properties, or .xml). All other users in the same group as the fileowner have read permissions only.

• Read, write, and execute permissions on all executable files (forexample, .exe, .sh, or .cmd). All other users in the same group as the file ownerhave read and execute permissions only.

This means that someone other than the person who installs the software can use theinstalled binaries in the Oracle home directory to configure a domain or set of FusionMiddleware products.

During configuration, the files generated by the configuration process are owned bythe user who ran the Configuration Wizard. This user has the same permissionsas described above for the installation user. However, security-sensitive files are notcreated with group permissions. Only the user that created the domain has read andwrite permissions and can administer the domain.

Consider the following examples:

• Example 1: A Single User Installs the Software and Configures the Domain

This example explains the file permissions where the same user installs thesoftware and configures the domain.

To ensure proper permissions and privileges for all files, Oracle recommends thatthe same owner perform both tasks: install the Oracle Fusion Middleware productand configure the WebLogic Server domain by using the Configuration Wizard.

Figure 2-1 Directory Structure when a Single User Installs the Software andConfigures the Domain

The Oracle home is created by User1 during product

installation. User1 has read/write/execute permissions

on all executable files, and read/write permissions on all

other files. All other users in User1’s group have

read/execute permissions on all executable files, and

read permissions on all other files.

product

Oracle Home

(Oracle_Home)

Application Home (applications)

oracle

home

Domain Home(domains)

configThe Domain home and Application home are created by

User1 during product installation. User1 has

read/write/execute permissions on all executable files,

and read/write permissions on all other files. All other

users in User1’s group have read/execute permissions

on all executable files, and read permissions on all

other files.


2-5

If the user who creates the domain is different than the user who installed thesoftware, then both users must have the same privileges, as shown in the nextexample.

• Example 2: The Oracle Home Directory and Domain are Created by DifferentUsers

This example explains the file permissions where one user creates the Oraclehome and another user configures the domain.

Figure 2-2 Directory Structure when Different Users Install the Softwareand Configure the Domain

The Oracle home is created by User1 during product

installation. User1 has read/write/execute permissions on

all executable files, and read/write permissions on all

other files. All other users in User1’s group have

read/execute permissions on all executable files, and read

permissions on all other files.

product

Oracle Home

(Oracle_Home)

Application Home (applications)

oracle

home

Domain Home(domains)

configThe Domain home and Application home are created by

User2 during product installation. User2 has

read/write/execute permissions on all executable files,

and read/write permissions on all other files. All other

users in User2’s group (including User1) have

read/execute permissions on all executable files, and read

permissions on all other files.

Note:

Certain domain files do not have group permissions. For example,cwallet.sso.

Consider the following points before you run the installer:

• On UNIX operating systems, Oracle recommends that you set umask to 027 onyour system before you install the software. This ensures that the file permissionsare set properly during installation. Use the following command:

umask 027

You must enter this command in the same terminal window from which you plan torun the product installer.

• On UNIX operating systems, do not run the installation program as a root user. Ifyou run the installer as a root user, the startup validation may fail and you cannotcontinue the installation.

• When you manage a product installation (for example, applying patches or startingmanaged Servers), use the same user ID that you used to install the product.


2-6

• On Windows operating systems, you must have administrative privileges to installthe product. See Verifying the Installation User has Administrator Privileges onWindows Operating Systems.

Understanding Non-Default User Permissions on UNIX Operating SystemsChanging the default permissions setting reduces the security of the installationand possibly your system. Oracle does not recommend changing default permissionsettings.

If other users require access to particular files or executable, consider using the UNIXsudo command (or other similar command) in lieu of changing file permissions.

Refer to your UNIX operating system Administrator's Guide or contact your operatingsystem vendor if you need further assistance.

Verifying that the Installation User has Administrator Privileges on WindowsOperating Systems

To update the Windows Registry, you must have administrator privileges.

By default, users with the administrator privilege sign in to the system with regularprivileges, but can request elevated permissions to perform administrative tasks.

To perform a task with elevated privileges:

1. Find the Command Prompt icon, either from the Start menu or the Windows iconin the lower-left corner.

2. Right-click Command Prompt and select Run as administrator.

This opens a new command prompt window, and all actions performed in thiswindow are done with administrator privileges.

Note:

If you have User Access Control enabled on your system, you may seean additional window asking you to confirm this action. Confirm andcontinue with this procedure.

3. Perform the desired task.

For example, to start the product installer:

For a jar file, enter:

java —jar distribution_name.jar

For an executable (.exe, .bin, or .sh file), enter:

distribution_name.exe

Understanding Directories for Installation and ConfigurationDuring the installation and domain configuration process, you must plan on providingthe locations for these directories: Oracle home, Domain home, and the Applicationhome.


2-7

• About the Recommended Directory StructureOracle recommends specific locations for the Oracle Home, Domain Home, andApplication Home.

• About the Oracle Home DirectoryWhen you install any Oracle Fusion Middleware product, you must use an Oraclehome directory.

• About the Domain Home DirectoryThe Domain home is the directory where domains that you configure are created.

• About the Application Home DirectoryThe Application home is the directory where applications for domains youconfigure are created.

• Installing Multiple Products in the Same DomainThere are two methods to install and configure multiple products in one domain.This is also known as extending a domain.

• Preparing for Shared StorageOracle Fusion Middleware allows you to configure multiple WebLogic Serverdomains from a single Oracle home. This allows you to install the Oracle homein a single location on a shared volume and reuse the Oracle home for multiplehost installations.

About the Recommended Directory StructureOracle recommends specific locations for the Oracle Home, Domain Home, andApplication Home.

Oracle recommends a directory structure similar to the one shown in Figure 2-3.

Figure 2-3 Recommended Oracle Fusion Middleware Directory Structure

This area contains binary

files laid down by the

product installer. Runtime

processes will not write to

this area.

product

Oracle Home

(Oracle_Home)

Application Home

(applications)

oracle

home

Domain Home

(Domains)

configThis area contains

configuration and

application data created

by user.

A base location (Oracle base) should be established on your system (for example, /home/oracle). From this base location, create two separate branches, namely, theproduct directory and the config directory. The product directory should contain the


2-8

product binary files and all the Oracle home directories. The config directory shouldcontain your domain and application data.

Oracle recommends that you do not keep your configuration datain the Oracle homedirectory; if you upgrade your product to another major release, are required to createa new Oracle home for binaries. You must also make sure that your configuration dataexists in a location where the binaries in the Oracle home have access.

The /home/oracle/product (for the Oracle home) and /home/oracle/config (for theapplication and configuration data) directories are used in the examples throughout thedocumentation; be sure to replace these directories with the actual directories on yoursystem.

About the Oracle Home DirectoryWhen you install any Oracle Fusion Middleware product, you must use an Oraclehome directory.

This directory is a repository for common files that are used by multiple FusionMiddleware products installed on the same machine. These files ensure that FusionMiddleware operates correctly on your system. They facilitate checking of cross-product dependencies during installation. For this reason, you can consider the Oraclehome directory a central support directory for all Oracle Fusion Middleware productsinstalled on your system.

Fusion Middleware documentation refers to the Oracle home directory asORACLE_HOME.

Oracle Home Considerations

Keep the following in mind when you create the Oracle home directory and installFusion Middleware products:

• Do not include spaces in the name of your Oracle home directory; the installerdisplays an error message if your Oracle home directory path contains spaces.

• You can install only one instance of each Oracle Fusion Middleware product ina single Oracle home directory. If you need to maintain separate versions of aproduct on the same machine, each version must be in its own Oracle homedirectory.

Although you can have several different products in a single Oracle home, onlyone version of each product can be in the Oracle home.

Multiple Home Directories

Although in most situations, a single Oracle home directory is sufficient, it is possibleto create more than one Oracle home directory. For example, you need to maintainmultiple Oracle home directories in the following situations:

• You prefer to maintain separate development and production environments, witha separate product stack for each. With two directories, you can update yourdevelopment environment without modifying the production environment until youare ready to do so.

• You want to maintain two different versions of a Fusion Middleware product atthe same time. For example, you want to install a new version of a product whilekeeping your existing version intact. In this case, you must install each productversion in its own Oracle home directory.


2-9

• You need to install multiple products that are not compatible with each other. SeeOracle Fusion Middleware 12c (12.2.1.4.0) Interoperability and Compatibility inUnderstanding Interoperability and Compatibility .

Note:

If you create more than one Oracle home directory, you must provide non-overlapping port ranges during the configuration phase for each product.

About the Domain Home DirectoryThe Domain home is the directory where domains that you configure are created.

The default Domain home location is ORACLE_HOME/user_projects/domains/domain_name. However, Oracle strongly recommends that you do not use this defaultlocation. Put your Domain home outside of the Oracle home directory, for example,in /home/oracle/config/domains. The config directory should contain domainand application data. Oracle recommends a separate domain directory so that newinstalls, patches, and other operations update the ORACLE_HOME only, not thedomain configuration.

See About the Recommended Directory Structure for more on the recommendeddirectory structure and locating your Domain home.

Fusion Middleware documentation refers to the Domain home directory asDOMAIN_HOME and includes all folders up to and including the domain name. Forexample, if you name your domain exampledomain and locate your domain datain the /home/oracle/config/domains directory, the documentation would useDOMAIN_HOME to refer to /home/oracle/config/domains/exampledomain.

About the Application Home DirectoryThe Application home is the directory where applications for domains you configureare created.

The default Application home location is ORACLE_HOME/user_projects/applications/domain_name. However, Oracle strongly recommends that you locate your Applicationhome outside of the Oracle home directory; if you upgrade your product to anothermajor release, you must create a new Oracle home for binaries.

See About the Recommended Directory Structure for more on the recommendeddirectory structure and locating your Application home..

Fusion Middleware documentation refers to the Application home directory asAPPLICATION_HOME and includes all folders up to and including the domain name. Forexample, if you name your domain exampledomain and you locate your applicationdata in the /home/oracle/config/applications directory, the documentation usesAPPLICATION_HOME to refer to /home/oracle/config/applications/exampledomain.

Installing Multiple Products in the Same DomainThere are two methods to install and configure multiple products in one domain. Thisis also known as extending a domain.


2-10

• Method 1.

Install and configure Product A, including creating the schemas and starting allservers in the domain to verify a successful domain configuration.

This is the method used in all installation guides in the Fusion Middleware library.You can repeat this process for as many products as necessary. It allows you tovalidate one product at a time and add more products incrementally.

To install Product B in the same domain as Product A:

1. Stop all servers to prevent any updates to the domain while you add the newproduct.

See Starting and Stopping Oracle Fusion Middleware in Administering OracleFusion Middleware.

2. Follow the instructions in the installation guide for Product B, including creatingthe necessary schemas.

3. Run the Configuration Wizard to configure the domain.

During configuration, the Configuration Wizard automatically detects thecomponents that have been installed and offers you the option to extend theexisting Product A domain to include Product B.

• Method 2.

Install all of the required products, then create the schemas for all of the products.After you create the schemas, configure the domain by using the necessaryproduct templates, then start all the servers.

This method of creating a multi-product domain may be slightly faster than Method1; however, the installation guides in the Fusion Middleware library do not providespecific instructions for this method of domain creation.

See Also:

• To update WebLogic domains, see Updating WebLogic Domains inCreating WebLogic Domains Using the Configuration Wizard.

• For important information regarding the ability of Oracle FusionMiddleware products to function with previous versions of otherOracle Fusion Middleware, Oracle, or third-party products, see OracleFusion Middleware 12c (12.2.1.4.0) Interoperability and Compatibility inUnderstanding Interoperability and Compatibility.

Preparing for Shared StorageOracle Fusion Middleware allows you to configure multiple WebLogic Server domainsfrom a single Oracle home. This allows you to install the Oracle home in a singlelocation on a shared volume and reuse the Oracle home for multiple host installations.

If you plan to use shared storage in your environment, see Using Shared Storage inHigh Availability Guide for more information.

For configuration requirements specific to Managed File Transfer, see High AvailabilityProperties in Using Oracle Managed File Transfer.


2-11

About JDK Requirements for an Oracle Fusion Middleware InstallationMost Fusion Middleware products are in .jar file format. These distributions do notinclude a JDK. To run a .jar distribution installer, you must have a certified JDKinstalled on your system.

Make sure that the JDK is installed outside of the Oracle home. If you install the JDKunder the Oracle home, you may encounter problems when you try to perform tasks inthe future. Oracle Universal Installer validates that the Oracle home directory is empty;the install does not progress until you specify an empty directory. Oracle recommendsthat you locate your JDK installation in the /home/oracle/products/jdk directory.

Platform-specific distributions have a .bin (for UNIX operating systems) or .exe (forWindows operating systems) installer; in these cases, a platform-specific JDK is in thedistribution and you do not need to install a JDK separately. However, you may needto upgrade this JDK to a more recent version, depending on the JDK versions that arecertified.

Always verify the required JDK version by reviewing the certification informationon the Oracle Fusion Middleware Supported System Configurations page. For 12c(12.2.1.4.0), the certified JDK is 1.8.0_211 and later.

To download the required JDK, navigate to the following URL and download the JavaSE JDK:

http://www.oracle.com/technetwork/java/javase/downloads/index.html

About Database Requirements for an Oracle Fusion MiddlewareInstallation

Many Oracle Fusion Middleware products require database schemas prior toconfiguration. If you do not already have a database where you can install theseschemas, you must install and configure a certified database.

To find a certified database for your operating system, see the certification documentfor your release on the Oracle Fusion Middleware Supported System Configurationspage on the Oracle Technology Network (OTN).

To make sure that your database is properly configured for schema creation, seeRepository Creation Utility Requirements in the Oracle Fusion Middleware SystemRequirements and Specifications document.

After your database is properly configured, you use the Repository Creation Utility(RCU) to create product schemas in your database. This tool is available in the Oraclehome for your Oracle Fusion Middleware product. See About the Repository CreationUtility in Creating Schemas with the Repository Creation Utility.

• About the Custom Variables Required for the SOA Suite SchemasWhen you install the Oracle SOA Suite schemas, you are prompted to set twocustom variables, which affect the way in which these schemas are created in thedatabase.


2-12

http://www.oracle.com/technetwork/java/javase/downloads/index.html

About the Custom Variables Required for the SOA Suite SchemasWhen you install the Oracle SOA Suite schemas, you are prompted to set two customvariables, which affect the way in which these schemas are created in the database.

These variables are explained further in the following sections:

• About the Database Profile Custom VariableThe Database Profile custom variable on the Repository Creation Utility (RCU)Custom Variables screen allows you to identify the predicted size or profile of thedatabase on which you are installing the SOA Infrastructure schema.

• About the Healthcare Integration Custom VariableThe Healthcare Integration custom variable helps to activate the Oracle SOA Suitefor healthcare integration user interface. The interface is not supported for OracleSOA Suite for healthcare integration.

About the Database Profile Custom VariableThe Database Profile custom variable on the Repository Creation Utility (RCU) CustomVariables screen allows you to identify the predicted size or profile of the database onwhich 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 inAdministering Oracle SOA Suite and Oracle Business Process Management Suite.

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

If you enter LARGE as the database profile, the RCU creates the SOA Infrastructureschema using an Oracle database feature called Interval Partitioning. Intervalpartitioning improves the efficiency of the database when large numbers of compositeapplications must be processed. When you select the LARGE database profile, theRCU creates the interval partitioned tables in a manner supported by the Oracle SOASuite purging scripts and guidelines.

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

• Partitioning Concepts

• Interval Partitioning

About the Healthcare Integration Custom VariableThe Healthcare Integration custom variable helps to activate the Oracle SOA Suite forhealthcare integration user interface. The interface is not supported for Oracle SOASuite for healthcare integration.

If you are not planning to use the Oracle SOA Suite for healthcare integration userinterface, then set the value of the Healthcare Integration custom variable to NO. If youare planning to use the Oracle SOA Suite for healthcare integration user interface, setit to YES. Otherwise, the Oracle SOA Suite for healthcare integration user interfacewill not function properly after it is installed and configured.


2-13

When set to YES, the RCU creates additional materialized views in the database,which are required by the Oracle SOA Suite for healthcare integration user interface.When set to NO, you can perform these additional schema configuration tasks later byrunning the following SQL script on the database. This script is installed in the OracleFusion Middleware Oracle home when you select the Healthcare with B2B installationtype:

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

See Using the Oracle SOA Suite for Healthcare Integration User Interface inHealthcare Integration User's Guide for Oracle SOA Suite.

About Product DistributionsYou create the initial Oracle B2B and SOA Suite for Healthcare Integration domainusing the Oracle Fusion Middleware Infrastructure distribution, which contains bothOracle WebLogic Server software and Oracle Java Required Files (JRF) software.

Oracle JRF software consists of:

• Oracle Web Services Manager

• Oracle Application Development Framework (Oracle ADF)

• Oracle Enterprise Manager Fusion Middleware Control

• Repository Creation Utility (RCU)

• Other libraries and technologies required to support Oracle Fusion Middlewareproducts

Installing Oracle Fusion Middleware Infrastructure is a prerequisite to installing OracleB2B and SOA Suite for Healthcare Integration.

Obtaining the Product DistributionYou can obtain the Oracle Fusion Middleware Infrastructure and Oracle B2B and SOASuite for Healthcare Integration distribution on the Oracle Technology Network (OTN).

To prepare to install Oracle Fusion Middleware Infrastructure and Oracle B2B andSOA Suite for Healthcare Integration:

1. Enter java -version on the command line to verify that a certified JDK is installedon your system. For 12c (12.2.1.4.0), the certified JDK is 1.8.0_211 and later.

See About JDK Requirements for an Oracle Fusion Middleware Installation.

2. Locate and download the Oracle Fusion Middleware Infrastructure and Oracle B2Band SOA Suite for Healthcare Integration software.

See Obtaining Product Distributions in Planning an Installation of Oracle FusionMiddleware.

Chapter 2About Product Distributions

2-14

3Installing the Oracle B2B and SOA Suitefor Healthcare Integration Software

Follow the steps in this section to install the Oracle B2B and SOA Suite for HealthcareIntegration software.Before beginning the installation, ensure that you have verified the prerequisites andcompleted all steps covered in Preparing to Install and Configure Oracle B2B and SOASuite for Healthcare Integration.

• Verifying the Installation ChecklistThe installation process requires specific information.

• Starting the Installation ProgramBefore running the installation program, you must verify the JDK and prerequisitesoftware is installed.

• Navigating the Installation ScreensThe installer shows a series of screens where you verify or enter information.

• Verifying the InstallationAfter you complete the installation, verify whether it was successful by completinga series of tasks.

Verifying the Installation ChecklistThe installation process requires specific information.

Table 3-1 lists important items that you must know before, or decide during, OracleB2B and SOA Suite for Healthcare Integration installation.

Table 3-1 Installation Checklist

Information Example Value Description

JAVA_HOME /home/Oracle/Java/jdk1.8.0_211

Environment variable thatpoints to the Java JDK homedirectory.

Database host examplehost.exampledomain

Name and domain of thehost where the database isrunning.

Database port 1521 Port number that the databaselistens on. The default Oracledatabase listen port is 1521.

Database service name orcl.exampledomain Oracle databases require aunique service name. Thedefault service name is orcl.

3-1

Table 3-1 (Cont.) Installation Checklist


DBA username SYS Name of user with databaseadministration privileges. Thedefault DBA user on Oracledatabases is SYS.

DBA password myDBApw957 Password of the userwith database administrationprivileges.

ORACLE_HOME /home/Oracle/product/ORACLE_HOME

Directory in which you willinstall your software.

This directory will includeOracle Fusion MiddlewareInfrastructure and Oracle B2Band SOA Suite for HealthcareIntegration, as needed.

WebLogic Server hostname examplehost.exampledomain

Host name for OracleWebLogic Server and OracleB2B and SOA Suitefor Healthcare Integrationconsoles.

Console port 7001 Port for Oracle WebLogicServer and Oracle B2B andSOA Suite for HealthcareIntegration consoles.

DOMAIN_HOME /home/Oracle/config/domains/b2b_domain

Location in which your domaindata is stored.

APPLICATION_HOME /home/Oracle/config/applications/b2b_domain

Location in which yourapplication data is stored.

Administrator user name foryour WebLogic domain

weblogic Name of the user withOracle WebLogic Serveradministration privileges. Thedefault administrator user isweblogic.

Administrator user password myADMpw902 Password of the user withOracle WebLogic Serveradministration privileges.

FTP Port 7021 Port for embedded FTPserver.

RCU ORACLE_HOME/oracle_common/bin

Path to the RepositoryCreation Utility (RCU).

RCU schema prefix B2B Prefix for names of databaseschemas used by Oracle B2Band SOA Suite for HealthcareIntegration.

RCU schema password myRCUpw674 Password for the databaseschemas used by Oracle B2Band SOA Suite for HealthcareIntegration.

Chapter 3Verifying the Installation Checklist

3-2

Table 3-1 (Cont.) Installation Checklist


Configuration utility ORACLE_HOME/oracle_common/common/bin

Path to the ConfigurationWizard for domain creationand configuration.

$FTP_ROOT $DOMAIN_HOME/product/ftp_root

Embedded FTP server rootdirectory.

Starting the Installation ProgramBefore running the installation program, you must verify the JDK and prerequisitesoftware is installed.

To start the installation program:

1. Sign in to the host system.

2. Change to the directory where you downloaded the installation program.

3. You must have installed the Oracle Fusion Middleware Infrastructure 12c(12.2.1.4.0). For instructions, see Installing the Infrastructure Software in Installingand Configuring the Oracle Fusion Middleware Infrastructure.

4. Start the installation program by running the java executable from the JDKdirectory. For example:

• (UNIX) /home/Oracle/Java/jdk1.8.0_211/bin/java -jarfmw_12.2.1.4.0_b2bhealthcare.jar

• (Windows) C:\home\Oracle\Java\jdk1.8.0_211\bin\java -jarfmw_12.2.1.4.0_b2bhealthcare.jar

Note:

You can also start the installer in silent mode using a saved response fileinstead of launching the installer screens. For more about silent or commandline installation, see Using the Oracle Universal Installer in Silent Mode inInstalling Software with the Oracle Universal Installer.

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

Navigating the Installation ScreensThe installer shows a series of screens where you verify or enter information.

The following table lists the order in which installer screens appear. If you needadditional help with an installation screen, click Help.

Chapter 3Starting the Installation Program

3-3

Table 3-2 Oracle B2B and SOA Suite for Healthcare Integration Install Screens

Screen Description

InstallationInventorySetup

On UNIX operating systems, this screen opens if this is the first time you areinstalling any Oracle product on this host. Specify the location where you wantto create your central inventory. Make sure that the operating system groupname selected on this screen has write permissions to the central inventorylocation.

For more about the central inventory, see About the Oracle Central Inventory inInstalling Software with the Oracle Universal Installer.

This screen does not appear on Windows operating systems.

Welcome Review the information to make sure that you have met all the prerequisites,then click Next.

Auto Updates Select to skip automatic updates, select patches, or search for the latestsoftware updates, including important security updates, through your My OracleSupport account.

InstallationLocation

Specify your Oracle home directory location.

This Oracle home must include Oracle Fusion Middleware Infrastructure , alongwith any other 12c (12.2.1.4.0) products that have been installed.

You can click View to verify and ensure that you are installing Oracle B2B andSOA Suite for Healthcare Integration in the correct Oracle home.

InstallationType

Select B2B if you are creating the B2B standard topology. Select Healthcare ifyou are creating a healthcare topology for HIPAA standards or HL7 documents.

PrerequisiteChecks

This screen verifies that your system meets the minimum necessaryrequirements.

To view the list of tasks that gets verified, select View Successful Tasks. Toview log details, select View Log. If any prerequisite check fails, then an errormessage appears at the bottom of the screen. Fix the error and click Rerunto try again. To ignore the error or the warning message and continue with theinstallation, click Skip (not recommended).

InstallationSummary

Use this screen to verify installation options you selected. If you want to savethese options to a response file, click Save Response File and enter theresponse file location and name. The response file collects and stores allthe information that you have entered, and enables you to perform a silentinstallation (from the command line) at a later time.

Click Install to begin the installation.

InstallationProgress

This screen shows the installation progress.

When the progress bar reaches 100% complete, click Finish to dismiss theinstaller, or click Next to see a summary.

InstallationComplete

This screen displays the Installation Location and the Feature Sets that areinstalled. Review this information and click Finish to close the installer.

Verifying the InstallationAfter you complete the installation, verify whether it was successful by completing aseries of tasks.

• Reviewing the Installation Log FilesReview the contents of the installation log files to make sure that the installer didnot encounter any problems.

Chapter 3Verifying the Installation

3-4

• Checking the Directory StructureThe contents of your installation vary based on the options that you selectedduring the installation.

• Viewing the Contents of the Oracle HomeYou can view the contents of the Oracle home directory by using theviewInventory script.

Reviewing the Installation Log FilesReview the contents of the installation log files to make sure that the installer did notencounter any problems.

By default, the installer writes logs files to the Oracle_Inventory_Location/logs(on UNIX operating systems) or Oracle_Inventory_Location\logs (on Windowsoperating systems) directory.

For a description of the log files and where to find them, see Installation Log Files inInstalling Software with the Oracle Universal Installer.

Checking the Directory StructureThe contents of your installation vary based on the options that you selected duringthe installation.

See What Are the Key Oracle Fusion Middleware Directories? in UnderstandingOracle Fusion Middleware.

Viewing the Contents of the Oracle HomeYou can view the contents of the Oracle home directory by using the viewInventoryscript.

See Viewing the Contents of an Oracle Home in Installing Software with the OracleUniversal Installer.

Chapter 3Verifying the Installation

3-5

4Configuring Oracle B2B Domain

After you have installed Oracle B2B, you can configure the domain, which you canalso extend for high availability.

The configuration steps presented here assume that you have completed theinstallation steps covered in:

• Preparing to Install and Configure Oracle B2B and SOA Suite for HealthcareIntegration

• Installing the Oracle B2B and SOA Suite for Healthcare Integration Software

Refer to the following sections to create the database schemas, configure a WebLogicdomain, and verify the configuration:

• Creating the Database SchemasBefore you can configure an Oracle B2B and SOA Suite for Healthcare Integrationdomain, you must install required schemas on a certified database for use with thisrelease of Oracle Fusion Middleware.

• Configuring the DomainUse the Configuration Wizard to create and configure a domain.

• Starting the ServersAfter configuration is complete, start Node Manager, then the WebLogicAdministration Server and Managed Servers.

• Verifying the ConfigurationAfter completing all configuration steps, you can perform additional steps to verifythat your domain is properly configured.

• Configuring Healthcare in a Weblogic Domain

Creating the Database SchemasBefore you can configure an Oracle B2B and SOA Suite for Healthcare Integrationdomain, you must install required schemas on a certified database for use with thisrelease of Oracle Fusion Middleware.

• Installing and Configuring a Certified DatabaseBefore you create the database schemas, you must install and configure acertified database, and verify that the database is up and running.

• Starting the Repository Creation UtilityStart the Repository Creation Utility (RCU) after you verify that a certified JDK isinstalled on your system.

• Navigating the Repository Creation Utility Screens to Create SchemasEnter required information in the RCU screens to create the database schemas.

4-1

Installing and Configuring a Certified DatabaseBefore you create the database schemas, you must install and configure a certifieddatabase, and verify that the database is up and running.

See About Database Requirements for an Oracle Fusion Middleware Installation.

Starting the Repository Creation UtilityStart the Repository Creation Utility (RCU) after you verify that a certified JDK isinstalled on your system.

To start the RCU:

1. Verify that a certified JDK already exists on your system by running java-version from the command line. For 12c (12.2.1.4.0), the certified JDK is1.8.0_211 and later.


2. Ensure that the JAVA_HOME environment variable is set to the location of thecertified JDK. For example:

• (UNIX) setenv JAVA_HOME /home/Oracle/Java/jdk1.8.0_211

• (Windows) set JAVA_HOME=C:\home\Oracle\Java\jdk1.8.0_211

3. Change to the following directory:

• (UNIX) ORACLE_HOME/oracle_common/bin

• (Windows) ORACLE_HOME\oracle_common\bin

4. Enter the following command:

• (UNIX) ./rcu

• (Windows) rcu.bat

Navigating the Repository Creation Utility Screens to Create SchemasEnter required information in the RCU screens to create the database schemas.

• Introducing the RCUThe Welcome screen is the first screen that appears when you start the RCU.

• Selecting a Method of Schema CreationUse the Create Repository screen to select a method to create and loadcomponent schemas into the database.

• Providing Database Connection DetailsOn the Database Connection Details screen, provide the database connectiondetails for the RCU to connect to your database.

• Specifying a Custom Prefix and Selecting Schemas for Oracle B2B andHealthcareSpecify a custom prefix and database schema to automatically select CommonInfrastructure Services and dependent schemas.

Chapter 4Creating the Database Schemas

4-2

• Specifying Schema PasswordsOn the Schema Passwords screen, specify how you want to set the schemapasswords on your database, then enter and confirm your passwords.

• Specifying Custom VariablesSpecify the custom variables for the SOA Infrastructure schema.

• Completing Schema CreationNavigate through the remaining RCU screens to complete schema creation.

Introducing the RCUThe Welcome screen is the first screen that appears when you start the RCU.

Click Next.

Selecting a Method of Schema CreationUse the Create Repository screen to select a method to create and load componentschemas into the database.

On the Create Repository screen:

• If you have the necessary permissions and privileges to perform DBA activities onyour database, select System Load and Product Load. This procedure assumesthat you have SYSDBA privileges.

• If you do not have the necessary permissions or privileges to perform DBAactivities in the database, you must select Prepare Scripts for System Load onthis screen. This option generates a SQL script that you can give to your databaseadministrator. See About System Load and Product Load in Creating Schemaswith the Repository Creation Utility.

• If the DBA has already run the SQL script for System Load, select PerformProduct Load.

Providing Database Connection DetailsOn the Database Connection Details screen, provide the database connection detailsfor the RCU to connect to your database.

Note:

If you are unsure of the service name for your database, you can obtainit from the SERVICE_NAMES parameter in the initialization parameter fileof the database. If the initialization parameter file does not contain theSERVICE_NAMES parameter, then the service name is the same as theglobal database name, which is specified in the DB_NAME and DB_DOMAINparameters.

For example:

Database Type: Oracle DatabaseHost Name: examplehost.exampledomain.comPort: 1521


4-3

Service Name: Orcl.exampledomain.comUser Name: sysPassword: ******Role: SYSDBA

Click Next to proceed, then click OK in the dialog window that confirms a successfuldatabase connection.

Specifying a Custom Prefix and Selecting Schemas for Oracle B2B andHealthcare

Specify a custom prefix and database schema to automatically select CommonInfrastructure Services and dependent schemas.

Select Create new prefix, specify a custom prefix, then select the SOASuite schema. This action automatically selects the following schemas asdependencies:

• User Messaging Service

• Metadata Services

• Oracle Platform Security Services

• Audit Services

• Audit Services Append

• Audit Services Viewer

• WebLogic Services

The schema Common Infrastructure Services is also automatically created; thisschema is grayed out; you cannot select or deselect it. This schema enables youto retrieve information from RCU during domain configuration. See Understanding theService Table Schema in Creating Schemas with the Repository Creation Utility.

The custom prefix is used to logically group these schemas together for use in thisdomain only; you must create a unique set of schemas for each domain as schemasharing across domains is not supported.

For more information about custom prefixes, see Understanding Custom Prefixes inCreating Schemas with the Repository Creation Utility.

For more information about how to organize your schemas in a multi-domainenvironment, see Planning Your Schema Creation in Creating Schemas with theRepository Creation Utility.

Tip:

You must make a note of the custom prefix you choose to enter here; you willneed this later on during the domain creation process.

Click Next to proceed, then click OK on the dialog window confirming that prerequisitechecking for schema creation was successful.


4-4

Specifying Schema PasswordsOn the Schema Passwords screen, specify how you want to set the schemapasswords on your database, then enter and confirm your passwords.

You must make a note of the passwords you set on this screen; you will need themlater on during the domain creation process.

Specifying Custom VariablesSpecify the custom variables for the SOA Infrastructure schema.

For the Oracle SOA Suite standard installation topology, set values for the DatabaseProfile (SMALL) and Healthcare Integration (NO for B2B installation, YES forHealthcare Integration for Oracle SOA Suite).

See About the Custom Variables Required for the SOA Suite Schemas

For more information about the options on this screen, see Custom Variables inCreating Schemas with the Repository Creation Utility.

Completing Schema CreationNavigate through the remaining RCU screens to complete schema creation.

On the Map Tablespaces screen, the Encrypt Tablespace check box appears only ifyou enabled Transparent Data Encryption (TDE) in the database (Oracle or OracleEBR) when you start the RCU. Select the Encrypt Tablespace check box if you wantto encrypt all new tablespaces that the RCU creates.

When you reach the Completion Summary screen, click Close to dismiss the RCU.

Configuring the DomainUse the Configuration Wizard to create and configure a domain.

For information on other methods to create domains, see Additional Tools for Creating,Extending, and Managing WebLogic Domains in Creating WebLogic Domains Usingthe Configuration Wizard.

• Starting the Configuration WizardStart the Configuration Wizard to begin configuring a domain.

• Navigating the Configuration Wizard Screens to Create and Configure the DomainEnter required information in the Configuration Wizard screens to create andconfigure the domain for the topology.

Starting the Configuration WizardStart the Configuration Wizard to begin configuring a domain.

To start the Configuration Wizard:


(UNIX) ORACLE_HOME/oracle_common/common/bin

Chapter 4Configuring the Domain

4-5

(Windows) ORACLE_HOME\oracle_common\common\bin

where ORACLE_HOME is your 12c (12.2.1.4.0) Oracle home.


(UNIX) ./config.sh

(Windows) config.cmd

Navigating the Configuration Wizard Screens to Create and Configurethe Domain

Enter required information in the Configuration Wizard screens to create and configurethe domain for the topology.

Note:

You can use this procedure to extend an existing domain. If your needs donot match the instructions in the procedure, be sure to make your selectionsaccordingly, or see the supporting documentation for more details.

• Selecting the Domain Type and Domain Home LocationUse the Configuration Type screen to select a Domain home directory location,optimally outside the Oracle home directory.

• Selecting the Configuration Templates for Oracle B2BUse the Templates screen to select the templates you require. You have the optionto create a Reference Configuration domain or a Classic domain.

• Configuring High Availability OptionsUse this screen to configure service migration and persistence settings thataffect high availability. This screen appears for the first time when you createa cluster that uses automatic service migration, persistent stores, or both, andall subsequent clusters that are added to the domain by using the ConfigurationWizard, automatically apply the selected HA options.

• Selecting the Application Home LocationUse the Application Location screen to select the location to store applicationsassociated with your domain, also known as the Application home directory.

• Configuring the Administrator AccountUse the Administrator Account screen to specify the user name and password forthe default WebLogic Administrator account for the domain.

• Specifying the Domain Mode and JDKUse the Domain Mode and JDK screen to specify the domain mode and JavaDevelopment Kit (JDK).

• Specifying the Database Configuration TypeUse the Database Configuration type screen to specify details about the databaseand database schema.

• Specifying JDBC Component Schema InformationUse the JDBC Component Schema screen to verify or specify details about thedatabase schemas.


4-6

• Testing the JDBC ConnectionsUse the JDBC Component Schema Test screen to test the data sourceconnections.

• Selecting Advanced ConfigurationUse the Advanced Configuration screen to complete the domain configuration.

• Configuring the Administration Server Listen AddressUse the Administration Server screen to select the IP address of the host.

• Configuring Node ManagerUse the Node Manager screen to select the type of Node Manager you want toconfigure, along with the Node Manager credentials.

• Configuring Managed Servers for Oracle B2BUse the Managed Servers screen to configure Managed Servers.

• Configuring a Cluster for Oracle B2BUse the Clusters screen to create a new cluster.

• Defining Server TemplatesIf you are creating dynamic clusters for a high availability setup, use the ServerTemplates screen to define one or more server templates for domain.

• Configuring Dynamic ServersIf you are creating dynamic clusters for a high availability setup, use the DynamicServers screen to configure the dynamic servers.

• Assigning Oracle B2B Managed Servers to the ClusterUse the Assign Servers to Clusters screen to assign Managed Servers to a newconfigured cluster. A configured cluster is a cluster you configure manually. You donot use this screen if you are configuring a dynamic cluster, a cluster that containsone or more generated server instances that are based on a server template.

• Configuring Coherence ClustersUse the Coherence Clusters screen to configure the Coherence cluster.

• Creating a New Oracle B2B MachineUse the Machines screen to create new machines in the domain. A machine isrequired so that Node Manager can start and stop servers.

• Assigning Servers to Oracle B2B MachinesUse the Assign Servers to Machines screen to assign the Administration Serverand Managed Servers to the new machine you just created.

• Virtual TargetsIf you have a WebLogic Server Multitenant (MT) environment, you use the VirtualTargets screen to add or delete virtual targets. For this installation (not a WebLogicServer MT environment), you do not enter any values; just select Next.

• PartitionsThe Partitions screen is used to configure partitions for virtual targets in WebLogicServer Multitenant (MT) environments. Select Next without selecting any options.

• Reviewing Your Configuration Specifications and Configuring the DomainThe Configuration Summary screen shows detailed configuration information forthe domain you are about to create.

• Writing Down Your Domain Home and Administration Server URLThe End of Configuration screen shows information about the domain you justconfigured.


4-7

Selecting the Domain Type and Domain Home LocationUse the Configuration Type screen to select a Domain home directory location,optimally outside the Oracle home directory.

Oracle recommends that you locate your Domain home in accordance with thedirectory structure in What Are the Key Oracle Fusion Middleware Directories? inUnderstanding Oracle Fusion Middleware, where the Domain home is located outsidethe Oracle home directory. This directory structure helps avoid issues when you needto upgrade or reinstall software.

To specify the Domain type and Domain home directory:

1. On the Configuration Type screen, select Create a new domain.

2. In the Domain Location field, specify your Domain home directory.

For more details about this screen, see Configuration Type in Creating WebLogicDomains Using the Configuration Wizard.

Selecting the Configuration Templates for Oracle B2BUse the Templates screen to select the templates you require. You have the option tocreate a Reference Configuration domain or a Classic domain.

Reference Configuration Domain

Note:

A Reference Configuration domain cannot be extended to BPM. You need tocreate a Classic domain to extend to BPM.

On the Templates screen, make sure that Create Domain Using Product Templatesis selected, then select Oracle B2B Reference Configuration [B2B].

• Oracle B2B Reference Configuration- 12.2.1.4.0 [B2B]

Selecting this template automatically selects the following as dependencies:

– Oracle SOA Suite Reference Configuration

– Oracle Enterprise Manager

– Oracle WSM Policy Manager

– Oracle JRF

– WebLogic Coherence Cluster Extension

To complete the Reference Configuration domain, perform the manual steps describedin Configuring Reference Configuration Domain Parameters.

For more information about configuring a Reference Configuration domain andenabling settings for developing projects, see:

• Configuring a Reference Configuration Domain in Administering Oracle SOA Suiteand Oracle Business Process Management Suite


4-8

https://docs.oracle.com/en/middleware/fusion-middleware/12.2.1.4/insoa/configuring-product-domain.html#GUID-5A5684F6-4CED-40DB-8606-DBA489920FAC

• Developing SOA Projects in Reference Configuration Mode in Developing SOAApplications with Oracle SOA Suite

Classic Domain

A Classic domain is the default domain for JDeveloper that contains all the featuresexcept for the Reference Configuration settings.

Click Browse and select oracle.soa.b2b.classic.domain_template.jar from theTemplates folder (b2b > common > templates > wls), then click OK.

Note:

oracle.soa.b2b.classic.domain_template.jar is a domain templateand not an extension template. Template has dependencies on BasicWeblogic Server Domain template (wls.jar) and Oracle B2B template(oracle.soa.b2b_template.jar). This template should not be used toextend any domain, it should be used only to create a new domain.

For more information about this screen, see Templates in Creating WebLogic DomainsUsing the Configuration Wizard.

Note:

To extend the B2B domain from Oracle SOA Suite domain or Oracle SOASuite Classic domain, select Oracle B2B template.Navigate to soa->common->templates->wls, and then selectoracle.soa.b2b_template.jar.

Configuring High Availability OptionsUse this screen to configure service migration and persistence settings that affect highavailability. This screen appears for the first time when you create a cluster that usesautomatic service migration, persistent stores, or both, and all subsequent clusters thatare added to the domain by using the Configuration Wizard, automatically apply theselected HA options.

Enable Automatic Service Migration

Select Enable Automatic Service Migration to enable pinned services to migrateautomatically to a healthy Managed Server for failover. It configures migratable targetdefinitions that are required for automatic service migration and the cluster leasing.Choose one of these cluster leasing options:

• Database Leasing - Managed Servers use a table on a valid JDBC SystemResource for leasing. Requires that the Automatic Migration data source havea valid JDBC System Resource. If you select this option, the Migration Basisis configured to Database and the Data Source for Automatic Migration isalso automatically configured by the Configuration Wizard. If you have a highavailability database, such as Oracle RAC, to manage leasing information,


4-9

configure the database for server migration according to steps in High-availabilityDatabase Leasing.

• Consensus Leasing - Managed Servers maintain leasing information in-memory.You use Node Manager to control Managed Servers in a cluster. (All serversthat are migratable, or which could host a migratable target, must have a NodeManager associated with them.) If you select this option, the Migration Basis isconfigured to Consensus by the Configuration Wizard.

See Leasing for more information on leasing.

See Service Migration for more information on Automatic Service Migration.

JTA Transaction Log Persistence

This section has two options: Default Persistent Store and JDBC TLog Store.

• Default Persistent Store - Configures the JTA Transaction Log store of the serversin the default file store.

• JDBC TLog Store - Configures the JTA Transaction Log store of the servers inJDBC stores.

Oracle recommends that you select JDBC TLog Store. When you complete theconfiguration, you have a cluster where JDBC persistent stores are set up forTransaction logs.

For more details on persistent and TLOG stores, see the following topics inDeveloping JTA Applications for Oracle WebLogic Server:

• Using the Default Persistent Store

• Using a JDBC TLOG Store

JMS Service Persistence

A persistent JMS store is a physical repository for storing persistent message dataand durable subscribers. It can be either a disk-based file store or a JDBC-accessibledatabase. You can use a JMS file store for paging of messages to disk when memoryis exhausted.

• JMS File Store - Configures a component to use JMS File Stores. If you selectthis option, you can choose the File Store option in the Advanced ConfigurationScreen to change the settings, if required. In the File Stores screen, you can setfile store names, directories, and synchronous write policies.

• JMS JDBC Store - Configures a component to use JDBC stores for all its JMSservers. When you complete the configuration, you have a cluster and JDBCpersistent stores are configured for the JMS servers.

Selecting the Application Home LocationUse the Application Location screen to select the location to store applicationsassociated with your domain, also known as the Application home directory.

Oracle recommends that you locate your Application home in accordance with thedirectory structure in What Are the Key Oracle Fusion Middleware Directories? inUnderstanding Oracle Fusion Middleware, where the Application home is locatedoutside the Oracle home directory. This directory structure helps avoid issues whenyou need to upgrade or re-install your software.


4-10

http://docs.oracle.com/cd/E12839_01/web.1111/e13709/migration.htm#i1048026

http://docs.oracle.com/cd/E12839_01/web.1111/e13709/migration.htm#i1048026

For more about the Application home directory, see About the Application HomeDirectory.

For more information about this screen, see Application Location in Creating WebLogicDomains Using the Configuration Wizard.

Configuring the Administrator AccountUse the Administrator Account screen to specify the user name and password for thedefault WebLogic Administrator account for the domain.

Oracle recommends that you make a note of the user name and password that youenter on this screen; you need these credentials later to boot and connect to thedomain's Administration Server.

Specifying the Domain Mode and JDKUse the Domain Mode and JDK screen to specify the domain mode and JavaDevelopment Kit (JDK).

On the Domain Mode and JDK screen:

• Select Production in the Domain Mode field.

• Select the Oracle HotSpot JDK in the JDK field.

For more information about this screen, see Domain Mode and JDK in CreatingWebLogic Domains Using the Configuration Wizard.

Specifying the Database Configuration TypeUse the Database Configuration type screen to specify details about the database anddatabase schema.

On the Database Configuration type screen, select RCU Data. This option instructsthe Configuration Wizard to connect to the database and Service Table (STB) schemato automatically retrieve schema information for schemas needed to configure thedomain.

Note:

If you select Manual Configuration on this screen, you must manually fill inparameters for your schema on the next screen.

After selecting RCU Data, specify details in the following fields:

Field Description

DBMS/Service Enter the database DBMS name, or service name if you selected aservice type driver.

Example: orcl.exampledomain.com

Host Name Enter the name of the server hosting the database.

Example: examplehost.exampledomain.com


4-11

Field Description

Port Enter the port number on which the database listens.

Example: 1521

Schema Owner

Schema Password

Enter the username and password for connecting to the database'sService Table schema. This is the schema username and passwordentered for the Service Table component on the Schema Passwordsscreen in the RCU (see Specifying Schema Passwords).

The default username is prefix_STB, where prefix is the customprefix that you defined in the RCU.

Click Get RCU Configuration when you finish specifying the database connectioninformation. The following output in the Connection Result Log indicates that theoperation succeeded:

Connecting to the database server...OKRetrieving schema data from database server...OKBinding local schema components with retrieved data...OK

Successfully Done.

For more information about the schema installed when the RCU is run, see About theService Table Schema in Creating Schemas with the Repository Creation Utility.

See Database Configuration Type in Creating WebLogic Domains Using theConfiguration Wizard .

Specifying JDBC Component Schema InformationUse the JDBC Component Schema screen to verify or specify details about thedatabase schemas.

Verify that the values populated on the JDBC Component Schema screen are correctfor all schemas. If you selected RCU Data on the previous screen, the schema tableshould already be populated appropriately.

For high availability environments, see the following sections in High Availability Guidefor additional information on configuring data sources for Oracle RAC databases:

• Configuring Active GridLink Data Sources with Oracle RAC

• Configuring Multi Data Sources

See JDBC Component Schema in Creating WebLogic Domains Using theConfiguration Wizard for more details about this screen.

Testing the JDBC ConnectionsUse the JDBC Component Schema Test screen to test the data source connections.

A green check mark in the Status column indicates a successful test. If you encounterany issues, see the error message in the Connection Result Log section of the screen,fix the problem, then try to test the connection again.

By default, the schema password for each schema component is the password youspecified while creating your schemas. If you want different passwords for different


4-12

schema components, manually edit them in the previous screen (JDBC ComponentSchema) by entering the password you want in the Schema Password column,against each row. After specifying the passwords, select the check box correspondingto the schemas that you changed the password in and test the connection again.

For more information about this screen, see JDBC Component Schema Test inCreating WebLogic Domains Using the Configuration Wizard.

Selecting Advanced ConfigurationUse the Advanced Configuration screen to complete the domain configuration.

On the Advanced Configuration screen, select:

• Administration Server

Required to properly configure the listen address of the Administration Server.

• Node Manager

Required to configure Node Manager.

• Topology

Required to configure the Oracle B2B Managed Server.

Optionally, select other available options as required for your desired installationenvironment. The steps in this guide describe a standard installation topology, butyou may choose to follow a different path. If your installation requirements extendto additional options outside the scope of this guide, you may be presented withadditional screens to configure those options. For information about all ConfigurationWizard screens, see Configuration Wizard Screens in Creating WebLogic DomainsUsing the Configuration Wizard.

Configuring the Administration Server Listen AddressUse the Administration Server screen to select the IP address of the host.

Select the drop-down list next to Listen Address and select the IP address of the hostwhere the Administration Server will reside, or use the system name or DNS namethat maps to a single IP address. Do not use All Local Addresses.

Do not specify any server groups for the Administration Server.

Configuring Node ManagerUse the Node Manager screen to select the type of Node Manager you want toconfigure, along with the Node Manager credentials.

Select Per Domain Default Location as the Node Manager type, then specify NodeManager credentials.

For more information about this screen, see Node Manager in Creating WebLogicDomains Using the Configuration Wizard.

For more about Node Manager types, see Node Manager Overview in AdministeringNode Manager for Oracle WebLogic Server.


4-13

Configuring Managed Servers for Oracle B2BUse the Managed Servers screen to configure Managed Servers.

On the Managed Servers screen, a new Managed Server named b2b_server1 isautomatically created by default.

Note:

When deployed on a SOA server, the default Managed Server name issoa_server1 instead of b2b_server1. In this guide, b2b_server1 is used toreadily identify this Managed Server.

To configure Managed Servers for Oracle B2B:

1. In the Listen Address drop-down list, select the IP address of the host on whichthe Managed Server will reside or use the system name or DNS name that mapsto a single IP address. Do not use All Local Addresses.

2. In the Server Groups drop-down list, make sure that SOA-MGD-SVRS is selected.This server group ensures that SOA and Oracle Web Services Manager (OWSM)services are targeted to the Managed Servers you are creating.

There is another server group called SOA-MGD-SVRS-ONLY that targets onlySOA but not Oracle Web Services Manager (OWSM) to the server. This is typicallyused if you want to have Oracle Web Services Manager (OWSM) in a differentserver rather than with the SOA server.

Server groups target Fusion Middleware applications and services to one or moreservers by mapping defined application service groups to each defined servergroup. A given application service group may be mapped to multiple server groupsif needed. Any application services that are mapped to a given server groupare automatically targeted to all servers that are assigned to that group. SeeApplication Service Groups, Server Groups, and Application Service Mappings inDomain Template Reference.

3. Configuring a second Managed Server is one of the steps needed to configurethe standard topology for high availability. If you are not creating a highly availableenvironment, then this step is optional.

Click Add and select SOA-MGD-SVRS to create a second Managed Servernamed b2b_server2.

For more information about the high availability standard topology, seeUnderstanding the Fusion Middleware Standard HA Topology in High AvailabilityGuide.

For more information about the next steps to prepare for high availability after yourdomain is configured, see Preparing Your Environment for High Availability.

These server names and will be referenced throughout this document; if you choosedifferent names be sure to replace them as needed.

For more information about this screen, see Managed Servers in Creating WebLogicDomains Using the Configuration Wizard.


4-14

Configuring a Cluster for Oracle B2BUse the Clusters screen to create a new cluster.

On the Clusters screen:

1. Click Add.

2. Specify b2b_cluster1 in the Cluster Name field.

3. Leave the Cluster Address field blank.

By default, server instances in a cluster communicate with one another usingunicast. If you want to change your cluster communications to use multicast, seeConsiderations for Choosing Unicast or Multicast in Administering Clusters for OracleWebLogic Server.

You can also create clusters using Fusion Middleware Control. In this case, youcan configure cluster communication (unicast or multicast) when you create the newcluster. See Create and configure clusters in Oracle WebLogic Server AdministrationConsole Online Help.

For more information about this screen, see Clusters in Creating WebLogic DomainsUsing the Configuration Wizard.

Defining Server TemplatesIf you are creating dynamic clusters for a high availability setup, use the ServerTemplates screen to define one or more server templates for domain.

To continue configuring the domain, click Next.

For steps to create a dynamic cluster for a high availability setup, see Using DynamicClusters in High Availability Guide.

Configuring Dynamic ServersIf you are creating dynamic clusters for a high availability setup, use the DynamicServers screen to configure the dynamic servers.

If you are not configuring a dynamic cluster, click Next to continue configuring thedomain.

Note:

When you create dynamic clusters, keep in mind that after you assign theMachine Name Match Expression, you do not need to create machines foryour dynamic cluster.

To create a dynamic cluster for a high availability setup, see Using Dynamic Clustersin High Availability Guide.


4-15

Assigning Oracle B2B Managed Servers to the ClusterUse the Assign Servers to Clusters screen to assign Managed Servers to a newconfigured cluster. A configured cluster is a cluster you configure manually. You do notuse this screen if you are configuring a dynamic cluster, a cluster that contains one ormore generated server instances that are based on a server template.

Note:

All Managed Servers of a component type in the domain must belong to thatcluster. For example, Oracle B2B domains support only a single Oracle B2Bcluster inside each domain.

For more on configured cluster and dynamic cluster terms, see About DynamicClusters in Understanding Oracle WebLogic Server.

On the Assign Servers to Clusters screen:

1. In the Clusters pane, select the cluster to which you want to assign the ManagedServers; in this case, b2b_cluster1.

2. In the Servers pane, assign b2b_server1 to b2b_cluster1 by doing one of thefollowing:

• Click once on b2b_server1 to select it, then click the right arrow to move itbeneath the selected cluster (b2b_cluster1) in the Clusters pane.

• Double-click on b2b_server1 to move it beneath the selected cluster(b2b_cluster1) in the Clusters pane.

3. Repeat to assign b2b_server2 to b2b_cluster1.

The following image shows a generic example of the Clusters pane after ManagedServers are assigned to clusters.For more information about this screen, see Assign Servers to Clusters in CreatingWebLogic Domains Using the Configuration Wizard.

Configuring Coherence ClustersUse the Coherence Clusters screen to configure the Coherence cluster.

Leave the default port number as the Coherence cluster listen port. After configuration,the Coherence cluster is automatically added to the domain.

Note:

Setting the unicast listen port to 0 creates an offset for the Managed Serverport numbers. The offset is 5000, meaning the maximum allowed value thatyou can assign to a Managed Server port number is 60535, instead of 65535.

See Table 5-2 for more information and next steps for configuring Coherence.


4-16

For Coherence licensing information, see Oracle Coherence Products in LicensingInformation.

Creating a New Oracle B2B MachineUse the Machines screen to create new machines in the domain. A machine isrequired so that Node Manager can start and stop servers.

If you plan to create a high availability environment and know the list of machinesyour target topology requires, you can follow the instructions in this section to createall the machines at this time. For more about scale out steps, see Optional Scale OutProcedure in High Availability Guide.

To create a new Oracle B2B machine so that Node Manager can start and stopservers:

1. Select the Machine tab (for Windows) or the UNIX Machine tab (for UNIX), thenclick Add to create a new machine.

2. In the Name field, specify a machine name, such as soa_machine1.

3. In the Node Manager Listen Address field, select the IP address of the machine inwhich the Managed Servers are being configured.

You must select a specific interface and not localhost. This allows Coherencecluster addresses to be dynamically calculated.

4. Verify the port in the Node Manager Listen Port field.

5. Repeat these steps to add more machines, if required.

Note:

If you are extending an existing domain, you can assign servers to anyexisting machine. It is not necessary to create a new machine unless yoursituation requires it.

For more information about this screen, see Machines in Creating WebLogic DomainsUsing the Configuration Wizard.

Assigning Servers to Oracle B2B MachinesUse the Assign Servers to Machines screen to assign the Administration Server andManaged Servers to the new machine you just created.

On the Assign Servers to Machines screen:

1. In the Machines pane, select the machine to which you want to assign the servers;in this case, soa_machine1.

2. In the Servers pane, assign AdminServer to soa_machine1 by doing one of thefollowing:

• Click once on AdminServer to select it, then click the right arrow to move itbeneath the selected machine (soa_machine1) in the Machines pane.


4-17

• Double-click on AdminServer to move it beneath the selected machine(soa_machine1) in the Machines pane.

3. Repeat these steps to assign all Managed Servers to their respective machines.

For more information about this screen, see Assign Servers to Machines in CreatingWebLogic Domains Using the Configuration Wizard.

Virtual TargetsIf you have a WebLogic Server Multitenant (MT) environment, you use the VirtualTargets screen to add or delete virtual targets. For this installation (not a WebLogicServer MT environment), you do not enter any values; just select Next.

For details about this screen, see Virtual Targets in Creating WebLogic Domains Usingthe Configuration Wizard.

Note:

WebLogic Server Multitenant virtual targets are deprecated in WebLogicServer 12.2.1.4.0 and will be removed in the next release.

PartitionsThe Partitions screen is used to configure partitions for virtual targets in WebLogicServer Multitenant (MT) environments. Select Next without selecting any options.

For details about options on this screen, see Partitions in Creating WebLogic DomainsUsing the Configuration Wizard.

Note:

WebLogic Server Multitenant domain partitions are deprecated in WebLogicServer 12.2.1.4.0 and will be removed in the next release.

Reviewing Your Configuration Specifications and Configuring the DomainThe Configuration Summary screen shows detailed configuration information for thedomain you are about to create.

Review each item on the screen and verify that the information is correct. To make anychanges, go back to a screen by clicking the Back button or selecting the screen inthe navigation pane. Domain creation does not start until you click Create.

For more details about options on this screen, see Configuration Summary in CreatingWebLogic Domains Using the Configuration Wizard.

Writing Down Your Domain Home and Administration Server URLThe End of Configuration screen shows information about the domain you justconfigured.

Make a note of the following items because you need them later:


4-18

• Domain Location

• Administration Server URL

You need the domain location to access scripts that start Node Manager andAdministration Server, and you need the URL to access the Administration Server.

Click Finish to dismiss the Configuration Wizard.

Starting the ServersAfter configuration is complete, start Node Manager, then the WebLogic AdministrationServer and Managed Servers.

For more information on additional tools you can use to manage your domain, seeOverview of Oracle Fusion Middleware Administration Tools in Administering OracleFusion Middleware.

• Starting Node Manager

• Starting the Administration Server

• Starting the Managed Servers

Starting Node ManagerTo start the per-domain Node Manager:





• (UNIX) Using nohup and nm.out as an example output file:

nohup ./startNodeManager.sh > LOG_DIR/nm.out&

where LOG_DIR is the location of directory in which you want to store the logfiles.

• (Windows) startNodeManager.cmd

Note:

On Windows operating systems, Oracle recommends that youconfigure Node Manager to run as a startup service. This allowsNode Manager to start up automatically each time the system isrestarted.

See Running Node Manager as a Startup Service in AdministeringNode Manager for Oracle WebLogic Server.

Starting the Administration ServerTo start the Administration Server:

Chapter 4Starting the Servers

4-19

1. Go to the DOMAIN_HOME/bin directory.


• (UNIX)

./startWebLogic.sh

• (Windows)

startWebLogic.cmd

If you selected Production Mode on the Domain Mode and JDK screen when youcreated the domain, you see a prompt for the Administrator user login credentials asprovided on the Administrator Account screen.

For more information about starting the Administration Server, see Starting andStopping Administration Server in Administering Oracle Fusion Middleware.

In production mode, a boot identity file can be created to bypass the need toprovide a user name and password when starting the Administration Server. For moreboot identity files, see Creating a Boot Identity File for an Administration Server inAdministering Server Startup and Shutdown for Oracle WebLogic Server.

You can verify that the Administration Server is up andrunning by accessing the Administration Server Console. TheURL is provided on the End of Configuration screen (http://administration_server_host:administration_server_port/console). The defaultAdministration Server port number is 7001.

Note:

Make sure that the database hosting your product schemas is up andrunning and accessible by the Administration Server.

For more information about how to use the Administration Console, see GettingStarted Using Oracle WebLogic Server Administration Console in Administering OracleFusion Middleware.

Starting the Managed ServersTo start the Managed Servers:

1. Sign in to Oracle Fusion Middleware Control:

http://administration_server_host:administration_server_port/em

The Administration Server host and port number were in the URL on the End ofConfiguration screen (Writing Down Your Domain Home and Administration ServerURL). The default Administration Server port number is 7001.

The login credentials were provided on the Administrator Account screen(Configuring the Administrator Account).

2. The Enterprise Manager landing page lists the servers configured for this domainand displays their status (such as Running or Shutdown). For a newly configureddomain, only the AdminServer(admin) will be running.


4-20

Select the first Managed Server.

3. Next to the WebLogic Server menu, select Start Up.

4. Repeat Steps 3 and 4 to start all Managed Servers.

5. On the main landing page, verify that all the Managed Servers are up and running.

Verifying the ConfigurationAfter completing all configuration steps, you can perform additional steps to verify thatyour domain is properly configured.

To verify that the domain is configured properly, see Performing Additional DomainConfiguration Tasks.

Configuring Healthcare in a Weblogic DomainOracle B2B healthcare domain (B2BHC) can only be created from SOA classicdomain. You must first create a SOA classic domain and then extend that to B2BHCdomain during the custom template.

Following are the steps to configure Oracle Healthcare domain in 12.2.1.4.0:

1. Install SOA bits using fmw_12.2.1.4.0_soa.jar.

2. Install Healthcare bits using fmw_12.2.1.4.0_b2bhealthcare.jar (SelectB2B+Healthcare).

3. Start the Config wizard using config.sh.

4. On the Templates page, select Create Domain using a custom template option.

5. Select a Template window and then navigate to soa-> common -> templates ->wls.

6. Select the file oracle.soa.classic.domain_template.jar to choose the SOAClassic domain template, and then click OK.

7. Complete the wizard to create a SOA domain.

8. Start the Config wizard again using config.sh.

9. In the Configuration Type, select Upgrade an existing domain and then clickNext.

10. On the Templates page, select Update Domain using a custom template option.

11. On the Select a Template window, navigate to soa->common->templates->wls.

12. Select the file oracle.soa.healthcare_template.jar to choose the Healthcaretemplate and then click OK.

13. Complete the wizard to create a SOA+Healthcare domain.

14. Start the soa managed server to access the Healthcare application.

Chapter 4Verifying the Configuration

4-21

5Configuring the Oracle SOA Suite forHealthcare Integration Domain

After you have installed Oracle SOA Suite for Healthcare Integration, you canconfigure the domain, which you can also extend for high availability.

The configuration steps presented here assume that you have completed theinstallation steps covered in:

• Preparing to Install and Configure Oracle B2B and SOA Suite for HealthcareIntegration

• Installing the Oracle B2B and SOA Suite for Healthcare Integration Software

Refer to the following sections to create the database schemas for Oracle SOA Suitefor Healthcare Integration, configure a WebLogic domain for Oracle SOA Suite forHealthcare Integration, and verify the configuration.

• Creating the Database SchemasBefore you can configure an Oracle B2B and SOA Suite for Healthcare Integrationdomain, you must install required schemas on a certified database for use with thisrelease of Oracle Fusion Middleware.

• Configuring the DomainUse the Configuration Wizard to create and configure a domain.

• Starting the ServersAfter configuration is complete, start Node Manager, then the WebLogicAdministration Server and Managed Servers.

• Verifying the ConfigurationAfter completing all configuration steps, you can perform additional steps to verifythat your domain is properly configured.

Creating the Database SchemasBefore you can configure an Oracle B2B and SOA Suite for Healthcare Integrationdomain, you must install required schemas on a certified database for use with thisrelease of Oracle Fusion Middleware.

• Installing and Configuring a Certified DatabaseBefore you create the database schemas, you must install and configure acertified database, and verify that the database is up and running.

• Starting the Repository Creation UtilityStart the Repository Creation Utility (RCU) after you verify that a certified JDK isinstalled on your system.

• Navigating the Repository Creation Utility Screens to Create SchemasEnter required information in the RCU screens to create the database schemas.

5-1

Installing and Configuring a Certified DatabaseBefore you create the database schemas, you must install and configure a certifieddatabase, and verify that the database is up and running.

See About Database Requirements for an Oracle Fusion Middleware Installation.

Starting the Repository Creation UtilityStart the Repository Creation Utility (RCU) after you verify that a certified JDK isinstalled on your system.

To start the RCU:

1. Verify that a certified JDK already exists on your system by running java-version from the command line. For 12c (12.2.1.4.0), the certified JDK is1.8.0_211 and later.


2. Ensure that the JAVA_HOME environment variable is set to the location of thecertified JDK. For example:




• (UNIX) ORACLE_HOME/oracle_common/bin

• (Windows) ORACLE_HOME\oracle_common\bin


• (UNIX) ./rcu

• (Windows) rcu.bat

Navigating the Repository Creation Utility Screens to Create SchemasEnter required information in the RCU screens to create the database schemas.

• Introducing the RCUThe Welcome screen is the first screen that appears when you start the RCU.

• Selecting a Method of Schema CreationUse the Create Repository screen to select a method to create and loadcomponent schemas into the database.

• Providing Database Connection DetailsOn the Database Connection Details screen, provide the database connectiondetails for the RCU to connect to your database.

• Specifying a Custom Prefix and Selecting Schemas for Oracle B2B andHealthcareSpecify a custom prefix and database schema to automatically select CommonInfrastructure Services and dependent schemas.


5-2

• Specifying Schema PasswordsOn the Schema Passwords screen, specify how you want to set the schemapasswords on your database, then enter and confirm your passwords.

• Specifying Custom VariablesSpecify the custom variables for the SOA Infrastructure schema.

• Completing Schema CreationNavigate through the remaining RCU screens to complete schema creation.

Introducing the RCUThe Welcome screen is the first screen that appears when you start the RCU.

Click Next.

Selecting a Method of Schema CreationUse the Create Repository screen to select a method to create and load componentschemas into the database.

On the Create Repository screen:

• If you have the necessary permissions and privileges to perform DBA activities onyour database, select System Load and Product Load. This procedure assumesthat you have SYSDBA privileges.

• If you do not have the necessary permissions or privileges to perform DBAactivities in the database, you must select Prepare Scripts for System Load onthis screen. This option generates a SQL script that you can give to your databaseadministrator. See About System Load and Product Load in Creating Schemaswith the Repository Creation Utility.

• If the DBA has already run the SQL script for System Load, select PerformProduct Load.

Providing Database Connection DetailsOn the Database Connection Details screen, provide the database connection detailsfor the RCU to connect to your database.

Note:

If you are unsure of the service name for your database, you can obtainit from the SERVICE_NAMES parameter in the initialization parameter fileof the database. If the initialization parameter file does not contain theSERVICE_NAMES parameter, then the service name is the same as theglobal database name, which is specified in the DB_NAME and DB_DOMAINparameters.

For example:

Database Type: Oracle DatabaseHost Name: examplehost.exampledomain.comPort: 1521


5-3

Service Name: Orcl.exampledomain.comUser Name: sysPassword: ******Role: SYSDBA

Click Next to proceed, then click OK in the dialog window that confirms a successfuldatabase connection.

Specifying a Custom Prefix and Selecting Schemas for Oracle B2B andHealthcare

Specify a custom prefix and database schema to automatically select CommonInfrastructure Services and dependent schemas.

Select Create new prefix, specify a custom prefix, then select the SOASuite schema. This action automatically selects the following schemas asdependencies:

• User Messaging Service

• Metadata Services

• Oracle Platform Security Services

• Audit Services

• Audit Services Append

• Audit Services Viewer

• WebLogic Services

The schema Common Infrastructure Services is also automatically created; thisschema is grayed out; you cannot select or deselect it. This schema enables youto retrieve information from RCU during domain configuration. See Understanding theService Table Schema in Creating Schemas with the Repository Creation Utility.

The custom prefix is used to logically group these schemas together for use in thisdomain only; you must create a unique set of schemas for each domain as schemasharing across domains is not supported.

For more information about custom prefixes, see Understanding Custom Prefixes inCreating Schemas with the Repository Creation Utility.

For more information about how to organize your schemas in a multi-domainenvironment, see Planning Your Schema Creation in Creating Schemas with theRepository Creation Utility.

Tip:

You must make a note of the custom prefix you choose to enter here; you willneed this later on during the domain creation process.

Click Next to proceed, then click OK on the dialog window confirming that prerequisitechecking for schema creation was successful.


5-4

Specifying Schema PasswordsOn the Schema Passwords screen, specify how you want to set the schemapasswords on your database, then enter and confirm your passwords.

You must make a note of the passwords you set on this screen; you will need themlater on during the domain creation process.

Specifying Custom VariablesSpecify the custom variables for the SOA Infrastructure schema.

For the Oracle SOA Suite standard installation topology, set values for the DatabaseProfile (SMALL) and Healthcare Integration (NO for B2B installation, YES forHealthcare Integration for Oracle SOA Suite).

See About the Custom Variables Required for the SOA Suite Schemas

For more information about the options on this screen, see Custom Variables inCreating Schemas with the Repository Creation Utility.

Completing Schema CreationNavigate through the remaining RCU screens to complete schema creation.

On the Map Tablespaces screen, the Encrypt Tablespace check box appears only ifyou enabled Transparent Data Encryption (TDE) in the database (Oracle or OracleEBR) when you start the RCU. Select the Encrypt Tablespace check box if you wantto encrypt all new tablespaces that the RCU creates.

When you reach the Completion Summary screen, click Close to dismiss the RCU.

Configuring the DomainUse the Configuration Wizard to create and configure a domain.

For information on other methods to create domains, see Additional Tools for Creating,Extending, and Managing WebLogic Domains in Creating WebLogic Domains Usingthe Configuration Wizard.

• Starting the Configuration WizardStart the Configuration Wizard to begin configuring a domain.

• Navigating the Configuration Wizard Screens to Create and Configure the DomainEnter required information in the Configuration Wizard screens to create andconfigure the domain for the topology.

Starting the Configuration WizardStart the Configuration Wizard to begin configuring a domain.

To start the Configuration Wizard:


(UNIX) ORACLE_HOME/oracle_common/common/bin


5-5

(Windows) ORACLE_HOME\oracle_common\common\bin

where ORACLE_HOME is your 12c (12.2.1.4.0) Oracle home.


(UNIX) ./config.sh

(Windows) config.cmd

Navigating the Configuration Wizard Screens to Create and Configurethe Domain

Enter required information in the Configuration Wizard screens to create and configurethe domain for the topology.

Note:

You can use this procedure to extend an existing domain. If your needs donot match the instructions in the procedure, be sure to make your selectionsaccordingly, or see the supporting documentation for more details.

• Selecting the Domain Type and Domain Home LocationUse the Configuration Type screen to select a Domain home directory location,optimally outside the Oracle home directory.

• Selecting the Configuration Templates for Oracle SOA Suite for HealthcareIntegrationUse the Templates screen to select the templates you require.

• Selecting the Application Home LocationUse the Application Location screen to select the location to store applicationsassociated with your domain, also known as the Application home directory.

• Configuring the Administrator AccountUse the Administrator Account screen to specify the user name and password forthe default WebLogic Administrator account for the domain.

• Specifying the Domain Mode and JDKUse the Domain Mode and JDK screen to specify the domain mode and JavaDevelopment Kit (JDK).

• Specifying the Database Configuration TypeUse the Database Configuration type screen to specify details about the databaseand database schema.

• Specifying JDBC Component Schema InformationUse the JDBC Component Schema screen to verify or specify details about thedatabase schemas.

• Testing the JDBC ConnectionsUse the JDBC Component Schema Test screen to test the data sourceconnections.

• Selecting Advanced ConfigurationUse the Advanced Configuration screen to complete the domain configuration.


5-6

• Configuring the Administration Server Listen AddressUse the Administration Server screen to select the IP address of the host.

• Configuring Node ManagerUse the Node Manager screen to select the type of Node Manager you want toconfigure, along with the Node Manager credentials.

• Configuring Managed Servers for Oracle HealthcareUse the Managed Servers screen to configure Managed Servers.

• Configuring a Cluster for Oracle HealthcareUse the Clusters screen to create a new cluster.

• Defining Server TemplatesIf you are creating dynamic clusters for a high availability setup, use the ServerTemplates screen to define one or more server templates for domain.

• Configuring Dynamic ServersIf you are creating dynamic clusters for a high availability setup, use the DynamicServers screen to configure the dynamic servers.

• Assigning Oracle Healthcare Managed Servers to the ClusterUse the Assign Servers to Clusters screen to assign Managed Servers to a newconfigured cluster. A configured cluster is a cluster you configure manually. You donot use this screen if you are configuring a dynamic cluster, a cluster that containsone or more generated server instances that are based on a server template.

• Configuring Coherence ClustersUse the Coherence Clusters screen to configure the Coherence cluster.

• Creating a New Oracle Healthcare MachineUse the Machines screen to create new machines in the domain. A machine isrequired so that Node Manager can start and stop servers.

• Assigning Servers to Oracle Healthcare MachinesUse the Assign Servers to Machines screen to assign the Administration Serverand Managed Servers to the new machine you just created.

• Virtual TargetsIf you have a WebLogic Server Multitenant (MT) environment, you use the VirtualTargets screen to add or delete virtual targets. For this installation (not a WebLogicServer MT environment), you do not enter any values; just select Next.

• PartitionsThe Partitions screen is used to configure partitions for virtual targets in WebLogicServer Multitenant (MT) environments. Select Next without selecting any options.

• Reviewing Your Configuration Specifications and Configuring the DomainThe Configuration Summary screen shows detailed configuration information forthe domain you are about to create.

• Writing Down Your Domain Home and Administration Server URLThe End of Configuration screen shows information about the domain you justconfigured.

Selecting the Domain Type and Domain Home LocationUse the Configuration Type screen to select a Domain home directory location,optimally outside the Oracle home directory.

Oracle recommends that you locate your Domain home in accordance with thedirectory structure in What Are the Key Oracle Fusion Middleware Directories? in


5-7

Understanding Oracle Fusion Middleware, where the Domain home is located outsidethe Oracle home directory. This directory structure helps avoid issues when you needto upgrade or reinstall software.

To specify the Domain type and Domain home directory:

1. On the Configuration Type screen, select Create a new domain.

2. In the Domain Location field, specify your Domain home directory.

For more details about this screen, see Configuration Type in Creating WebLogicDomains Using the Configuration Wizard.

Selecting the Configuration Templates for Oracle SOA Suite for HealthcareIntegration

Use the Templates screen to select the templates you require.

On the Templates screen, make sure Create Domain Using Product Templates isselected, then select the following templates:

• Oracle SOA Suite for healthcare integration - 12.2.1.4.0 [soa]

Selecting this template automatically selects the following as dependencies:

– Oracle B2B

– Oracle SOA Suite

– Oracle Enterprise Manager

– Oracle WSM Policy Manager

– Oracle JRF

– WebLogic Coherence Cluster Extension

For more information about this screen, see Templates in Creating WebLogic DomainsUsing the Configuration Wizard.

Selecting the Application Home LocationUse the Application Location screen to select the location to store applicationsassociated with your domain, also known as the Application home directory.

Oracle recommends that you locate your Application home in accordance with thedirectory structure in What Are the Key Oracle Fusion Middleware Directories? inUnderstanding Oracle Fusion Middleware, where the Application home is locatedoutside the Oracle home directory. This directory structure helps avoid issues whenyou need to upgrade or re-install your software.

For more about the Application home directory, see About the Application HomeDirectory.

For more information about this screen, see Application Location in Creating WebLogicDomains Using the Configuration Wizard.


5-8

Configuring the Administrator AccountUse the Administrator Account screen to specify the user name and password for thedefault WebLogic Administrator account for the domain.

Oracle recommends that you make a note of the user name and password that youenter on this screen; you need these credentials later to boot and connect to thedomain's Administration Server.

Specifying the Domain Mode and JDKUse the Domain Mode and JDK screen to specify the domain mode and JavaDevelopment Kit (JDK).

On the Domain Mode and JDK screen:

• Select Production in the Domain Mode field.

• Select the Oracle HotSpot JDK in the JDK field.

For more information about this screen, see Domain Mode and JDK in CreatingWebLogic Domains Using the Configuration Wizard.

Specifying the Database Configuration TypeUse the Database Configuration type screen to specify details about the database anddatabase schema.

On the Database Configuration type screen, select RCU Data. This option instructsthe Configuration Wizard to connect to the database and Service Table (STB) schemato automatically retrieve schema information for schemas needed to configure thedomain.

Note:

If you select Manual Configuration on this screen, you must manually fill inparameters for your schema on the next screen.

After selecting RCU Data, specify details in the following fields:

Field Description

DBMS/Service Enter the database DBMS name, or service name if you selected aservice type driver.

Example: orcl.exampledomain.com

Host Name Enter the name of the server hosting the database.

Example: examplehost.exampledomain.com

Port Enter the port number on which the database listens.

Example: 1521


5-9

Field Description

Schema Owner

Schema Password

Enter the username and password for connecting to the database'sService Table schema. This is the schema username and passwordentered for the Service Table component on the Schema Passwordsscreen in the RCU (see Specifying Schema Passwords).

The default username is prefix_STB, where prefix is the customprefix that you defined in the RCU.

Click Get RCU Configuration when you finish specifying the database connectioninformation. The following output in the Connection Result Log indicates that theoperation succeeded:

Connecting to the database server...OKRetrieving schema data from database server...OKBinding local schema components with retrieved data...OK

Successfully Done.

For more information about the schema installed when the RCU is run, see About theService Table Schema in Creating Schemas with the Repository Creation Utility.

See Database Configuration Type in Creating WebLogic Domains Using theConfiguration Wizard .

Specifying JDBC Component Schema InformationUse the JDBC Component Schema screen to verify or specify details about thedatabase schemas.

Verify that the values populated on the JDBC Component Schema screen are correctfor all schemas. If you selected RCU Data on the previous screen, the schema tableshould already be populated appropriately.

For high availability environments, see the following sections in High Availability Guidefor additional information on configuring data sources for Oracle RAC databases:

• Configuring Active GridLink Data Sources with Oracle RAC

• Configuring Multi Data Sources

See JDBC Component Schema in Creating WebLogic Domains Using theConfiguration Wizard for more details about this screen.

Testing the JDBC ConnectionsUse the JDBC Component Schema Test screen to test the data source connections.

A green check mark in the Status column indicates a successful test. If you encounterany issues, see the error message in the Connection Result Log section of the screen,fix the problem, then try to test the connection again.

By default, the schema password for each schema component is the password youspecified while creating your schemas. If you want different passwords for differentschema components, manually edit them in the previous screen (JDBC ComponentSchema) by entering the password you want in the Schema Password column,


5-10

against each row. After specifying the passwords, select the check box correspondingto the schemas that you changed the password in and test the connection again.

For more information about this screen, see JDBC Component Schema Test inCreating WebLogic Domains Using the Configuration Wizard.

Selecting Advanced ConfigurationUse the Advanced Configuration screen to complete the domain configuration.

On the Advanced Configuration screen, select:

• Administration Server

Required to properly configure the listen address of the Administration Server.

• Node Manager

Required to configure Node Manager.

• Topology

Required to configure the Oracle B2B Managed Server.

Optionally, select other available options as required for your desired installationenvironment. The steps in this guide describe a standard installation topology, butyou may choose to follow a different path. If your installation requirements extendto additional options outside the scope of this guide, you may be presented withadditional screens to configure those options. For information about all ConfigurationWizard screens, see Configuration Wizard Screens in Creating WebLogic DomainsUsing the Configuration Wizard.

Configuring the Administration Server Listen AddressUse the Administration Server screen to select the IP address of the host.

Select the drop-down list next to Listen Address and select the IP address of the hostwhere the Administration Server will reside, or use the system name or DNS namethat maps to a single IP address. Do not use All Local Addresses.

Do not specify any server groups for the Administration Server.

Configuring Node ManagerUse the Node Manager screen to select the type of Node Manager you want toconfigure, along with the Node Manager credentials.

Select Per Domain Default Location as the Node Manager type, then specify NodeManager credentials.

For more information about this screen, see Node Manager in Creating WebLogicDomains Using the Configuration Wizard.

For more about Node Manager types, see Node Manager Overview in AdministeringNode Manager for Oracle WebLogic Server.


5-11

Configuring Managed Servers for Oracle HealthcareUse the Managed Servers screen to configure Managed Servers.

On the Managed Servers screen, a new Managed Server named hc_server1 isautomatically created by default.

Note:

When deployed on a SOA server, the default Managed Server name issoa_server1 instead of hc_server1. In this guide, hc_server1 is used toreadily identify this Managed Server.

To configure Managed Servers for Oracle Healthcare:

1. In the Listen Address drop-down list, select the IP address of the host on whichthe Managed Server will reside or use the system name or DNS name that mapsto a single IP address. Do not use All Local Addresses.

2. In the Server Groups drop-down list, make sure that SOA-MGD-SVRS is selected.This server group ensures that SOA and Oracle Web Services Manager (OWSM)services are targeted to the Managed Servers you are creating.

There is another server group called SOA-MGD-SVRS-ONLY that targets onlySOA but not Oracle Web Services Manager (OWSM) to the server. This is typicallyused if you want to have Oracle Web Services Manager (OWSM) in a differentserver rather than with the SOA server.

Server groups target Fusion Middleware applications and services to one or moreservers by mapping defined application service groups to each defined servergroup. A given application service group may be mapped to multiple server groupsif needed. Any application services that are mapped to a given server groupare automatically targeted to all servers that are assigned to that group. SeeApplication Service Groups, Server Groups, and Application Service Mappings inDomain Template Reference.

3. Configuring a second Managed Server is one of the steps needed to configurethe standard topology for high availability. If you are not creating a highly availableenvironment, then this step is optional.

Click Add and select SOA-MGD-SVRS to create a second Managed Servernamed hc_server2.

For more information about the high availability standard topology, seeUnderstanding the Fusion Middleware Standard HA Topology in High AvailabilityGuide.

For more information about the next steps to prepare for high availability after yourdomain is configured, see Preparing Your Environment for High Availability.

These server names and will be referenced throughout this document; if you choosedifferent names be sure to replace them as needed.

For more information about this screen, see Managed Servers in Creating WebLogicDomains Using the Configuration Wizard.


5-12

Configuring a Cluster for Oracle HealthcareUse the Clusters screen to create a new cluster.

On the Clusters screen:

1. Click Add.

2. Specify hc_cluster1 in the Cluster Name field.

3. Leave the Cluster Address field blank.

By default, server instances in a cluster communicate with one another usingunicast. If you want to change your cluster communications to use multicast, seeConsiderations for Choosing Unicast or Multicast in Administering Clusters for OracleWebLogic Server.

You can also create clusters using Fusion Middleware Control. In this case, youcan configure cluster communication (unicast or multicast) when you create the newcluster. See Create and configure clusters in Oracle WebLogic Server AdministrationConsole Online Help.

For more information about this screen, see Clusters in Creating WebLogic DomainsUsing the Configuration Wizard.

Defining Server TemplatesIf you are creating dynamic clusters for a high availability setup, use the ServerTemplates screen to define one or more server templates for domain.

To continue configuring the domain, click Next.

For steps to create a dynamic cluster for a high availability setup, see Using DynamicClusters in High Availability Guide.

Configuring Dynamic ServersIf you are creating dynamic clusters for a high availability setup, use the DynamicServers screen to configure the dynamic servers.

If you are not configuring a dynamic cluster, click Next to continue configuring thedomain.

Note:

When you create dynamic clusters, keep in mind that after you assign theMachine Name Match Expression, you do not need to create machines foryour dynamic cluster.

To create a dynamic cluster for a high availability setup, see Using Dynamic Clustersin High Availability Guide.


5-13

Assigning Oracle Healthcare Managed Servers to the ClusterUse the Assign Servers to Clusters screen to assign Managed Servers to a newconfigured cluster. A configured cluster is a cluster you configure manually. You do notuse this screen if you are configuring a dynamic cluster, a cluster that contains one ormore generated server instances that are based on a server template.

Note:

All Managed Servers of a component type in the domain must belong to thatcluster. For example, Oracle SOA Suite for Healthcare Integration domainssupport only a single Healthcare cluster inside each domain.

See About Dynamic Clusters for more on configured cluster and dynamic clusterterms.

On the Assign Servers to Clusters screen:

1. In the Clusters pane, select the cluster to which you want to assign the ManagedServers; in this case, hc_cluster1.

2. In the Servers pane, assign hc_server1 to hc_cluster1 by doing one of thefollowing:

• Click once on hc_server1 to select it, then click the right arrow to move itbeneath the selected cluster (hc_cluster1) in the Clusters pane.

• Double-click on hc_server1 to move it beneath the selected cluster(hc_cluster1) in the clusters pane.

3. Repeat to assign hc_server2 to hc_cluster1.

The following image shows a generic example of the Clusters pane after ManagedServers are assigned to clusters.For more information about this screen, see Assign Servers to Clusters in CreatingWebLogic Domains Using the Configuration Wizard.

Configuring Coherence ClustersUse the Coherence Clusters screen to configure the Coherence cluster.

Leave the default port number as the Coherence cluster listen port. After configuration,the Coherence cluster is automatically added to the domain.

Note:

Setting the unicast listen port to 0 creates an offset for the Managed Serverport numbers. The offset is 5000, meaning the maximum allowed value thatyou can assign to a Managed Server port number is 60535, instead of 65535.

See Table 5-2 for more information and next steps for configuring Coherence.


5-14

For Coherence licensing information, see Oracle Coherence Products in LicensingInformation.

Creating a New Oracle Healthcare MachineUse the Machines screen to create new machines in the domain. A machine isrequired so that Node Manager can start and stop servers.

To create a new Oracle Healthcare machine so that Node Manager can start and stopservers:

1. Select the Machine tab (for Windows) or the UNIX Machine tab (for UNIX), thenclick Add to create a new machine.

2. In the Name field, specify a machine name, such as hc_machine1.

3. In the Node Manager Listen Address field, select the IP address of the machine inwhich the Managed Servers are being configured.

You must select a specific interface and not localhost. This allows Coherencecluster addresses to be dynamically calculated.

4. Verify the port in the Node Manager Listen Port field.

5. Repeat these steps to add more machines, if required.

Note:

If you are extending an existing domain, you can assign servers to anyexisting machine. It is not necessary to create a new machine unless yoursituation requires it.

For more information about this screen, see Machines in Creating WebLogic DomainsUsing the Configuration Wizard.

Assigning Servers to Oracle Healthcare MachinesUse the Assign Servers to Machines screen to assign the Administration Server andManaged Servers to the new machine you just created.

On the Assign Servers to Machines screen:

1. In the Machines pane, select the machine to which you want to assign the servers;in this case, hc_machine1.

2. In the Servers pane, assign AdminServer to hc_machine1 by doing one of thefollowing:

• Click once on AdminServer to select it, then click the right arrow to move itbeneath the selected machine (hc_machine1) in the Machines pane.

• Double-click on AdminServer to move it beneath the selected machine(hc_machine1) in the Machines pane.

3. Repeat these steps to assign all Managed Servers to their respective machines.

The following figure shows a generic example of the Machines pane after ManagedServers for a product are assigned to machines.


5-15

For more information about this screen, see Assign Servers to Machines in CreatingWebLogic Domains Using the Configuration Wizard.

Virtual TargetsIf you have a WebLogic Server Multitenant (MT) environment, you use the VirtualTargets screen to add or delete virtual targets. For this installation (not a WebLogicServer MT environment), you do not enter any values; just select Next.

For details about this screen, see Virtual Targets in Creating WebLogic Domains Usingthe Configuration Wizard.

Note:

WebLogic Server Multitenant virtual targets are deprecated in WebLogicServer 12.2.1.4.0 and will be removed in the next release.

PartitionsThe Partitions screen is used to configure partitions for virtual targets in WebLogicServer Multitenant (MT) environments. Select Next without selecting any options.

For details about options on this screen, see Partitions in Creating WebLogic DomainsUsing the Configuration Wizard.

Note:

WebLogic Server Multitenant domain partitions are deprecated in WebLogicServer 12.2.1.4.0 and will be removed in the next release.

Reviewing Your Configuration Specifications and Configuring the DomainThe Configuration Summary screen shows detailed configuration information for thedomain you are about to create.

Review each item on the screen and verify that the information is correct. To make anychanges, go back to a screen by clicking the Back button or selecting the screen inthe navigation pane. Domain creation does not start until you click Create.

For more details about options on this screen, see Configuration Summary in CreatingWebLogic Domains Using the Configuration Wizard.

Writing Down Your Domain Home and Administration Server URLThe End of Configuration screen shows information about the domain you justconfigured.

Make a note of the following items because you need them later:

• Domain Location

• Administration Server URL


5-16

You need the domain location to access scripts that start Node Manager andAdministration Server, and you need the URL to access the Administration Server.

Click Finish to dismiss the Configuration Wizard.

Starting the ServersAfter configuration is complete, start Node Manager, then the WebLogic AdministrationServer and Managed Servers.

For more information on additional tools you can use to manage your domain, seeOverview of Oracle Fusion Middleware Administration Tools in Administering OracleFusion Middleware.

• Starting Node Manager

• Starting the Administration Server

• Starting the Managed Servers

Starting Node ManagerTo start the per-domain Node Manager:





• (UNIX) Using nohup and nm.out as an example output file:

nohup ./startNodeManager.sh > LOG_DIR/nm.out&

where LOG_DIR is the location of directory in which you want to store the logfiles.

• (Windows) startNodeManager.cmd

Note:

On Windows operating systems, Oracle recommends that youconfigure Node Manager to run as a startup service. This allowsNode Manager to start up automatically each time the system isrestarted.

See Running Node Manager as a Startup Service in AdministeringNode Manager for Oracle WebLogic Server.

Starting the Administration ServerTo start the Administration Server:

1. Go to the DOMAIN_HOME/bin directory.



5-17

• (UNIX)

./startWebLogic.sh

• (Windows)

startWebLogic.cmd

If you selected Production Mode on the Domain Mode and JDK screen when youcreated the domain, you see a prompt for the Administrator user login credentials asprovided on the Administrator Account screen.

For more information about starting the Administration Server, see Starting andStopping Administration Server in Administering Oracle Fusion Middleware.

In production mode, a boot identity file can be created to bypass the need toprovide a user name and password when starting the Administration Server. For moreboot identity files, see Creating a Boot Identity File for an Administration Server inAdministering Server Startup and Shutdown for Oracle WebLogic Server.

You can verify that the Administration Server is up andrunning by accessing the Administration Server Console. TheURL is provided on the End of Configuration screen (http://administration_server_host:administration_server_port/console). The defaultAdministration Server port number is 7001.

Note:

Make sure that the database hosting your product schemas is up andrunning and accessible by the Administration Server.

For more information about how to use the Administration Console, see GettingStarted Using Oracle WebLogic Server Administration Console in Administering OracleFusion Middleware.

Starting the Managed ServersTo start the Managed Servers:

1. Sign in to Oracle Fusion Middleware Control:

http://administration_server_host:administration_server_port/em

The Administration Server host and port number were in the URL on the End ofConfiguration screen (Writing Down Your Domain Home and Administration ServerURL). The default Administration Server port number is 7001.

The login credentials were provided on the Administrator Account screen(Configuring the Administrator Account).

2. The Enterprise Manager landing page lists the servers configured for this domainand displays their status (such as Running or Shutdown). For a newly configureddomain, only the AdminServer(admin) will be running.

Select the first Managed Server.

3. Next to the WebLogic Server menu, select Start Up.


5-18

4. Repeat Steps 3 and 4 to start all Managed Servers.

5. On the main landing page, verify that all the Managed Servers are up and running.

Verifying the ConfigurationAfter completing all configuration steps, you can perform additional steps to verify thatyour domain is properly configured.

To verify that the domain is configured properly, see Performing Additional DomainConfiguration Tasks.

Chapter 5Verifying the Configuration

5-19

6Next Steps After Configuring the Domain

After you configure a product domain, there are additional tasks that you may want toperform.

• Performing Basic Administrative TasksReview the administrative tasks you will likely want to perform on a new domain.

• Performing Additional Domain Configuration TasksReview additional configuration tasks you will likely want to perform on a newdomain.

• Preparing Your Environment for High AvailabilityScaling out for high availability requires additional steps.

Performing Basic Administrative TasksReview the administrative tasks you will likely want to perform on a new domain.

Table 6-1 Basic Administration Tasks for a New Domain

Task Description More Information

Getting familiar with FusionMiddleware administration tools

Get familiar with various tools thatyou can use to manage yourenvironment.

See Overview of Oracle FusionMiddleware Administration Toolsin Administering Oracle FusionMiddleware.

Starting and stopping products andservers

Learn how to start and stopOracle Fusion Middleware, includingthe Administration Server, ManagedServers, and components.

See Starting and Stopping OracleFusion Middleware in AdministeringOracle Fusion Middleware.

Configuring Secure Sockets Layer(SSL)

Learn how to set up securecommunications between OracleFusion Middleware componentsusing SSL.

See Configuring SSL in OracleFusion Middleware in AdministeringOracle Fusion Middleware.

Monitoring Oracle Fusion Middleware Learn how to keep track of thestatus of Oracle Fusion Middlewarecomponents.

See Monitoring Oracle FusionMiddleware in Administering OracleFusion Middleware.

Understanding Backup and RecoveryProcedures

Learn the recommended backupand recovery procedures for OracleFusion Middleware.

See Introduction to Backup andRecovery in Administering OracleFusion Middleware.

Getting familiar with databasepurging

Get familiar with scheduling andrunning purge jobs that automaticallyremove older flow instances, adapterreports, and fault alerts data from thedatabase.

See Managing Database Growthin Administering Oracle SOA Suiteand Oracle Business ProcessManagement Suite.

6-1

Performing Additional Domain Configuration TasksReview additional configuration tasks you will likely want to perform on a new domain.

Table 6-2 Additional Domain Configuration Tasks


Deploying Applications Learn how to deploy yourapplications to Oracle FusionMiddleware.

See Deploying Applications inAdministering Oracle FusionMiddleware.

Adding a Web Tier front-end to yourdomain

Oracle Web Tier hosts Web pages(static and dynamic), providessecurity and high performancealong with built-in clustering, loadbalancing, and failover features. Inparticular, the Web Tier containsOracle HTTP Server.

To install and configure Oracle HTTPServer in the WebLogic Serverdomain, see Configuring OracleHTTP Server in a WebLogic ServerDomain in Installing and ConfiguringOracle HTTP Server.

See also Installing Multiple Productsin the Same Domain for importantinformation.

Tuning and configuring Coherencefor your topology

The standard installation topologyincludes a Coherence clusterthat contains storage-enabledManaged Coherence Servers. Thisconfiguration is a good starting pointfor using Coherence, but dependingupon your specific requirements,consider tuning and reconfiguringCoherence to improve performancein a production environment.

For more information aboutCoherence clusters, see Configuringand Managing Coherence Clustersin Administering Clusters for OracleWebLogic Server.

For information on tuning Coherence,see Performance Tuning inAdministering Oracle Coherence.

For information on storing HTTPsession data in Coherence,see Using Coherence*Web withWebLogic Server in AdministeringHTTP Session Management withOracle Coherence*Web.

For more about creating anddeploying Coherence applications,see Getting Started in DevelopingOracle Coherence Applications forOracle WebLogic Server.

Preparing Your Environment for High AvailabilityScaling out for high availability requires additional steps.

Table 6-3 provides a list of tasks to perform if you want to scale out your standardinstallation environment for high availability.

Chapter 6Performing Additional Domain Configuration Tasks

6-2

Table 6-3 Tasks Required to Prepare Your Environment for High Availability


Scaling out to multiple hostcomputers

To enable high availability, it is importantto provide failover capabilities to anotherhost computer. That way, if one computergoes down, your environment can continueto serve the consumers of your deployedapplications.

See Scaling Out a Topology(Machine Scale Out) in the HighAvailability Guide.

Configuring high availabilityfor your Web Tiercomponents.

If you have added a Web tier front-end, thenyou must configure the Web Tier for highavailability, as well as the WebLogic Serversoftware.

See Configuring High Availabilityfor Web Tier Components in HighAvailability Guide.

Setting up a front-end loadbalancer

A load balancer can be used to distributerequests across servers more evenly.

See Server Load Balancing in aHigh Availability Environment andConfiguring Load Balancer VirtualServer Names and Ports in HighAvailability Guide.

Configuring Node Manager Node Manager enables you to start,shut down, and restart the AdministrationServer and Managed Server instancesfrom a remote location. This documentassumes you have configured a per-domainNode Manager. Review the Node Managerdocumentation, for information on advancedNode Manager configuration options andfeatures.

See Advanced Node ManagerConfiguration in Administering NodeManager for Oracle WebLogicServer.

Chapter 6Preparing Your Environment for High Availability

6-3

7Uninstalling or Reinstalling Oracle B2B andSOA Suite for Healthcare Integration

Follow the instructions in this section to uninstall or reinstall Oracle B2B and SOASuite for Healthcare Integration.

Oracle recommends that you always use the instructions in this section to remove thesoftware. If you try to remove the software manually, you may encounter problemswhen you try to reinstall the software again at a later time. Following the procedures inthis section ensures that the software is properly removed.

• About Product UninstallationThe Oracle Fusion Middleware uninstaller removes the software from the Oraclehome directory.

• Stopping Oracle Fusion MiddlewareBefore running the Uninstall Wizard, Oracle recommends that you stop all serversand processes associated with the Oracle home you are going to remove.

• Removing Your Database SchemasBefore you remove the Oracle home, Oracle recommends that you run theRepository Creation Utility (RCU) to remove database schemas associated withthis domain.

• Uninstalling the SoftwareFollow the instructions in this section to start the Uninstall Wizard and remove thesoftware.

• Removing the Oracle Home Directory ManuallyAfter you uninstall the software, you must manually remove your Oracle homedirectory and any existing subdirectories that the Uninstall Wizard did not remove.

• Removing the Program Shortcuts on Windows Operating SystemsOn Windows operating systems, you must also manually remove the programshortcuts; the Deinstallation Wizard does not remove them for you.

• Removing the Domain and Application DataAfter you uninstall the software, you must remove the domain and applicationdata.

• Reinstalling the SoftwareYou can reinstall your software into the same Oracle home as a previousinstallation only if you uninstalled the software by following the instructions in thissection, including manually removing the Oracle home directory.

About Product UninstallationThe Oracle Fusion Middleware uninstaller removes the software from the Oracle homedirectory.

The following table summarizes the tasks to uninstall Fusion Middleware products.

7-1

Table 7-1 Roadmap for Product Uninstallation


Stop Oracle Fusion Middleware All servers and processes in yourdomain should be stopped beforerunning the uninstaller.

See Stopping Oracle FusionMiddleware.

Remove your database schemas Run Repository Creation Utility toremove your database schemas.

See Removing Your DatabaseSchemas.

Remove the software Run the product uninstaller toremove Oracle Fusion MiddlewareInfrastructure.

Note that if your Oracle homecontains multiple products, you mustrun the uninstaller multiple times,once for each product.

See Uninstalling the Software.

Remove the Oracle home directory The uninstaller does not remove allfiles and folders from the Oraclehome directory. After the uninstalleris finished, you must manuallyremove the Oracle home to completeyour product removal.

See Removing the Oracle HomeDirectory Manually.

Remove your domain and applicationdata

The uninstaller does not remove datacontained in your Domain home orApplication home directories, even ifthey are located inside the Oraclehome. You must remove thesedirectories manually.

See Removing the Domain andApplication Data.

Stopping Oracle Fusion MiddlewareBefore running the Uninstall Wizard, Oracle recommends that you stop all servers andprocesses associated with the Oracle home you are going to remove.

See Stopping an Oracle Fusion Middleware Environment in Administering OracleFusion Middleware.

Removing Your Database SchemasBefore you remove the Oracle home, Oracle recommends that you run the RepositoryCreation Utility (RCU) to remove database schemas associated with this domain.

Each domain has its own set of schemas, uniquely identified by a custom prefix.For more information about custom prefixes, see About Custom Prefixes in CreatingSchemas with the Repository Creation Utility. This set of schemas cannot be sharedwith any other domain. For more information about creating schemas with theRCU, see Planning Your Schema Creation in Creating Schemas with the RepositoryCreation Utility.

If there are multiple sets of schemas on your database, be sure to identify the schemaprefix associated with the domain that you are removing.

For schema removal steps, see Dropping Schemas in Creating Schemas with theRepository Creation Utility.

Chapter 7Stopping Oracle Fusion Middleware

7-2

Uninstalling the SoftwareFollow the instructions in this section to start the Uninstall Wizard and remove thesoftware.

If you want to uninstall the product in a silent (command-line) mode, see Running theOracle Universal Installer for Silent Uninstallation in Installing Software with the OracleUniversal Installer.

• Starting the Uninstall Wizard

• Selecting the Product to Uninstall

• Navigating the Uninstall Wizard Screens

Starting the Uninstall WizardTo start the Uninstall Wizard:


(UNIX) ORACLE_HOME/oui/bin

(Windows) ORACLE_HOME\oui\bin


(UNIX) ./deinstall.sh

(Windows) deinstall.cmd

Selecting the Product to UninstallBecause multiple products exist in the Oracle home, ensure that you are uninstallingthe correct product.

After you run the Uninstall Wizard, the Distribution to Uninstall screen opens. Fromthe dropdown menu, select B2B 12.2.1.4.0 and click Uninstall. The uninstallationprogram shows the screens listed in Navigating the Uninstall Wizard Screens.

Note:

You can uninstall Oracle Fusion Middleware Infrastructure after you uninstallOracle B2B and SOA Suite for Healthcare Integration software by runningthe Uninstall Wizard again. Before doing so, make sure that there are noother products using the Infrastructure; those products will no longer functiononce the Infrastructure is removed. You will not encounter the Distribution toUninstall screen if no other software depends on Oracle Fusion MiddlewareInfrastructure. See Uninstalling Oracle Fusion Middleware Infrastructure inInstalling and Configuring the Oracle Fusion Middleware Infrastructure.

Navigating the Uninstall Wizard ScreensThe Uninstall Wizard shows a series of screens to confirm the removal of the software.

Chapter 7Uninstalling the Software

7-3

If you need help on screen listed in Table 7-2, click Help on the screen.

Table 7-2 Uninstall Wizard Screens and Descriptions

Screen Description

Welcome Introduces you to the product Uninstall Wizard.

Uninstall Summary Shows the Oracle home directory and its contents that are uninstalled. Verify that this is thecorrect directory.

If you want to save these options to a response file, click Save Response File and enterthe response file location and name. You can use the response file later to uninstall theproduct in silent (command-line) mode. See Running the Oracle Universal Installer forSilent Uninstall in Installing Software with the Oracle Universal Installer.

Click Deinstall, to begin removing the software.

Uninstall Progress Shows the uninstallation progress.

Uninstall Complete Appears when the uninstallation is complete. Review the information on this screen, thenclick Finish to close the Uninstall Wizard.

Removing the Oracle Home Directory ManuallyAfter you uninstall the software, you must manually remove your Oracle homedirectory and any existing subdirectories that the Uninstall Wizard did not remove.

For example, if your Oracle home directory is /home/Oracle/product/ORACLE_HOME on a UNIX operating system, enter the following commands:

cd /home/Oracle/product rm -rf ORACLE_HOME

On a Windows operating system, if your Oracle home directory isC:\Oracle\Product\ORACLE_HOME, use a file manager window and navigate to theC:\Oracle\Product directory. Right-click on the ORACLE_HOME folder and selectDelete.

Removing the Program Shortcuts on Windows OperatingSystems

On Windows operating systems, you must also manually remove the programshortcuts; the Deinstallation Wizard does not remove them for you.

To remove the program shortcuts on Windows:

1. Change to the followingdirectory: C:\ProgramData\Microsoft\Windows\StartMenu\Programs\Oracle\ORACLE_HOME\Product

2. If you only have one product installed in your Oracle home, delete theORACLE_HOME directory. If you have multiple products installed in your Oraclehome, delete all products before you delete the ORACLE_HOME directory.

Chapter 7Removing the Oracle Home Directory Manually

7-4

Removing the Domain and Application DataAfter you uninstall the software, you must remove the domain and application data.

To remove the domain and application data:

1. Manually remove your Domain home directory. For example:

On a UNIX operating system, if your Domain home directory is /home/Oracle/config/domains/b2b_domain, enter the following command:

cd /home/Oracle/config/domains

rm -rf b2b_domain

On a Windows operating system, if your Domain home directory isC:\Oracle\Config\domains\b2b_domain, use a file manager window and navigateto the C:\Oracle\Config\domains directory. Right-click on the b2b_domain folderand select Delete.

2. Manually remove your Application home directory. For example:

On a UNIX operating system, if your Application home directory is /home/Oracle/config/applications/b2b_domain, enter the following commands:

cd /home/Oracle/config/applications

rm -rf b2b_domain

On a Windows operating system, if your Application home directory isC:\Oracle\Config\applications\b2b_domain, use a file manager window andnavigate to the C:\Oracle\Config\applications directory. Right-click on theb2b_domain folder and select Delete.

3. Back up the domain_registry.xml file in your Oracle home, then edit the file andremove the line associated with the domain that you are removing. For example,to remove the b2b_domain, find the following line and remove it:

<domain location="/home/Oracle/config/domains/b2b_domain"/>

Save and exit the file when you are finished.

Reinstalling the SoftwareYou can reinstall your software into the same Oracle home as a previous installationonly if you uninstalled the software by following the instructions in this section,including manually removing the Oracle home directory.

When you reinstall, you can then specify the same Oracle home as your previousinstallation.

If ODI is installed again in the same location where it was previously deleted, deletethe entire Oracle Home where it was previously installed.

Consider the following cases where the Oracle home is not empty:

• Installing in an existing Oracle home that contains the same feature sets.

The installer warns you that the Oracle home that you specified during installationalready contains the same software you are trying to install.

Chapter 7Removing the Domain and Application Data

7-5

You can either:

– Select a different installation type. In this case, only the feature sets that donot exist in the Oracle home directory are installed.

– Select a different Oracle home directory.

• Installing in an existing, non-empty Oracle home.

For example, suppose you chose to create your Domain home or Applicationhome somewhere inside your existing Oracle home. This data is not removedwhen you uninstall a product, so if you try to reinstall into the same Oracle home,the installer does not allow it. Your options are:

– Uninstall your software from the Oracle home (as this section describes) andthen remove the Oracle home directory. After you uninstall the software andremove the Oracle home directory, you can reinstall and reuse the sameOracle home location. Any domain or application data that was in the Oraclehome must be re-created.

– Select a different Oracle home directory.

Chapter 7Reinstalling the Software

7-6

ASecondary Topologies for Oracle B2B

This appendix describes secondary (alternate) topologies for Oracle B2B.

• Oracle SOA Suite, Oracle B2B, and Business Activity Monitoring TopologyUse this topology to implement Oracle Business Activity Monitoring (BAM) in yourOracle B2B domain.

• Oracle SOA Suite, Oracle B2B, and Oracle Service Bus TopologyUse this topology to implement Oracle Service Bus in your Oracle B2B domain.

Oracle SOA Suite, Oracle B2B, and Business ActivityMonitoring Topology

Use this topology to implement Oracle Business Activity Monitoring (BAM) in yourOracle B2B domain.

The BAM software is targeted to its own cluster; this ensures that there is no resourcecontention between the Oracle B2B and BAM software.

A-1

Figure A-1 BAM and B2B Topology

Roadmap for Installing and Configuring the Oracle SOA Suite, B2B, andBusiness Activity Monitoring Topology

The following table describes the roadmap needed to configure this topology on yoursystem.

Table A-1 Overview of the Installation and Configuration Steps for Oracle SOASuite, B2B, and Business Activity Monitoring

Task Description More Information Special Instructions

Verify your systemenvironment

Before beginning theinstallation, verifythat the minimumsystem and networkrequirements are met.

See Roadmap forVerifying Your SystemEnvironment.

None.

Appendix AOracle SOA Suite, Oracle B2B, and Business Activity Monitoring Topology

A-2

Table A-1 (Cont.) Overview of the Installation and Configuration Steps forOracle SOA Suite, B2B, and Business Activity Monitoring


Obtain the appropriatedistribution

Oracle B2B requiresan existing OracleSOA Suite and OracleFusion MiddlewareInfrastructureinstallation. Whenyou install OracleSOA Suite,Business ActivityMonitoring also getsautomatically installed.You must install B2Bin the same Oraclehome as OracleFusion MiddlewareInfrastructure andOracle SOA Suite.

See About ProductDistributions.

You must obtainall distributions ofOracle Infrastructure,Oracle SOA Suiteand Business ProcessManagement, andOracle B2B.

Determine yourinstallation directories

Verify that thedirectories that willneed to be createdcan be created oraccessed by theinstaller, and existon systems thatmeet the minimumrequirements.

See What Arethe Key OracleFusion MiddlewareDirectories? inUnderstanding OracleFusion Middleware.

None.

Install OracleFusion MiddlewareInfrastructure

Install OracleFusion MiddlewareInfrastructure to createthe Oracle homedirectory for OracleSOA Suite and B2B.

See Installing theInfrastructure Softwarein Installing andConfiguring the OracleFusion MiddlewareInfrastructure.

You do not needto configure OracleFusion MiddlewareInfrastructure.

Install Oracle SOASuite

Install the Oracle SOASuite software intothe existing OracleInfrastructure Oraclehome.

See Installing theOracle SOA Suiteand Oracle BusinessProcess ManagementSoftware in Installingand ConfiguringOracle SOA Suiteand Business ProcessManagement.

You do not need toconfigure Oracle SOASuite.

Install Oracle B2B Install the OracleB2B software intothe existing OracleInfrastructure andOracle SOA SuiteOracle home.

See Installing theOracle B2B and SOASuite for HealthcareIntegration Software.

Select B2B onthe Installation Typescreen.


A-3

Table A-1 (Cont.) Overview of the Installation and Configuration Steps forOracle SOA Suite, B2B, and Business Activity Monitoring


Create a WebLogicdomain

Use the configurationwizard to createand configure theWebLogic domain.Ensure that youselect the appropriateoptions on theconfiguration screens.

See ConfiguringOracle B2B Domain.

Follow the instructionsprovided for specificscreens in Table A-2.

Start the servers Once you completethe domaincreation, start theadministration andmanaged servers.

See Starting theServers.

None.

Verify theconfiguration

Verify to ensurethat the domain isconfigured properly.

See Verifying theConfiguration.

None.

Next steps afterinstalling andconfiguring OracleB2B.

You can performadministrative as wellas management tasksfor the domainthat you have justconfigured.

See Next StepsAfter Configuring theDomain.

None.

Configuration Options to Select for Oracle SOA Suite, Oracle B2B, and BusinessActivity Monitoring

Almost all of the screens and options that you must select while configuring OracleSOA Suite, Oracle B2B, and Business Activity Monitoring are identical to thoseprovided in Configuring the Domain. However, there are a couple of screens on whichyou must select different options, and Table A-2 lists the key screens and options.Ensure that you select the configuration options as provided in this section.

Table A-2 Key Screens and Configuration Options for Oracle SOA Suite, OracleB2B, and Business Activity Monitoring Topology

Screen Description

Templates This screen appears after you start theconfiguration wizard to create your domain.

In addition to the templates listed in Selectingthe Configuration Templates for Oracle B2B,select Business Activity Monitoring -12.2.1.4.0 [soa].


A-4

https://docs.oracle.com/middleware/1213/core/BTWOB/sec_topologies.htm#CHDGJIDC

Table A-2 (Cont.) Key Screens and Configuration Options for Oracle SOASuite, Oracle B2B, and Business Activity Monitoring Topology

Screen Description

Managed Servers On this screen, two managedservers are crated: bam_server1 andsoa_server1, are created. Click Add andcreate two more managed servers:bam_server2 and soa_server2.

Ensure that in the Listen Address drop-downlist, you select the IP address of the host onwhich the Managed Server will reside. Do notuse All Local Addresses.

In the Server Groups drop-down list, ensurethat soa_server1 and soa_server2 aretargeted to SOA-MGD-SVRS and bam_server1 and bam_server2 to BAM 12-MGD-SVRS-ONLY.

Clusters On this screen, create two clusters:soa_cluster1 and bam_cluster1.

Assign Servers to Clusters On this screen, assign the servers as follows:

• bam_server1 and bam_server2 to bam_cluster1

• soa_server1 and soa_server2 to soa_cluster1

Machines On this screen, create two machines:bam_machine1 and soa_machine1.

Assign Servers to Machine On this screen, assign the servers as follows:

• AdminServer, bam_server1, and bam_server2 to bam_machine1.

• soa_server1 and soa_server2 to soa_machine1.

Oracle SOA Suite, Oracle B2B, and Oracle Service BusTopology

Use this topology to implement Oracle Service Bus in your Oracle B2B domain.

The Oracle Service Bus software is targeted to its own cluster; this ensures that thereis no resource contention between the Oracle B2B and Oracle Service Bus software.

Appendix AOracle SOA Suite, Oracle B2B, and Oracle Service Bus Topology

A-5

Figure A-2 Roadmap for Installing and Configuring the Oracle SOA Suite, B2B,and Oracle Service Bus Topology

The following table describes the roadmap needed to configure this topology on yoursystem.

Table A-3 Overview of the Installation and Configuration Steps for Oracle SOASuite, B2B, and Oracle Service Bus Topology


Verify your systemenvironment

Before beginning theinstallation, verifythat the minimumsystem and networkrequirements are met.

See Roadmap forVerifying Your SystemEnvironment.

None.


A-6

Table A-3 (Cont.) Overview of the Installation and Configuration Steps forOracle SOA Suite, B2B, and Oracle Service Bus Topology


Obtain the appropriatedistribution

Oracle B2B requiresand existing OracleSOA Suite and OracleFusion MiddlewareInfrastructureinstallation. You mustinstall B2B inthe same Oraclehome as OracleFusion MiddlewareInfrastructure, OracleSOA Suite, and OracleService Bus.

See About ProductDistributions.

You must obtainall distributions ofOracle Infrastructure,Oracle SOA Suiteand Business ProcessManagement, andOracle Service Bus.

Determine yourinstallation directories

Verify that thedirectories that willneed to be createdcan be created oraccessed by theinstaller, and existon systems thatmeet the minimumrequirements.

See What Arethe Key OracleFusion MiddlewareDirectories? inUnderstanding OracleFusion Middleware.

None.

Install OracleFusion MiddlewareInfrastructure

Install OracleFusion MiddlewareInfrastructure to createthe Oracle homedirectory for OracleSOA Suite and B2B.

See Installing theInfrastructure Softwarein Installing andConfiguring the OracleFusion MiddlewareInfrastructure.

You do not needto configure OracleFusion MiddlewareInfrastructure.

Install Oracle SOASuite

Install the Oracle SOASuite software intothe existing OracleInfrastructure Oraclehome.

See Installing theOracle SOA Suiteand Oracle BusinessProcess ManagementSoftware in Installingand ConfiguringOracle SOA Suiteand Business ProcessManagement.

You do not need toconfigure Oracle SOASuite.

Install Oracle ServiceBus

Install the OracleService Bus softwareinto the existingOracle Infrastructureand Oracle SOA Suitehome.

See Installing theOracle Service BusSoftware in Installingand ConfiguringOracle Service Bus.

You do not needto configure OracleService Bus.

Install Oracle B2B Install the OracleB2B software intothe existing OracleInfrastructure andOracle SOA SuiteOracle home.

See Installing theOracle B2B and SOASuite for HealthcareIntegration Software.

Select B2B onthe Installation Typescreen.


A-7

Table A-3 (Cont.) Overview of the Installation and Configuration Steps forOracle SOA Suite, B2B, and Oracle Service Bus Topology


Create a WebLogicdomain

Use the configurationwizard to createand configure theWebLogic domain.Ensure that youselect the appropriateoptions on theconfiguration screens.

See ConfiguringOracle B2B Domain.

Follow the instructionsprovided for specificscreens in Table A-4.

Start the servers Once you completethe domaincreation, start theadministration andmanaged servers.

See Starting theServers.

None.

Verify theconfiguration

Verify to ensurethat the domain isconfigured properly.

See Verifying theConfiguration.

None.

Next steps afterinstalling andconfiguring OracleB2B.

You can performadministrative as wellas management tasksfor the domainthat you have justconfigured.

See Next StepsAfter Configuring theDomain.

None.

Configuration Options to Select for Oracle SOA Suite, Oracle B2B, and OracleService Bus

Almost all of the screens and options that you must select while configuring OracleSOA Suite, Oracle B2B, and Oracle Service Bus are identical to those provided inConfiguring the Domain. However, there are a couple of screens on which you mustselect different options, and Table A-2 lists the key screens and options. Ensure thatyou select the configuration options provided here.

Table A-4 Key Screens and Configuration Options for Oracle SOA Suite, OracleB2B, and Business Activity Monitoring Topology

Screen Description

Templates This screen appears after you start theconfiguration wizard to create your domain.

In addition to the templates listed in Selectingthe Configuration Templates for Oracle B2B,select Oracle Service Bus - 12.2.1.4.0 [soa].


A-8

https://docs.oracle.com/middleware/1213/core/BTWOB/sec_topologies.htm#CHDGJIDC

Table A-4 (Cont.) Key Screens and Configuration Options for Oracle SOASuite, Oracle B2B, and Business Activity Monitoring Topology

Screen Description

Managed Servers On this screen, two managed server arecreated: osb_server1 and soa_server1.Click Add and create two more managedservers: osb_server2 and soa_server2.

Ensure that in the Listen Address drop-downlist, you select the IP address of the host onwhich the Managed Server will reside. Do notuse All Local Addresses.

In the Server Groups drop-down list, ensurethat soa_server1 and soa_server2 aretargeted to SOA-MGD-SVRS and osb_server1 and osb_server2 to OSB 12-MGD-SVRS-ONLY.

Clusters On this screen, create twoclusters: soa_cluster1 and osb_cluster1.

Assign Servers to Clusters On this screen, assign the servers as follows:

• osb_server1 and osb_server2 to osb_cluster1

• soa_server1 and soa_server2 to soa_cluster1

Machines On this screen, create twomachines: osb_machine1 and soa_machine1.

Assign Servers to Machine On this screen, assign the servers as follows:

• AdminServer, osb_server1, and osb_server2 to osb_machine1.

• soa_server1 and soa_server2 to soa_machine1.


A-9

BUpdating the JDK After Installing andConfiguring an Oracle Fusion MiddlewareProduct

Consider that you have a JDK version jdk1.8.0_121 installed on your machine.When you install and configure an Oracle Fusion Middleware product, the utilities,such as Configuration Wizard (config.sh|exe), OPatch, or RCU point to a defaultJDK, for example, jdk1.8.0_121. After some time, Oracle releases a new versionof the JDK, say jdk1.8.0_211 that carries security enhancements and bug fixes.From 12c (12.2.1.3.0) onwards, you can upgrade the existing JDK to a newer version,and can have the complete product stack point to the newer version of the JDK.

You can maintain multiple versions of JDK and switch to the required version on needbasis.

• About Updating the JDK Location After Installing an Oracle Fusion MiddlewareProductThe binaries and other metadata and utility scripts in the Oracle home and Domainhome, such as RCU or Configuration Wizard, use a JDK version that was usedwhile installing the software and continue to refer to the same version of the JDK.The JDK path is stored in a variable called JAVA_HOME which is centrally locatedin .globalEnv.properties file inside the ORACLE_HOME/oui directory.

About Updating the JDK Location After Installing an OracleFusion Middleware Product

The binaries and other metadata and utility scripts in the Oracle home and Domainhome, such as RCU or Configuration Wizard, use a JDK version that was usedwhile installing the software and continue to refer to the same version of the JDK.The JDK path is stored in a variable called JAVA_HOME which is centrally locatedin .globalEnv.properties file inside the ORACLE_HOME/oui directory.

The utility scripts such as config.sh|cmd, launch.sh, or opatch reside in theORACLE_HOME, and when you invoke them, they refer to the JAVA_HOMEvariable located in .globalEnv.properties file. To point these scripts and utilities to thenewer version of JDK, you must update the value of the JAVA_HOME variable inthe .globalEnv.properties file by following the directions listed in Updating the JDKLocation in an Existing Oracle Home .

To make the scripts and files in your Domain home directory point to the newer versionof the JDK, you can follow one of the following approaches:

• Specify the path to the newer JDK on the Domain Mode and JDK screen whilerunning the Configuration Wizard.

For example, consider that you installed Oracle Fusion Middleware Infrastructurewith the JDK version 8u121. So while configuring the WebLogic domain with theConfiguration Assistant, you can select the path to the newer JDK on the Domain

B-1

Mode and JDK screen of the Configuration Wizard. Example: /scratch/jdk/jdk1.8.0_131.

• Manually locate the files that have references to the JDK using grep (UNIX) orfindstr (Windows) commands and update each reference. See Updating theJDK Location in an Existing Domain Home.

Note:

If you install the newer version of the JDK in the same location as theexisting JDK by overwriting the files, then you don’t need to take any action.

• Updating the JDK Location in an Existing Oracle HomeThe getProperty.sh|cmd script displays the value of a variable, such asJAVA_HOME, from the .globalEnv.properties file. The setProperty.sh|cmd scriptis used to set the value of variables, such as OLD_JAVA_HOME or JAVA_HOMEthat contain the locations of old and new JDKs in the .globalEnv.properties file.

• Updating the JDK Location in an Existing Domain HomeYou must search the references to the current JDK, for example jdk1.8.0_121manually, and replace those instances with the location of the new JDK.

Updating the JDK Location in an Existing Oracle HomeThe getProperty.sh|cmd script displays the value of a variable, such as JAVA_HOME,from the .globalEnv.properties file. The setProperty.sh|cmd script is used to setthe value of variables, such as OLD_JAVA_HOME or JAVA_HOME that contain thelocations of old and new JDKs in the .globalEnv.properties file.

The getProperty.sh|cmd and setProperty.sh|cmd scripts are located in the followinglocation:

(UNIX) ORACLE_HOME/oui/bin(Windows) ORACLE_HOME\oui\binWhere, ORACLE_HOME is the directory that contains the products using the currentversion of the JDK, such as jdk1.8.0_121.

To update the JDK location in the .globalEnv.properties file:

1. Use the getProperty.sh|cmd script to display the path of the current JDK from theJAVA_HOME variable. For example:

(UNIX) ORACLE_HOME/oui/bin/getProperty.sh JAVA_HOME(Windows) ORACLE_HOME\oui\bin\getProperty.cmd JAVA_HOMEecho JAVA_HOMEWhere JAVA_HOME is the variable in the .globalEnv.properties file that containsthe location of the JDK.

2. Back up the path of the current JDK to another variable such asOLD_JAVA_HOME in the .globalEnv.properties file by entering the followingcommands:

(UNIX) ORACLE_HOME/oui/bin/setProperty.sh -name OLD_JAVA_HOME-value specify_the_path_of_current_JDK(Windows) ORACLE_HOME\oui\bin\setProperty.cmd -nameOLD_JAVA_HOME -value specify_the_path_of_current_JDK

Appendix BAbout Updating the JDK Location After Installing an Oracle Fusion Middleware Product

B-2

This command creates a new variable called OLD_JAVA_HOME inthe .globalEnv.properties file, with a value that you have specified.

3. Set the new location of the JDK in the JAVA_HOME variable ofthe .globalEnv.properties file, by entering the following commands:

(UNIX) ORACLE_HOME/oui/bin/setProperty.sh -name JAVA_HOME -value specify_the_location_of_new_JDK(Windows) ORACLE_HOME\oui\bin\setProperty.cmd -name JAVA_HOME-value specify_the_location_of_new_JDK

After you run this command, the JAVA_HOME variable in the .globalEnv.propertiesfile now contains the path to the new JDK, such as jdk1.8.0_131.

Updating the JDK Location in an Existing Domain HomeYou must search the references to the current JDK, for example jdk1.8.0_121manually, and replace those instances with the location of the new JDK.

You can use the grep (UNIX) or findstr (Windows) commands to search for thejdk-related references.

You’ll likely be required to update the location of JDK in the following three files:

(UNIX) DOMAIN_HOME/bin/setNMJavaHome.sh(Windows) DOMAIN_HOME\bin\setNMJavaHome.cmd

(UNIX) DOMAIN_HOME/nodemanager/nodemanager.properties(Windows) DOMAIN_HOME\nodemanager\nodemanager.properties

(UNIX) DOMAIN_HOME/bin/setDomainEnv.sh(Windows) DOMAIN_HOME\bin\setDomainEnv.cmd

Appendix BAbout Updating the JDK Location After Installing an Oracle Fusion Middleware Product

B-3