13 Extending the Domain to Include Inbound Refinery
- Overview of Extending the Domain to Include Inbound Refinery
Inbound Refinery is required for document conversion by Oracle WebCenter Content Server. - Support for Dynamic Clusters in Inbound Refinery
The WebCenter Content Inbound Refinery component does not support Dynamic Clusters. Only static configured cluster instructions are provided. - Extending the Domain for Inbound Refinery
The instructions for extending the existing enterprise deployment domain with the Inbound Refinery software are detailed in this section. - Completing Postconfiguration and Verification Tasks for Inbound Refinery
After extending the domain with the Inbound Refinery software, consider the following post-configuration and verification tasks. - Configuring the Inbound Refinery Managed Servers
To initialize the configuration of an Inbound Refinery Managed Server, you need to access it only once through HTTP. You can do this directly at the Managed Server's listen address. An Inbound Refinery instance should not be placed behind an HTTP server. - Validating the Configuration of the Inbound Refinery Managed Servers
To ensure that the Inbound Refinery Managed Servers you have created are properly configured, validate the configuration by logging in to Content Server and verifying that a file with an extension recognized as valid for conversion is correctly converted. - Backing Up the Configuration
It is an Oracle best practices recommendation to create a backup after you successfully extended a domain or at another logical point. Create a backup after you verify that the installation so far is successful. This is a quick backup for the express purpose of immediate restoration in case of problems in later steps.
Parent topic: Configuring the Enterprise Deployment
Overview of Extending the Domain to Include Inbound Refinery
Inbound Refinery is required for document conversion by Oracle WebCenter Content Server.
The actual number of Inbound Refinery Managed Servers varies depending on requirements. For availability reasons, Oracle recommends configuring at least two Inbound Refinery Managed Servers, each installed and configured on a separate machine. In the reference Oracle WebCenter Content enterprise deployment topology, Inbound Refinery will be configured on the same machine as Content Server.
Even though multiple Managed Servers are created in the process of extending the domain with Inbound Refinery in this enterprise deployment topology, each Inbound Refinery instance is completely independent. Inbound Refinery does not run in a cluster.
Parent topic: Extending the Domain to Include Inbound Refinery
Support for Dynamic Clusters in Inbound Refinery
The WebCenter Content Inbound Refinery component does not support Dynamic Clusters. Only static configured cluster instructions are provided.
Parent topic: Extending the Domain to Include Inbound Refinery
Extending the Domain for Inbound Refinery
The instructions for extending the existing enterprise deployment domain with the Inbound Refinery software are detailed in this section.
- Starting the Configuration Wizard
Start the Configuration Wizard as the first step to extend the existing enterprise deployment domain. - Navigating the Configuration Wizard Screens to Extend the Domain
Parent topic: Extending the Domain to Include Inbound Refinery
Starting the Configuration Wizard
Start the Configuration Wizard as the first step to extend the existing enterprise deployment domain.
Note:
If you added any customizations directly to the start scripts in the domain, those are overwritten by the configuration wizard. To customize server startup parameters that apply to all servers in a domain, you can create a file called setUserOverridesLate.sh
and configure it, for example, add custom libraries to the WebLogic Server classpath, specify Additional JAVA command line options for running the servers, or specify additional environment variables. Any customizations you add to this file are preserved during domain upgrade operations, and are carried over to remote servers when using the pack
and unpack
commands.
For more information about using the setUserOverridesLate
script with this Enterprise Deployment Guide, see Customizing Server Parameters with the setUserOverridesLate Script.
To start the Configuration Wizard:
Parent topic: Extending the Domain for Inbound Refinery
Navigating the Configuration Wizard Screens to Extend the Domain
Follow the instructions in this section to update and configure the domain for the topology.
Note:
You can use the same procedure described in this section to extend an existing domain. If your needs do not match the instructions given in the procedure, be sure to make your selections accordingly, or refer to the supporting documentation for additional details.
Domain creation and configuration includes the following tasks:
- Task 1 Selecting the Domain Type and Domain Home Location
-
On the Configuration Type screen, select Update an existing domain.
In the Domain Location field, select the value of the ASERVER_HOME variable, which represents the complete path to the initial Administration Server domain home you created.
For more information about the directory location variables, see File System and Directory Variables Used in This Guide.
Tip:
More information about the other options on this screen can be found in Configuration Type in Creating WebLogic Domains Using the Configuration Wizard.
Click Next to proceed.
- Task 2 Selecting the Configuration Template
-
On the Templates screen, make sure Update Domain Using Product Templates is selected, then select the following templates:
-
Oracle Universal Content Management - Inbound Refinery - 12.2.1.3.0 [wccontent]
The Infrastructure templates, WebCenter Portal templates, and WebCenter Content templates should already be selected, because they were used to create and update the initial domain.
Tip:
More information about the options on this screen can be found in Templates in Creating WebLogic Domains Using the Configuration Wizard.
Click Next to proceed.
-
- Task 3 Providing the GridLink Oracle RAC Database Connection Details
-
On the GridLink Oracle RAC Component Schema screen, click Next.
- Task 4 Testing the JDBC Connections
-
Click Next to continue.
- Task 5 Selecting Advanced Configuration
-
To complete domain configuration for the topology, select the following option on the Advanced Configuration screen:
Topology
Click Next to proceed.
- Task 6 Configuring Managed Servers
-
On the Managed Servers screen, a new Managed Server appears in the list of servers.
Perform the following tasks to modify the default Managed Server and create a second Managed Server:
-
Rename the default Managed Server to
WLS_IBR1
. -
Click Add to create a new Managed Server and name it
WLS_IBR2
.Tip:
The server names recommended here will be used throughout this document. If you choose different names be sure to replace them as needed.
-
Use the information in the following table to fill in the rest of the columns for each Managed Server.
Table 13-1 Values Required for Each Oracle Inbound Refinery Server
Server Name Listen Address Listen Port Enable SSL SSL Listen Port Server Group WLS_IBR1
WCCHOST1
16250
No
Disabled
IBR-MGD-SVR
WLS_IBR2
WCCHOST2
16250
No
Disabled
IBR-MGD-SVR
Tip:
More information about the options on the Managed Server screen can be found in Managed Servers in Creating WebLogic Domains Using the Configuration Wizard.
Click Next to proceed.
-
- Task 7 Configuring a Cluster
-
In this task, you create a cluster of Managed Servers to which you can target the Oracle Inbound Refinery software.
Use the Clusters screen to create a new cluster:
-
Click the Add button.
-
Specify
IBR_Servers
in the Cluster Name field. -
From the Dynamic Server Groups drop-down list, select
Unspecified
. -
Click Next to proceed to the next screen.
Note:
By default, server instances in a cluster communicate with one another using unicast. If you want to change your cluster communications to use multicast, refer to "Considerations for Choosing Unicast or Multicast" in Administering Clusters for Oracle WebLogic Server.
Tip:
More information about the options on this screen can be found in Clusters in Creating WebLogic Domains Using the Configuration Wizard.
-
- Task 8 Assigning Server Templates
-
Click Next to proceed to the next screen.
- Task 9 Configuring Dynamic Servers
-
Verity that all dynamic server options are disabled and unchecked for the
IBR_Servers
static (configured) cluster.-
Confirm that the Dynamic Cluster, Calculated Listen Port, and Calculated Machine Names checkboxes on this screen are unchecked.
-
Confirm the Server Template selection is Unspecified.
-
Click Next to proceed.
-
- Task 10 Assigning Managed Servers to the Cluster
-
Use the Assign Servers to Clusters screen to assign
WLS_IBR1
andWLS_IBR2
to the new clusterIBR_Servers
:-
In the Clusters pane, select the cluster to which you want to assign the servers; in this case,
IBR_Servers
. -
In the Servers pane, assign WLS_IBR1 to
IBR_Servers
by doing one of the following:-
Click once on
WLS_IBR1
Managed Server to select it, then click on the right arrow to move it beneath the selected cluster in the Clusters pane. -
Double-click
WLS_IBR1
to move it beneath the selected cluster in the clusters pane.
-
-
Repeat to assign
WLS_IBR2
toIBR_Servers
.Tip:
More information about the options on this screen can be found in Assign Servers to Clusters in Creating WebLogic Domains Using the Configuration Wizard.
-
Click Next to proceed.
-
- Task 11 Configuring Coherence Clusters
-
Use the Coherence Clusters screen to configure the Coherence cluster that is automatically added to the domain. Leave the port number value at
9991
, as it was defined during the initial Infrastructure domain creation.Note:
For Coherence licensing information, refer to Oracle Coherence in Oracle Fusion Middleware Licensing Information.
Click Next to proceed.
- Task 12 Verifying the Existing Machines
-
Under the Unix Machine tab, verify the names of the machines you created when creating the initial Infrastructure domain.
Click Next to proceed.
- Task 13 Assigning Servers to Machines
-
Use the Assign Servers to Machines screen to assign the Oracle Inbound Refinery Managed Servers you just created to the corresponding machines in the domain.
Assign
WLS_IBR1
to WCCHOST1, and assignWLS_IBR2
to WCCHOST2.Tip:
More information about the options on this screen can be found in Assign Servers to Machines in Creating WebLogic Domains Using the Configuration Wizard.
Click Next to proceed.
- Task 14 Reviewing Virtual Targets
-
Click Next to proceed to the next screen.
- Task 15 Reviewing Partitions
-
Click Next to proceed to the next screen.
- Task 16 Reviewing Your Configuration Specifications and Configuring the Domain
-
The Configuration Summary screen contains the detailed configuration information for the domain. Review the details of each item on the screen and verify that the information is correct.
You can go back to any previous screen if you need to make any changes, either by using the Back button or by selecting the screen in the navigation pane.
Click Update to execute the domain extension.
Tip:
More information about the options on this screen can be found in Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.
- Task 17 Writing Down Your Domain Home and Administration Server URL
-
The Configuration Success screen will show the following items about the domain you just configured:
-
Domain Location
-
Administration Server URL
You must make a note of both items as you will need them later; the domain location is needed to access the scripts used to start the Node Manager and Administration Server, and the URL is needed to access the Administration Server.
Click Finish to dismiss the Configuration Wizard.
-
- Task 18 Start the Administration Server
-
Start the Administration Server to ensure the changes you have made to the domain have been applied.
Parent topic: Extending the Domain for Inbound Refinery
Completing Postconfiguration and Verification Tasks for Inbound Refinery
After extending the domain with the Inbound Refinery software, consider the following post-configuration and verification tasks.
- Propagate the Domain Configuration Updates for Inbound Refinery
- Updating the NodeManager Configuration After Unpacking the Domain
When extending a domain, thenodemanager.properties
file in MSERVER_HOME may be overwritten with some values from thenodemanager.properties
file for ASERVER_HOME. Specifically, theListenAddress
and/orCustomIdentityAlias
values can be reset. - Starting the Inbound Refinery Managed Servers
Parent topic: Extending the Domain to Include Inbound Refinery
Propagate the Domain Configuration Updates for Inbound Refinery
Updating the NodeManager Configuration After Unpacking the Domain
When extending a domain, the nodemanager.properties
file in MSERVER_HOME may be overwritten with some values from the nodemanager.properties
file for ASERVER_HOME. Specifically, the ListenAddress
and/or CustomIdentityAlias
values can be reset.
Notes::
-
The
ListenAddress
may typically get reset on the MSERVER_HOME nodemanager residing on the same host as the ASERVER_HOME nodemanager. In this topology, WCCHOST1. -
For domain extensions prior to Enabling SSL Communication Between the SOA Servers and the Hardware Load Balancer, steps 2 through 4 regarding the
CustomIdentityAlias
may not be applicable.
MSERVER_HOME/nodemanager/nodemanager.properties
file on each host:
Note:
For more information about theCustomIdentityAlias
parameter, see Configuring Node Manager to Use the Custom Keystores.
Configuring the Inbound Refinery Managed Servers
To initialize the configuration of an Inbound Refinery Managed Server, you need to access it only once through HTTP. You can do this directly at the Managed Server's listen address. An Inbound Refinery instance should not be placed behind an HTTP server.
All subsequent access to the Inbound Refinery instance is through the socket listener. This listener is protected through the incoming socket connection address security filter configured in the next section.
Oracle recommends configuring each Content Server instance with all Inbound Refinery instances. The process for configuring Content Server is to add each Inbound Refinery instance as a provider. You also need to perform some post-installation steps with Inbound Refinery.
The following sections describe the procedures for post-installation configuration of each Inbound Refinery instance.
- Configuring Inbound Refinery Settings
After starting the Inbound Refinery Managed Servers, configure the settings for each server on its post-installation configuration screen. - Setting Up Content Server to Send Jobs to Inbound Refinery for Conversion
Before Oracle WebCenter Content Server can send jobs to Inbound Refinery for conversion, you need to perform the setup tasks described in the following sections for each Inbound Refinery Managed Server.
Parent topic: Extending the Domain to Include Inbound Refinery
Configuring Inbound Refinery Settings
After starting the Inbound Refinery Managed Servers, configure the settings for each server on its post-installation configuration screen.
Parent topic: Configuring the Inbound Refinery Managed Servers
Setting Up Content Server to Send Jobs to Inbound Refinery for Conversion
Before Oracle WebCenter Content Server can send jobs to Inbound Refinery for conversion, you need to perform the setup tasks described in the following sections for each Inbound Refinery Managed Server.
- Creating an Outgoing Provider
Before Content Server can send files to Inbound Refinery for conversion, you must set up an outgoing provider from Content Server to each Inbound Refinery with the Handles Inbound Refinery Conversion Jobs option checked. - Enabling Components for Inbound Refinery on Content Server
Some conversion types require helper components to be enabled on Content Server. The InboundRefinerySupport component must always be enabled on any Content Server instance that uses Inbound Refinery for document conversion. It is enabled by default on a new Content Server installation. - Selecting File Formats To Be Converted
To tell Content Server which files to send to Inbound Refinery to be converted, you need to select file formats.
Parent topic: Configuring the Inbound Refinery Managed Servers
Creating an Outgoing Provider
Before Content Server can send files to Inbound Refinery for conversion, you must set up an outgoing provider from Content Server to each Inbound Refinery with the Handles Inbound Refinery Conversion Jobs option checked.
Enabling Components for Inbound Refinery on Content Server
Some conversion types require helper components to be enabled on Content Server. The InboundRefinerySupport component must always be enabled on any Content Server instance that uses Inbound Refinery for document conversion. It is enabled by default on a new Content Server installation.
Selecting File Formats To Be Converted
To tell Content Server which files to send to Inbound Refinery to be converted, you need to select file formats.
Validating the Configuration of the Inbound Refinery Managed Servers
To ensure that the Inbound Refinery Managed Servers you have created are properly configured, validate the configuration by logging in to Content Server and verifying that a file with an extension recognized as valid for conversion is correctly converted.
For example, if you selected docx
as a format to be converted, you can convert a Microsoft Word document with a .docx
extension to PDF format.
For information about the check-in and check-out procedures, see "Uploading Documents" and "Checking Out and Downloading Files" in Oracle Fusion Middleware Using Oracle WebCenter Content.
For information about the conversion process, see "Configuring Content Servers to Send Jobs to Refineries" in Oracle Fusion Middleware Managing Oracle WebCenter Content.
Parent topic: Extending the Domain to Include Inbound Refinery
Backing Up the Configuration
It is an Oracle best practices recommendation to create a backup after you successfully extended a domain or at another logical point. Create a backup after you verify that the installation so far is successful. This is a quick backup for the express purpose of immediate restoration in case of problems in later steps.
The backup destination is the local disk. You can discard this backup when the enterprise deployment setup is complete. After the enterprise deployment setup is complete, you can initiate the regular deployment-specific Backup and Recovery process.
For information about backing up your configuration, see Performing Backups and Recoveries for an Enterprise Deployment.
Parent topic: Extending the Domain to Include Inbound Refinery