15 Extending the Domain to Include Capture
You need to perform certain tasks in order to extend the enterprise deployment domain with Oracle WebCenter Enterprise Capture software.
- Overview of Extending the Domain to Include Capture
Oracle WebCenter Enterprise Capture provides organizations with a single system to capture both paper and electronic documents. - Extending the Domain for Capture
The instructions for extending the existing enterprise deployment domain with the Capture software are detailed in this section. - Propagating the Domain Configuration to WLS_CPT1 and WLS_CPT2
You need to perform the following steps in order to propagate the domain configuration to the Capture Managed Servers. - Configuring Oracle HTTP Server for the Capture Cluster
To enable Oracle HTTP Server to route to CPT_Cluster, which contains the WLS_CPT1 and WLS_CPT2 Managed Servers, you must set the WebLogicCluster parameter to the list of nodes in the cluster.
Parent topic: Configuring the Enterprise Deployment
Overview of Extending the Domain to Include Capture
Oracle WebCenter Enterprise Capture provides organizations with a single system to capture both paper and electronic documents.
Capture supports both centralized and distributed image capture from a user-friendly web interface capable of using high-volume, production-level scanners. Support for the industry-standard TWAIN scanning interface enables Capture to use a wide variety of industry-leading document imaging scanners to digitize paper content. Existing electronic document files can be easily captured by users or automatically captured through an importing process that can monitor an email server or network folder. Once captured, documents are organized and indexed by applying metadata through manual or automated processes that use bar code recognition technology. After documents are completed, they are committed into a content management system. Capture is fully integrated with Oracle WebCenter Content to provide organizations with one system to capture, store, manage and retrieve their mission critical business content.
Parent topic: Extending the Domain to Include Capture
Extending the Domain for Capture
The instructions for extending the existing enterprise deployment domain with the Capture software are detailed in this section.
Extending the domain involves the following tasks.
- 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 Capture
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.
To start the Configuration Wizard:
Parent topic: Extending the Domain for Capture
Navigating the Configuration Wizard Screens to Extend the Domain
Follow the instructions in the following sections to create and configure the domain for the topology with static and dynamic clusters.
Parent topic: Extending the Domain for Capture
Extending the Domain with Static Clusters
Follow the instructions in this section to create and configure the domain for the topology with static clusters.
Note:
You can use the same procedure described in this section to extend an existing domain with static clusters. 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"
-
Task 5, "Providing the GridLink Oracle RAC Database Connection Details"
-
Task 19, "Reviewing Your Configuration Specifications and Configuring the Domain"
-
Task 20, "Writing Down Your Domain Home and Administration Server URL"
- 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 Administration Server domain home you created in Creating the Initial Infrastructure Domain for an Enterprise Deployment and while extending the domain with WebCenter Content, SOA and Inbound Refinery.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.
- 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 WebCenter Enterprise Capture - 12.2.1.2.0 [wccapture]
In addition, the following additional templates should already be selected, because they were used to create the initial domain. These templates are not required to run Capture. They are already selected as part of the enterprise deployment configuration.
-
Oracle Universal Content Management - Content Server - 12.2.1.2.0 [wccontent]
-
Oracle SOA Suite - 12.2.1.2.0 [soa]
-
Oracle Universal Content Management - Inbound Refinery - 12.2.1.2.0 [wccontent]
-
Oracle Enterprise Manager - 12.2.1.2.0 [em]
-
Oracle WSM Policy Manager - 12.2.1.2.0 [oracle_common]
-
Oracle JRF - 12.2.1.2.0 [oracle_common]
-
WebLogic Coherence Cluster Extension - 12.2.1.2.0 [wlserver]
-
Tip:
More information about the options on this screen can be found in Templates in Creating WebLogic Domains Using the Configuration Wizard.
-
- Task 3 Specifying the Database Configuration Type
-
On the Database Configuration Type screen, select RCU Data.
All fields are pre-populated, because you already configured the domain to reference the Fusion Middleware schemas that are required for the Infrastructure domain.
Verify and ensure that credentials in all the fields are the same that you have provided while configuring Oracle Fusion Middleware Infrastructure.
Click Get RCU Configuration after you finish verifying the database connection information. The following output in the Connection Result Log indicates that the operating succeeded:
Connecting to the database server...OK Retrieving schema data from database server...OK Binding local schema components with retrieved data...OK Successfully Done.
Tip:
For more information about the RCU Data option, see Understanding the Service Table Schema in Creating Schemas with the Repository Creation Utility.
For more information about the other options on this screen, see Datasource Defaults in Creating WebLogic Domains Using the Configuration Wizard.
- Task 4 Specifying JDBC Component Schema Information
-
Click Convert to GridLink and click Next.
- Task 5 Providing the GridLink Oracle RAC Database Connection Details
-
On the GridLink Oracle RAC Component Schema screen, perform the following tasks.
-
Select the SCAN check box.
-
In the Host Name field, enter the Single Client Access Name (SCAN) Address for the Oracle RAC database.
-
In the SCAN Port field, enter the SCAN listening port for the database (for example, 1521).
-
In the ONS Host field, enter the SCAN address for the Oracle RAC database.
-
In the ONS Port field, enter the ONS Remote port (for example, 6200).
Click Next.
-
- Task 6 Testing the JDBC Connections
-
Click Next to continue.
- Task 7 Selecting Advanced Configuration
-
To complete domain configuration for the topology, select the following options on the Advanced Configuration screen:
-
Topology
-
File Store
-
- Task 8 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_CPT1
. -
Click Add to create a new Managed Server and name it
WLS_CPT2
.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 Capture Managed Server.
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.
Table 15-1 Values Required for Each Capture Managed Server
Server Name Listen Address Listen Port Enable SSL SSL Listen Port Server Groups WLS_CPT1
WCCHOST1
16400
No
Disabled
JRF-MAN-SVR CAPTURE-MGD-SVR
WLS_CPT2
WCCHOST2
16400
No
Disabled
JRF-MAN-SVR CAPTURE-MGD-SVR
-
- Task 9 Configuring a Cluster
-
In this task, you create a cluster of Managed Servers to which you can target the Capture software.
You will also set the Frontend Host property for the cluster, which ensures that, when necessary, WebLogic Server will redirect Web services callbacks and other redirects to
wcc.example.com
on the load balancer rather than the address in the HOST header of each request.For more information about the
wcc.example.com
virtual server address, see Configuring Virtual Hosts on the Hardware Load Balancer.Use the Clusters screen to create a new cluster:
-
Click the Add button.
-
Specify
CPT_Cluster
in the Cluster Name field. -
From the Dynamic Server Groups drop-down list, select
Unspecified
.
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 10 Assigning Server Templates
-
Click Next to proceed to the next screen.
- Task 11 Configuring Dynamic Servers
-
Verify that all dynamic server options are disabled for clusters that are to remain as static clusters.
-
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.
-
- Task 12 Assigning Managed Servers to the Cluster
-
Use the Assign Servers to Clusters screen to assign
WLS_CPT1
andWLS_CPT2
to the new cluster,CPT_Cluster
:-
In the Clusters pane, select the cluster to which you want to assign the servers; in this case,
CPT_Cluster
. -
In the Servers pane, assign
WLS_CPT1
toCPT_Cluster
by doing one of the following:-
Click the
WLS_CPT1
Managed Server once to select it, then click on the right arrow to move it beneath the selected cluster in the Clusters pane. -
Double-click
WLS_CPT1
to move it beneath the selected cluster in the clusters pane.
-
-
Repeat to assign
WLS_CPT2
toCPT_Cluster
.
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.
-
- Task 13 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
0
, as it was defined during the initial Infrastructure domain creation. Oracle Enterprise Capture does not use Coherence Clusters. This step is a part of the domain extension process.Note:
For Coherence licensing information, refer to Oracle Coherence in Oracle Fusion Middleware Licensing Information.
- Task 14 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 15 Assigning Servers to Machines
-
Use the Assign Servers to Machines screen to assign the Capture Managed Servers you just created to the corresponding machines in the domain.
Assign
WLS_CPT1
toWCCHOST1
, and assignWLS_CPT2
toWCCHOST2
.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.
- Task 16 Virtual Targets
-
Click Next to proceed to the next screen.
- Task 17 Partitions
-
Click Next to proceed to the next screen.
- Task 18 Configuring the JMS File Store
-
In the JMS File Stores screen, assign the following directory for each of the WCC Persistence stores including UMS and BPM file stores:
ORACLE_RUNTIME/CPT_Cluster/jms
In this example, replace ASERVER_HOME with the value of the variable for you environment. Replace CPT_Cluster with the name you assigned to the Capture cluster.
- Task 19 Reviewing Your Configuration Specifications and Configuring the Domain
-
The Configuration Summary screen contains the detailed configuration information for the domain you are about to create. 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.
- Task 20 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 21 Start the Administration Server
-
Start the Administration Server to ensure the changes you have made to the domain have been applied.
After you have completed extending the domain with static clusters, go to Propagating the Domain Configuration to WLS_CPT1 and WLS_CPT2.
Extending the Domain with Dynamic Clusters
Follow the instructions in this section to create and configure the domain for the topology with dynamic clusters.
Note:
You can use the same procedure described in this section to extend an existing domain with Dynamic Clusters. 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"
-
Task 5, "Providing the GridLink Oracle RAC Database Connection Details"
-
Task 19, "Reviewing Your Configuration Specifications and Configuring the Domain"
-
Task 20, "Writing Down Your Domain Home and Administration Server URL"
- 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 Administration Server domain home you created in Creating the Initial Infrastructure Domain for an Enterprise Deployment and while extending the domain with WebCenter Content, SOA and Inbound Refinery.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.
- 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 WebCenter Enterprise Capture - 12.2.1.3.0 [wccapture]
In addition, the following additional templates should already be selected, because they were used to create the initial domain. These templates are not required to run Capture. They are already selected as part of the enterprise deployment configuration.
-
Oracle Universal Content Mnagement - Content Server - 12.2.1.3.0 [wccontent]
-
Oracle SOA Suite - 12.2.1.3.0 [soa]
-
Oracle Universal Content Management - Inbound Refinery - 12.2.1.3.0 [wccontent]
-
Oracle Enterprise Manager - 12.2.1.3.0 [em]
-
Oracle WSM Policy Manager - 12.2.1.3.0 [oracle_common]
-
Oracle JRF - 12.2.1.3.0 [oracle_common]
-
WebLogic Coherence Cluster Extension - 12.2.1.3.0 [wlserver]
-
Tip:
More information about the options on this screen can be found in Templates in Creating WebLogic Domains Using the Configuration Wizard.
-
- Task 3 Specifying the Database Configuration Type
-
On the Database Configuration Type screen, select RCU Data.
All fields are pre-populated, because you already configured the domain to reference the Fusion Middleware schemas that are required for the Infrastructure domain.
Verify and ensure that credentials in all the fields are the same that you have provided while configuring Oracle Fusion Middleware Infrastructure.
Click Get RCU Configuration after you finish verifying the database connection information. The following output in the Connection Result Log indicates that the operating succeeded:
Connecting to the database server...OK Retrieving schema data from database server...OK Binding local schema components with retrieved data...OK Successfully Done.
Tip:
For more information about the RCU Data option, see "Understanding the Service Table Schema" in Creating Schemas with the Repository Creation Utility.
For more information about the other options on this screen, see "Datasource Defaults" in Creating WebLogic Domains Using the Configuration Wizard.
- Task 4 Specifying JDBC Component Schema Information
-
Click Convert to GridLink and click Next.
- Task 5 Providing the GridLink Oracle RAC Database Connection Details
-
On the GridLink Oracle RAC Component Schema screen, perform the following tasks.
-
Select the SCAN check box.
-
In the Host Name field, enter the Single Client Access Name (SCAN) Address for the Oracle RAC database.
-
In the SCAN Port field, enter the SCAN listening port for the database (for example, 1521).
-
In the ONS Host field, enter the SCAN address for the Oracle RAC database.
-
In the ONS Port field, enter the ONS Remote port (for example, 6200).
Click Next.
-
- Task 6 Testing the JDBC Connections
-
Click Next to continue.
- Task 7 Selecting Advanced Configuration
-
To complete domain configuration for the topology, select the following options on the Advanced Configuration screen:
-
Topology
-
File Store
-
- Task 8 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:
-
Delete the default Managed Server.
-
Click Next to proceed to the next screen.
-
- Task 9 Configuring a Cluster
-
In this task, you create a cluster of Managed Servers to which you can target the Capture software.
You will also set the Frontend Host property for the cluster, which ensures that, when necessary, WebLogic Server will redirect Web services callbacks and other redirects to
wcc.example.com
on the load balancer rather than the address in the HOST header of each request.For more information about the
wcc.example.com
virtual server address, see Configuring Virtual Hosts on the Hardware Load Balancer.Use the Clusters screen to create a new cluster:
-
Click the Add button.
-
Specify
CPT_Cluster
in the Cluster Name field. -
From the Dynamic Server Groups drop-down list, select ODDC-DYN-CLUSTER.
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 10 Assigning Server Templates
-
Use the Server Templates screen to add a template:
-
Specify
CPT-server-template
in the Name field. -
Specify
16400
in the Listen Port field. -
Leave the Enable SSL option unchecked.
-
From the Cluster drop-down list, select
CPT_Cluster
. -
Click Next to proceed to the next screen.
-
- Task 11 Configuring Dynamic Servers
-
Use the Dynamic Clusters screen to configure the required clusters:
-
Specify
CPT_Cluster
in the Cluster Name field. -
Specify
WLS_CPT
in the Server Name Prefix field. -
From the Server Template drop-down list, select
CPT-server-template
. -
Specify
2
in the Maximum Dynamic Server Count field. -
Specify WCCHOST* in the Machine Name Match Expression field.
-
Select the Calculated Machine Names and Dynamic Cluster fields.
-
Select the Calculated Listen Ports field.
-
Click Next to proceed to the next screen.
-
- Task 12 Assigning Managed Servers to the Cluster
-
Click Next to proceed to the next screen.
- Task 13 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
0
, as it was defined during the initial Infrastructure domain creation. Oracle Enterprise Capture does not use Coherence Clusters. This step is a part of the domain extension process.Note:
For Coherence licensing information, refer to Oracle Coherence in Oracle Fusion Middleware Licensing Information.
- Task 14 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 to the next screen.
- Task 15 Assigning Servers to Machines
-
Click Next to proceed to the next screen.
- Task 16 Virtual Targets
-
Click Next to proceed to the next screen.
- Task 17 Partitions
-
Click Next to proceed to the next screen.
- Task 18 Configuring the File Stores
-
In the JMS File Stores screen, assign the following directory for each of the WCC Persistence stores including UMS and BPM file stores:
ORACLE_RUNTIME/CPT_Cluster/jms
In this example, replace ASERVER_HOME with the value of the variable for you environment. Replace CPT_Cluster with the name you assigned to the Capture cluster.
- Task 19 Reviewing Your Configuration Specifications and Configuring the Domain
-
The Configuration Summary screen contains the detailed configuration information for the domain you are about to create. 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.
- Task 20 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 21 Start the Administration Server
-
Start the Administration Server to ensure the changes you have made to the domain have been applied.
Propagating the Domain Configuration to WLS_CPT1 and WLS_CPT2
You need to perform the following steps in order to propagate the domain configuration to the Capture Managed Servers.
Parent topic: Extending the Domain to Include Capture
Configuring Oracle HTTP Server for the Capture Cluster
To enable Oracle HTTP Server to route to CPT_Cluster, which contains the WLS_CPT1 and WLS_CPT2 Managed Servers, you must set the WebLogicCluster parameter to the list of nodes in the cluster.
- Configuring Oracle HTTP Server for the WLS_CPT Managed Servers
- Setting the Front-End HTTP Host and Port for the Capture Cluster
- Validating Access Through the Load Balancer
Parent topic: Extending the Domain to Include Capture
Configuring Oracle HTTP Server for the WLS_CPT Managed Servers
Parent topic: Configuring Oracle HTTP Server for the Capture Cluster
Setting the Front-End HTTP Host and Port for the Capture Cluster
Parent topic: Configuring Oracle HTTP Server for the Capture Cluster
Validating Access Through the Load Balancer
- While WLS_CPT2 is running, stop WLS_CPT1 from the WebLogic Server Administration Console.
- Access
https://wcc.example.com/dc-console
to verify that it is functioning properly. (You will not be able to retrieve reports or data because the Capture server is down.) - Start WLS_CPT1 from the WebLogic Server Administration Console.
- Stop WLS_CPT2 from the WebLogic Server Administration Console.
- Access
https://wcc.example.com/dc-console
to verify that it is functioning properly. - Start WLS_CPT2 from the WebLogic Server Administration Console.
Parent topic: Configuring Oracle HTTP Server for the Capture Cluster