Managing Conversions 2-5
■
Each refinery will need to be added as a provider to each content server. For details, see
Configuring Refinery Providers on page 2-5.
2.1.1.5 Scenario E
This scenario comprises multiple refineries per content server on separate computers.
2.1.1.5.1 Benefits
■
Fastest processing for high volumes of content and big file sizes.
■
Refinery processing does not affect content server searches and access to the web site, and vice versa.
2.1.1.5.2 Considerations
■
Each refinery computer needs a copy of all third-party applications required for conversion.
■
In this configuration, typically the following choices should be made when deploying the refineries:
– Each refinery will need to be added as a provider to each content server. For
details, see Configuring Refinery Providers
on page 2-5.
2.1.2 Configuring Refinery Providers
This section covers the following topics:
■
About Content Server and Refinery Providers on page 2-5
■
Adding Refinery Providers on page 2-5
■
Editing Refinery Providers on page 2-6
■
DisablingEnabling Refinery Providers on page 2-7
■
Deleting Refinery Providers on page 2-7
2.1.2.1 About Content Server and Refinery Providers
A content server communicates with a refinery via a provider. A refinery can serve as a provider for one or multiple content servers. For more information about common
configurations, see Content Server and Refinery Configuration Scenarios
on page 2-1.
You can add the refinery as a provider to a content server on the same computer, or you can add the refinery as a provider to content servers on separate computers after
deployment.
2.1.2.2 Adding Refinery Providers
To add a refinery as a provider to a content server, complete the following steps:
2-6 Administrators Guide for Conversion
1.
Log into the content server as an administrator.
2. Choose Administration, Providers. The
Providers Page is displayed.
3. In the Create a New Provider section, click Add in the Action column for the
outgoing provider type. The AddEdit Outgoing Socket Provider Page
is displayed.
4.
Complete the following fields:
■
Provider Name required: a name for the refinery provider.
■
Provider Description required: a user-friendly description for the provider.
■
Provider Class required: the name of the Java class for the provider. The
default is the intradoc.provider.SocketOutgoingProvider class.
■
Connection Class: not required.
■
Configuration Class: not required.
■
Server Host Name required: The host name of the server on which the
refinery is installed.
■
HTTP Server Address: The HTTP server address for the refinery. Not
required when the refinery is on the same computer as the content server.
■
Server Port required: The port on which the refinery provider will
communicate. This entry must match the server socket port configured on the post installation configuration page during deployment of Inbound Refinery.
For information on post configuration see the Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management Suite. The default
refinery port is 5555.
■
Instance Name required: the instance name of the refinery. For example,
ref2.
■
Relative Web Root required: the relative web root of the refinery is ibr.
5. Enable the Use Connection Password check box if the refinery you are connecting
to imposes authentication for the content server the content server will share the refinery’s user base. If enabled, you must specify a user name and password to be
used and have the ProxyConnections component installed and configured on the refinery.
6. Select the Handles Inbound Refinery Conversion Jobs check box. This is
required.
7. Clear the Inbound Refinery Read Only Mode check box. Select this check box
only when you do not want the content server to send new conversion jobs to the refinery.
8.
If necessary, change the maximum number of jobs allowed in the content server’s pre-converted queue. The default is 1000 jobs.
9. Click Add. The
Providers Page is displayed, with the new refinery provider added
to the Providers table.
10.
Restart the content server.
2.1.2.3 Editing Refinery Providers
