Inbound Refinery is required for document conversion by Oracle WebCenter Content Server. This section provides an overview of Inbound Refinery.
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.
This section provides instructions for extending the existing enterprise deployment domain with the Inbound Refinery software.
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:
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.
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.1.0 [wccontent]
The following additional templates should already be selected, because they were used to create the initial domain:
Oracle Enterprise Manager - 12.2.1.1.0 [em]
Oracle WSM Policy Manager - 12.2.1.1.0 [oracle_common]
Oracle JRF - 12.2.1.1.0 [oracle_common]
WebLogic Coherence Cluster Extension - 12.2.1.1.0 [wlserver]
Tip:
More information about the options on this screen can be found in Templates in Creating WebLogic Domains Using the Configuration Wizard.
On the GridLink Oracle RAC Component Schema screen, click Next.
Click Next to continue.
To complete domain configuration for the topology, select the following option on the Advanced Configuration screen:
Server Template, Managed Servers, Clusters, Dynamic Servers, Virtual Targets and Coherence
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 14-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.
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.
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.
Use the Assign Servers to Clusters screen to assign WLS_IBR1 and WLS_IBR2 to the new cluster IBR_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 to IBR_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.
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.
Under the Unix Machine tab, verify the names of the machines you created when creating the initial Infrastructure domain.
Click Next to proceed.
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 assign WLS_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 to the next screen.
Click Next to proceed to the next screen.
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.
Domain creation will not begin until you click Update.
Tip:
More information about the options on this screen can be found in Configuration Summary in Creating WebLogic Domains Using the Configuration Wizard.
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.
Start the Administration Server to ensure the changes you have made to the domain have been applied.
This section describes how to do post-configuration and verification tasks for Inbound Refinery.
Follow these steps to start the Node Manager from the Managed Server home:
On WCCHOST1, navigate to the following directory:
MSERVER_HOME/bin
Use the following command to start the Node Manager:
nohup ./startNodeManager.sh > ./nodemanager.out 2>&1 &
Change directory to the following directory on WCCHOST2 and repeat the preceding step.
MSERVER_HOME/bin
For information about additional Node Manager configuration options, see Administering Node Manager for Oracle WebLogic Server.
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.
After you start the Inbound Refinery Managed Servers, configure the settings for each server on its post-installation configuration screen.
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.
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.
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.
To tell Content Server which files to send to Inbound Refinery to be converted, you need to select file formats.
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.