1. Installing and Configuring Oracle WebCenter Content
  2. Configuring WebCenter Content Domain

4 Configuring WebCenter Content Domain

After you have installed WebCenter Content, you can configure the domain, which you can also extend for high availability.

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

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

  • Creating the Database Schemas
    Before you can configure an Oracle WebCenter Content domain, you must install required schemas on a certified database for use with this release of Oracle Fusion Middleware.
  • Configuring the Domain
    Use the Configuration Wizard to create and configure a domain.
  • Starting the Servers
    After configuration is complete, start Node Manager, then the WebLogic Administration Server and Managed Servers.
  • Verifying the Configuration
    After completing all configuration steps, you can perform additional steps to verify that your domain is properly configured.
  • Configuring Inbound Refinery Settings (Single Node)
    After you start the Inbound Refinery Managed Servers, configure the settings on the post-installation configuration screen. In most cases, you can accept the default settings.
  • Configuring WebCenter Content Settings
    You must complete the WebCenter Content configuration on the post-installation configuration page in Content Server.

Creating the Database Schemas

Before you can configure an Oracle WebCenter Content domain, you must install required schemas on a certified database for use with this release of Oracle Fusion Middleware.

Parent topic: Configuring WebCenter Content Domain

Installing and Configuring a Certified Database

Before you create the database schemas, you must install and configure a certified database, and verify that the database is up and running.

Note:

For an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), you must modify the wallet settings and set the environment variables, and apply patches on ORACLE HOME. For more information, see Settings to connect to Autonomous Transaction Processing Database and Applying Patches on ORACLE HOME.

See About Database Requirements for an Oracle Fusion Middleware Installation.

Parent topic: Creating the Database Schemas

Starting the Repository Creation Utility

Start the Repository Creation Utility (RCU) after you verify that a certified JDK is installed 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 is 1.8.0_211 and later.
  2. Ensure that the JAVA_HOME environment variable is set to the location of the certified 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

Parent topic: Creating the Database Schemas

Navigating the Repository Creation Utility Screens to Create Schemas

Enter required information in the RCU screens to create the database schemas.

Parent topic: Creating the Database Schemas

Introducing the RCU

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

Click Next.

Selecting a Method of Schema Creation

Use the Create Repository screen to select a method to create and load component schemas into the database.

On the Create Repository screen:

  • If you have the necessary permissions and privileges to perform DBA activities on your database, select System Load and Product Load. This procedure assumes that you have SYSDBA privileges.

  • If you do not have the necessary permissions or privileges to perform DBA activities in the database, you must select Prepare Scripts for System Load on this screen. This option generates a SQL script that you can give to your database administrator. See About System Load and Product Load in Oracle Fusion Middleware Creating Schemas with the Repository Creation Utility.

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

    Note:

    For an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), you must create schemas as a Normal user, and though, you do not have full SYS or SYSDBA privileges on the database, you must select System Load and Product Load.

Providing Database Connection Details

On the Database Connection Details screen, provide the database connection details for the RCU to connect to your database.

Note:

If you are unsure of the database service name, you can obtain it from the SERVICE_NAMES parameter in the initialization parameter file of the database. If the initialization parameter file does not contain the SERVICE_NAMES parameter, then the service name is the same as the global database name, which is specified in the DB_NAME and DB_DOMAIN parameters.

For an Oracle Autonomous Transaction Processing-Shared (ATP-S) database, use the database service name, <databasename>_tpurgent or <databasename>_tp, specified in tnsnames.ora. For service name details, see Database Service Names for Autonomous Transaction Processing and Autonomous JSON Database in Using Oracle Autonomous Database on Shared Exadata Infrastructure.

To create schemas on an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), you can specify the connection credentials using only the Connection String option. In this screen, a warning message is displayed. You can ignore the warning and continue with the schema creation. For more information, see SYS DBA Privileges Warning After Applying Patches.

To provide the database connection details:

  1. On the Database Connection Details screen, provide the database connection details.

    For example:

    • Database Type: Oracle Database
    • Connection String Format: Connection Parameters or Connection String
    • Connection String: examplehost.exampledomain.com:1521:Orcl.exampledomain.com
    • Host Name: examplehost.exampledomain.com
    • Port: 1521
    • Service Name: Orcl.exampledomain.com
    • User Name: sys
    • Password: ******
    • Role: SYSDBA

    For an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), enter connect string in the following format:

    jdbc:oracle:thin:@TNS_alias?TNS_ADMIN=<path of the wallet files, ojdbc.properties, and tnsnames.ora>

    In the connect string, you must pass TNS_alias as the database name found in tnsnames.ora, and TNS_ADMIN property to the location of the wallet files, ojdbc.properties, and tnsnames.ora.

    Note:

    For an Oracle Autonomous Transaction Processing-Shared (ATP-S) database, you must use only one of the database service names, <databasename>_tpurgent or <databasename>_tp, specified in tnsnames.ora. For database service name details, see Database Service Names for Autonomous Transaction Processing and Autonomous JSON Database in Using Oracle Autonomous Database on Shared Exadata Infrastructure.

    Example connect string for Oracle Autonomous Transaction Processing-Dedicated (ATP-D) database::

    jdbc:oracle:thin:@dbname_medium?TNS_ADMIN=/users/test/wallet_dbname/

    Example connect string for Oracle Autonomous Transaction Processing-Shared (ATP-S) database:

    jdbc:oracle:thin:@dbname_tp?TNS_ADMIN=/users/test/wallet_dbname/

  2. Click Next to proceed, then click OK in the dialog window that confirms a successful database connection.
Specifying a Custom Prefix and Selecting Schemas

You must enter a custom prefix to group schemas together, then select schemas you need. You can select the required schema on the Select Components screen.

Select Create new prefix, specify a custom prefix, then select the WebCenter Content schema. This action automatically selects the following schemas as dependencies:

  • Oracle WebCenter Content Server - Complete

  • Oracle WebCenter Enterprise Capture

  • Oracle WebCenter Content Server - Search Only

  • Oracle WebCenter Content: Imaging

The following schemas are selected by default:

  • Metadata Services

  • Oracle Platform Security Services

  • Audit Services

  • Audit Services Append

  • Audit Services Viewer

Tip:

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

Note:

If you install WebCenter Content only and select the Oracle WebCenter Content Server - Complete schema (but no other schemas), you must select the Metadata Services schema. You must select Metadata Services because WebCenter Content User Interface requires it.

To create schemas for Imaging, select Oracle WebCenter Content: Imaging, and also select Oracle WebCenter Content Server - Complete to use WebCenter Content as the Imaging repository.

For Oracle Web Services Manager (Oracle WSM) Policy Manager, or for using Imaging with Oracle SOA Suite, expand AS Common Schemas and select Metadata Services.

The schema Common Infrastructure Services is also created automatically. It enables you to retrieve information from RCU during domain configuration. This schema is grayed out; you cannot select or deselect it. For more details, see Understanding the Service Table Schema in Oracle Fusion Middleware Creating Schemas with the Repository Creation Utility.

The custom prefix logically groups these schemas together for use in this domain only; you must create a unique set of schemas for each domain because schema sharing across domains is not supported.

Tip:

For more details about custom prefixes, see Understanding Custom Prefixes in Oracle Fusion Middleware Creating Schemas with the Repository Creation Utility.

To organize your schemas in a multi-domain environment, see Planning Your Schema Creation in Oracle Fusion Middleware Creating Schemas with the Repository Creation Utility.

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

Specifying Schema Passwords

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

Note:

For an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), the schema password must be minimum 12 characters, and must contain at least one uppercase, one lower case, and one number.

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

Click Next.

Completing Schema Creation

Navigate through the remaining RCU screens to complete schema creation.

On the Map Tablespaces screen, the Encrypt Tablespace check box appears only if you enabled Transparent Data Encryption (TDE) in the database (Oracle or Oracle EBR) when you start the RCU.

To complete schema creation:
  1. On the Map Tablespaces screen, select Encrypt Tablespace if you want to encrypt all new tablespaces that the RCU creates.
  2. In the Completion Summary screen, click Close to dismiss the RCU.

    For an Oracle Autonomous Transaction Processing-Shared (ATP-S) database, in the Map Tablespaces screen you must override the default tablespaces and the temporary tablespaces, and also override the additional tablespaces, if applicable. See Map Tablespaces.

    If you encounter any issues when you create schemas on an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), see Troubleshooting Tips for Schema Creation on an Autonomous Transaction Processing Database in Creating Schemas with the Repository Creation Utility and Issues Related to Product Installation and Configuration on an Autonomous Database in Release Notes for Oracle Fusion Middleware Infrastructure.

Configuring the Domain

Use 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 Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Parent topic: Configuring WebCenter Content Domain

Starting the Configuration Wizard

Start the Configuration Wizard to begin configuring a domain.

To start the Configuration Wizard:

  1. Change to the following directory:

    (UNIX) ORACLE_HOME/oracle_common/common/bin

    (Windows) ORACLE_HOME\oracle_common\common\bin

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

  2. Enter the following command:

    (UNIX) ./config.sh

    (Windows) config.cmd

Parent topic: Configuring the Domain

Navigating the Configuration Wizard Screens to Create and Configure the Domain

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

Note:

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

Parent topic: Configuring the Domain

Selecting the Domain Type and Domain Home Location

Use 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 the directory structure in What Are the Key Oracle Fusion Middleware Directories? in Oracle Fusion Middleware Understanding Oracle Fusion Middleware, where the Domain home is located outside the Oracle home directory. This directory structure helps avoid issues when you need to 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 Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Selecting Configuration Templates for Oracle WebCenter Content

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

  • Oracle Universal Content Management - Inbound Refinery - 12.2.1.4.0[wccontent]

  • Oracle Universal Content Management - Content Server - 12.2.1.4.0 [wccontent]

    Selecting this template automatically selects the following as dependencies:

    • Oracle Enterprise Manager - 12.2.1.4.0 [em]

    • Oracle JRF - 12.2.1.4.0 [oracle_common]

    • WebLogic Coherence Cluster Extension - 12.2.1.4.0 [wlserver]

  • Oracle WebCenter Enterprise Capture - 12.2.1.4.0 [wccapture]

  • Oracle WebCenter Content - Web UI - 12.2.1.4.0 [wccontent]

  • Oracle WebCenter Content: Imaging

Tip:

For more details about options on this screen, see Templates in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Configuring High Availability Options

Use this screen to configure service migration and persistence settings that affect high availability. This screen appears for the first time when you create a cluster that uses automatic service migration, persistent stores, or both, and all subsequent clusters that are added to the domain by using the Configuration Wizard, automatically apply the selected HA options.

Enable Automatic Service Migration

Select Enable Automatic Service Migration to enable pinned services to migrate automatically to a healthy Managed Server for failover. It configures migratable target definitions 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 System Resource for leasing. Requires that the Automatic Migration data source have a valid JDBC System Resource. If you select this option, the Migration Basis is configured to Database and the Data Source for Automatic Migration is also automatically configured by the Configuration Wizard. If you have a high availability database, such as Oracle RAC, to manage leasing information, configure the database for server migration according to steps in High-availability Database Leasing.

  • Consensus Leasing - Managed Servers maintain leasing information in-memory. You use Node Manager to control Managed Servers in a cluster. (All servers that are migratable, or which could host a migratable target, must have a Node Manager associated with them.) If you select this option, the Migration Basis is configured 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 servers in the default file store.

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

Oracle recommends that you select JDBC TLog Store. When you complete the configuration, you have a cluster where JDBC persistent stores are set up for Transaction logs.

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

JMS Service Persistence

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

  • JMS File Store - Configures a component to use JMS File Stores. If you select this option, you can choose the File Store option in the Advanced Configuration Screen to change the settings, if required. In the File Stores screen, you can set file store names, directories, and synchronous write policies.

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

Selecting the Application Home Location

Use the Application Location screen to select the location to store applications associated with your domain, also known as the Application home directory.

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

For more about the Application home directory, see About the Application Home Directory.

For more information about this screen, see Application Location in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Configuring the Administrator Account

Use the Administrator Account screen to specify the user name and password for the default WebLogic Administrator account for the domain.

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

Specifying the Domain Mode and JDK

Use the Domain Mode and JDK screen to specify the domain mode and Java Development 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 Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.
Specifying JDBC Data Sources

Use this screen to specify JDBC Data Sources.

If you use a DB2 database, you must check system requirements before you select a DB2 driver. See the document Oracle Fusion Middleware System Requirements and Specifications.
  1. Select the default Data Source, mds-WCCUIMDSREPO.
  2. Enter values for DBMS/Service, Host Name, Port and Password and Username.

    Note:

    For an Autonomous Transaction Processing database, (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), specify the connection credentials using only the Connection URL String option, and enter the connect string in the following format:

    jdbc:oracle:thin:@TNS_alias?TNS_ADMIN=<path of the wallet files, ojdbc.properties, and tnsnames.ora>

    In the connect string, you must pass TNS_alias as the database name found in tnsnames.ora, and TNS_ADMIN property to the location of the wallet files, ojdbc.properties, and tnsnames.ora.

    Example connect string for Oracle Autonomous Transaction Processing-Dedicated (ATP-D) database:

    jdbc:oracle:thin:@dbname_medium?TNS_ADMIN=/users/test/wallet_dbname/

    Example connect string for Oracle Autonomous Transaction Processing-Shared (ATP-S) database:

    jdbc:oracle:thin:@dbname_tp?TNS_ADMIN=/users/test/wallet_dbname/

  3. Click Next.
Testing the JDBC Data Source

Use this screen to test the data source connections you configured in the previous screens.

Note:

To test database connections, the database you are connecting to must be running. If you don’t want to test the connections at this time, do not select any data sources and click Next to continue.

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

To test the data source:
  1. Select the check box next to the data source you want to test.
  2. Select Test Selected Connections.
  3. If the test is successful, then click Next. If it fails, click Back, correct the details and retest it.
Specifying the Database Configuration Type

Use the Database Configuration type screen to specify details about the database and database schema.

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

Note:

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

For an Autonomous Transaction Processing database, (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), you must select only the RCU Data option.

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 a service 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

Schema Owner

Schema Password

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

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

For an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), specify the connection credentials using only the Connection URL String option, and enter the connect string in the following format:

jdbc:oracle:thin:@TNS_alias?TNS_ADMIN=<path of the wallet files, ojdbc.properties, and tnsnames.ora>

In the connect string, you must pass TNS_alias as the database name found in tnsnames.ora, and TNS_ADMIN property to the location of the wallet files, ojdbc.properties, and tnsnames.ora.

Example connect string for Oracle Autonomous Transaction Processing-Dedicated (ATP-D) database:

jdbc:oracle:thin:@dbname_medium?TNS_ADMIN=/users/test/wallet_dbname/

Example connect string for Oracle Autonomous Transaction Processing-Shared (ATP-S) database:

jdbc:oracle:thin:@dbname_tp?TNS_ADMIN=/users/test/wallet_dbname/

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

Connecting to the database server...OK
Retrieving schema data from database server...OK
Binding local schema components with retrieved data...OK

Successfully Done.

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

See Database Configuration Type in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard .

Specifying JDBC Component Schema Information

Use the JDBC Component Schema screen to verify or specify details about the database schemas.

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

For an Autonomous Transaction Processing database (both Oracle Autonomous Transaction Processing-Dedicated (ATP-D) and Oracle Autonomous Transaction Processing-Shared (ATP-S)), specify the connection credentials using only the Connection URL String option, and enter the connect string in the following format: 

jdbc:oracle:thin:@TNS_alias?TNS_ADMIN=<path of the wallet files, ojdbc.properties, and tnsnames.ora>

In the connect string, you must pass TNS_alias as the database service name found in tnsnames.ora, and TNS_ADMIN property to the location of the wallet files, ojdbc.properties, and tnsnames.ora.

Example connect string for Oracle Autonomous Transaction Processing-Dedicated (ATP-D) database:

jdbc:oracle:thin:@dbname_medium?TNS_ADMIN=/users/test/wallet_dbname/

Example connect string for Oracle Autonomous Transaction Processing-Shared (ATP-S) database:

jdbc:oracle:thin:@dbname_medium?TNS_ADMIN=/users/test/wallet_dbname/

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

See JDBC Component Schema in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard for more details about this screen.

Testing the JDBC Connections

Use 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 encounter any 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 you specified while creating your schemas. If you want different passwords for different schema components, manually edit them in the previous screen (JDBC Component Schema) by entering the password you want in the Schema Password column, against each row. After specifying the passwords, select the check box corresponding to the schemas that you changed the password in and test the connection again.

For more information about this screen, see JDBC Component Schema Test in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Entering Credentials

Use the Credentials screen to set credentials for each key in the domain.

The Store Name column shows the credential store associated with each key.
(Optional) You can click Add to enter additional key credentials.
  1. Enter the User Name to use for the key.
  2. Enter the Password to use for the key.
  3. Select Next.
Selecting Advanced Configuration

Use 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 WebCenter Content Managed Server.

Optionally, select other available options as required for your desired installation environment. The steps in this guide describe a standard installation topology, but you may choose to follow a different path. If your installation requirements extend to additional options outside the scope of this guide, you may be presented with additional screens to configure those options. For information about all Configuration Wizard screens, see Configuration Wizard Screens in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Configuring the Administration Server Listen Address

Use 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 host where the Administration Server will reside, or use the system name or DNS name that maps to a single IP address. Do not use All Local Addresses.

Do not specify any server groups for the Administration Server.

Note:

Use the Mozilla Firefox browser to access Internet Protocol Version 6 (IPv6) URLs. You must enter the Global IPv6 address to create a domain and access URLs. (You should not use the local IPv6 address.)
Configuring Node Manager

Use the Node Manager screen to select the type of Node Manager you want to configure, along with the Node Manager credentials.

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

For more information about this screen, see Node Manager in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

For more about Node Manager types, see Node Manager Overview in Oracle Fusion Middleware Administering Node Manager for Oracle WebLogic Server.

Configuring Managed Servers for Oracle WebCenter Content

You create and configure new Managed Servers on the Managed Servers Screen.

You create two Managed Servers for each component, with the exception of Inbound Refinery.
  1. In the Listen Address drop-down list, select the IP address of the host on that the Managed Servers will reside on or use the system name or DNS name that maps to a single IP address. Do not use All Local Addresses.
  2. Select Enable SSL to enable an SSL (https) connection for WebCenter Content and WebCenter Content User Interface. Revise the SSL Listen Port value as needed.
  3. Leave the Server Groups settings as they appear; the Configuration Wizard assigns the correct server group automatically. A server group ensures that the correct services target Managed Servers you are creating.

    Server groups target Fusion Middleware applications and services to one or more servers by mapping defined application service groups to each defined server group. You can map a given application service group to multiple server groups if needed. Any application services that map to a certain server group are automatically targeted to all servers assigned to that group. For more information about server groups, see Application Service Groups, Server Groups, and Application Service Mappings in Oracle Fusion Middleware Domain Template Reference.

  4. Click Add and repeat this process to create a second Managed Server for each component except for Inbound Refinery. For example, cpt_server_2.

    You must configure a second Managed Server to configure the standard topology for high availability. If you are not creating a highly available environment, then this step is optional.

    For more about the high availability standard topology, see Understanding the Fusion Middleware Standard HA Topology in Oracle Fusion Middleware High Availability Guide.

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

Examples and procedures in the rest of this document refer to these server names; if you choose different names be sure to replace them as needed.

Tip:

For more about options on this screen, see Managed Servers in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Configuring a Cluster for WebCenter Content

Use the Clusters screen to create a new cluster.

On the Clusters screen:

  1. Click Add.
  2. Specify wcc_cluster_1 in the Cluster Name field.
  3. Leave the Cluster Address field blank.

Repeat the preceding steps to create three more clusters: cpt_cluster_1, ibr_cluster_1, and wccui_cluster_1.

By default, server instances in a cluster communicate with one another using unicast. If you want to change your cluster communications to use multicast, see Considerations for Choosing Unicast or Multicast in Oracle Fusion Middleware Administering Clusters for Oracle WebLogic Server.

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

For more information about this screen, see Clusters in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Defining Server Templates

If you are creating dynamic clusters for a high availability setup, use the Server Templates 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 Dynamic Clusters in Oracle Fusion Middleware High Availability Guide.

Configuring Dynamic Servers

If you are creating dynamic clusters for a high availability setup, use the Dynamic Servers screen to configure the dynamic servers.

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

Note:

When you create dynamic clusters, keep in mind that after you assign the Machine Name Match Expression, you do not need to create machines for your dynamic cluster.

To create a dynamic cluster for a high availability setup, see Using Dynamic Clusters in Oracle Fusion Middleware High Availability Guide.

Assigning WebCenter Content Managed Servers to the Cluster

Use the Assign Servers to Clusters screen to assign Managed Servers to a new configured cluster. A configured cluster is a cluster you configure manually. You do not use this screen if you are configuring a dynamic cluster, a cluster that contains one or more generated server instances that are based on a server template.

For more on configured cluster and dynamic cluster terms, see About Dynamic Clusters in Oracle Fusion Middleware 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 Managed Servers; in this case, wcc_cluster_1.
  2. In the Servers pane, assign wcc_server_1 to wcc_cluster_1 by doing one of the following:

    • Click once on wcc_server_1 to select it, then click the right arrow to move it beneath the selected cluster (wcc_cluster_1) in the Clusters pane.

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

  3. Repeat to assign wcc_server_2 to wcc_cluster_1.
The following image shows a generic example of the Clusters pane after Managed Servers are assigned to clusters.

For more information about this screen, see Assign Servers to Clusters in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Configuring Coherence Clusters

Use 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 Server port numbers. The offset is 5000, meaning the maximum allowed value that you 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.

For Coherence licensing information, see Oracle Coherence Products in Licensing Information.

Creating a New WebCenter Content Machine

Use the Machines screen to create new machines in the domain. A machine is required so that Node Manager can start and stop servers.

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

To create a new WebCenter Content machine so that Node Manager can start and stop servers:
  1. Select the Machine tab (for Windows) or the UNIX Machine tab (for UNIX), then click Add to create a new machine.
  2. In the Name field, specify a machine name, such as wcc_machine_1.
  3. In the Node Manager Listen Address field, select the IP address of the machine in which the Managed Servers are being configured.

    You must select a specific interface and not localhost. This allows Coherence cluster 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 any existing machine. It is not necessary to create a new machine unless your situation requires it.

For more information about this screen, see Machines in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Assigning Servers to WebCenter Content Machines

Use the Assign Servers to Machines screen to assign the Administration Server and Managed 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, wcc_machine_1.
  2. In the Servers pane, assign AdminServer to wcc_machine_1 by doing one of the following:

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

    • Double-click on AdminServer to move it beneath the selected machine (wcc_machine_1) 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 Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Virtual Targets

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

For details about this screen, see Virtual Targets in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Note:

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

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

For details about options on this screen, see Partitions in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Note:

WebLogic Server Multitenant domain partitions are deprecated in WebLogic Server 12.2.1.4.0 and will be removed in the next release.
Reviewing Your Configuration Specifications and Configuring the Domain

The Configuration Summary screen shows detailed configuration information for the domain you are about to create.

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

For more details about options on this screen, see Configuration Summary in Oracle Fusion Middleware Creating WebLogic Domains Using the Configuration Wizard.

Writing Down Your Domain Home and Administration Server URL

The End of Configuration screen shows information about the domain you just configured.

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

  • Domain Location

  • Administration Server URL

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

Click Finish to dismiss the Configuration Wizard.

Starting the Servers

After configuration is complete, start Node Manager, then the WebLogic Administration Server and Managed Servers.

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

Parent topic: Configuring WebCenter Content Domain

Starting Node Manager

To start the per-domain Node Manager:

  1. Change to the following directory:

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

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

  2. Enter the following command:

    • (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 log files.

    • (Windows) startNodeManager.cmd

      Note:

      On Windows operating systems, Oracle recommends that you configure Node Manager to run as a startup service. This allows Node Manager to start up automatically each time the system is restarted.

      See Running Node Manager as a Startup Service in Oracle Fusion Middleware Administering Node Manager for Oracle WebLogic Server.

Parent topic: Starting the Servers

Starting the Administration Server

To start the Administration Server:

  1. Go to the DOMAIN_HOME/bin directory.

  2. Enter the following command:

    • (UNIX)

      ./startWebLogic.sh

    • (Windows)

      startWebLogic.cmd

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

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

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

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

Note:

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

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

Parent topic: Starting the Servers

Starting the Managed Servers

To 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 of Configuration screen (Writing Down Your Domain Home and Administration Server URL). 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 domain and displays their status (such as Running or Shutdown). For a newly configured domain, only the AdminServer(admin) will be running.

    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.

Parent topic: Starting the Servers

Oracle WebCenter Content Managed Server Locations (URLs)

After you start the Managed Servers, use this topic to refer to Oracle WebCenter Content Managed Server locations.

Server URL

WebCenter Content

http://hostname:wcc-server-port/cs

Example: http://host1:16200/cs

WebCenter Content User Interface

http://hostname:wccui-server-port/wcc

Example: http://host1:16225/wcc

Inbound Refinery

http://hostname:ibr-server-port/ibr

Example: http://host1:16250/ibr

Capture

http://hostname:cpt-server-port/

Example: http://host1:7004/cpt

WebCenter Content: Imaging

http://hostname:imaging-server-port/imaging

Example: http://host1:16000/imaging

Parent topic: Starting the Servers

Verifying the Configuration

After completing all configuration steps, you can perform additional steps to verify that your domain is properly configured.

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

Parent topic: Configuring WebCenter Content Domain

Configuring Inbound Refinery Settings (Single Node)

After you start the Inbound Refinery Managed Servers, configure the settings on the post-installation configuration screen. In most cases, you can accept the default settings.

To configure the settings:
  1. Access the Inbound Refinery post-installation configuration screen at the following URL:
    http://managedServerHost:managedServerPort/ibr/
  2. Review the settings. See Inbound Refinery Configuration Page for a description of each field.
  3. Click Submit.
  4. Restart the Inbound Refinery Managed Server, using the WebLogic Server Administration Console.

Parent topic: Configuring WebCenter Content Domain

Inbound Refinery Configuration Page

Use descriptions of Inbound Refinery configuration page fields as you complete configuration steps in Configuring Inbound Refinery Settings (Single Node).

The following table describes Inbound Refinery configuration page fields.

Field Description
Inbound Refinery Instance Folder Absolute path to the Oracle instance directory of Inbound Refinery. Default is DomainHome/ucm/ The default Oracle instance directory forInbound Refinery is ORACLE_HOME/user_projects/domains/DomainHome/ucm/ibr The top-level folder in the folder hierarchy for the Content Server instance is ibr.

The path to the Oracle instance directory is the value of the IntradocDir variable for the Inbound Refinery instance. Oracle recommends that you make this directory path unique to this Managed Server, or node. For installations that you will probably upgrade, Oracle strongly recommends that you change the location of the Oracle instance directory to a directory outside any Oracle WebLogic Server domain directories or installation directories.

Native File Repository Location Directory that stores conversion jobs during their processing. After a job converts and Content Server picks it up, it is removed from this directory. You do not need to change this path.
Weblayout Folder URL for the Inbound Refinery web interface. You do not need to change this path.
Register Start Menu Actions Whether or not to register Start Menu actions.
Server Socket Port Number of the port to call top-level services.

To set up a provider from Inbound Refinery back to Content Server, you can leave the default

Server Socket Port value 5555 or change it to an unused port number.

Changing this field value also changes the IntradocServerPort entry in ORACLE_HOME/user_projects/domains/DomainHome/ucm/ibr/config/config.cfg

Note:

You must set Server Socket Port correctly to useInbound Refinery.

Note:

The default port number for Node Manager and Inbound Refinery is 5555. If both run on the same server, you must configure a different port number for Node Manager or Inbound Refinery.
Incoming Socket Connection Address Security Filter

Restricts Inbound Refinery access to a computer or computers with a specified IP address or addresses.

To enable access from Content Server, enter a value for this field. For example:

127.0.0.1|0:0:0:0:0:0:0:1|your.server.IP.address

This value should be the Content Server instance IP address of the or instances that will send jobs to Inbound Refinery, not the IP address of Inbound Refinery. (In a test or demo environment, these IP addresses could be the same.)

This field accepts wildcards such as 10.*.*.*. You can change this value by setting SocketHostAddressSecurityFilter in DomainHome/ucm/ibr/config/config.cfg and restarting Inbound Refinery.

Note:

To use Inbound Refinery, you must set the Incoming Socket Connection Address Security Filter value correctly.
Web Server HTTP/HTTPS Address The name of the web server. (HttpServerAddress property).
WebAddress Is HTTPS Whether or not the URL for the web server starts with HTTPS, for a server that has SSL enabled.
Inbound Refinery URL Prefix Relative URL for theInbound Refinery instance.
Server Instance Name Inbound Refinery instance name.
Server Instance Label Instance name shown for Inbound Refinery.
Service Instance Description Inbound Refinery Instance description

Parent topic: Configuring Inbound Refinery Settings (Single Node)

Configuring WebCenter Content Settings

You must complete the WebCenter Content configuration on the post-installation configuration page in Content Server.

WebCenter Content shows the configuration page when you first sign in to Managed Server at http://managedServerHost:managedServerPort/cs

Note:

The domain administrator must be the first user to sign in to the WebCenter Content Managed Server so that they can complete configuration. For more details about administration, see Introduction in Oracle Fusion Middleware Administering Oracle WebCenter Content

To complete WebCenter Content configuration:

  1. Start the Administration Server. See Starting the Administration Server.
  2. Start the WebCenter Content Managed Server. See Starting the Managed Servers.
  3. Go to the Content Server post-installation page at http://managedServerHost:16200/cs/
  4. Enter or edit any configuration values you want to change.
    You can select a full-text search engine in the FullText Search Option field. Leave the field blank to set up the system as metadata only.
  5. Enter a value in Incoming Socket Connection Address Security Filter to enable access from Inbound Refinery. For example:
    127.0.0.1|your.server.IP.address|0:0:0:0:0:0:0:1|

    This field accepts wildcards such as 10.*.*.* You can change this value later by setting SocketHostAddressSecurityFilter in DomainHome/ucm/cs/config/config.cfg and restarting WebCenter Content Managed Server.

    For Oracle WSM security, the SocketHostAddressSecurityFilter value must be set as follows: 

    SocketHostAddressSecurityFilter=*.*.*.*|0:0:0:0:0:0:0:1
  6. Verify that the Server Socket Port setting is 4444. The Managed Server configuration file stores this value as IntradocServerPort=4444
  7. Click Submit.
  8. Restart the WebCenter Content Managed Server. See Starting the Managed Servers
  • WebCenter Content Configuration Page
    You enter or verify values in the WebCenter Content configuration page fields to completeWebCenter Content configuration.
  • Completing the Imaging Configuration
    You can complete the initial configuration of Oracle WebCenter Content: Imaging in an Oracle WebLogic Server domain.
  • Configuring Capture
    The Capture System Administrator requires system administration privileges to configure and monitor an Oracle WebCenter Enterprise Capture system environment. The configuration consists of tasks such as starting the Capture Managed Server, assigning roles to Capture users in Fusion Middleware Control, and modifying system-level settings through MBeans.

Parent topic: Configuring WebCenter Content Domain

WebCenter Content Configuration Page

You enter or verify values in the WebCenter Content configuration page fields to completeWebCenter Content configuration.

You can use descriptions of these fields while completing steps in Configuring WebCenter Content Settings

Field Description
Content Server Instance Folder Absolute path to the Oracle instance directory of WebCenter Content. Default is DomainHome/ucm/ The default Oracle instance directory forInbound Refinery is ORACLE_HOME/user_projects/domains/DomainHome/ucm/cs The top-level folder in the folder hierarchy for the Content Server instance is cs.

The path to the Oracle instance directory is the value of the IntradocDir variable for the WebCenter Content instance. Oracle recommends that you make this directory path unique to this Managed Server, or node. For installations that you will probably upgrade, Oracle strongly recommends that you change the location of the Oracle instance directory to a directory outside any Oracle WebLogic Server domain directories or installation directories.

Native File Repository Location Path to the vault directory for storing native content checked into WebCenter Content.
Weblayout Folder Path to the weblayout directory for storing web-viewable renditions of native and alternate files.
Register Start Menu Actions Whether or not to register Start Menu actions.
Is New Content Server Instance Whether or not theWebCenter Content instance is new.
Server Socket Port Number of the port to call top-level services. Default: 5555

To set up a provider from Inbound Refinery back to Content Server, you can leave the default

Changing this field value also changes the IntradocServerPort entry in DOMAIN_HOME/ucm/ibr/config/config.cfg

Incoming Socket Connection Address Security Filter

Restricts WebCenter Content access to a computer or computers with a specified IP address or addresses.

The default value of this field is the local host’s IP address, such as 127.0.0.1.

You can specify multiple IP addresses, separated by pipes ( | ). Make sure that there are no spaces on either side of the pipe character. For example:

127.0.0.1|0:0:0:0:0:0:0:1|your.server.IP.address

This field accepts wildcards * for zero or many characters, and ? for any one character. (For example, 10.10.3.*)

Typically, use the IP Address Filter field only (most commoon) or Hostname Filter field, not both.

Web Server HTTP/HTTPS Address Name of the web server. (HttpServerAddress property).
WebAddress Is HTTPS Whether or not the URL for the web server starts with HTTPS, for a server that has SSL enabled.
Inbound Refinery URL Prefix Relative URL for theInbound Refinery instance.
Server Instance Name Inbound Refinery instance name.
Server Instance Label Instance name shown for Inbound Refinery.
Service Instance Description Inbound Refinery Instance description
Is Auto Number Enabled Whether or not automatic numbering of WebCenter Contentinstances is enabled.
Auto Number Prefix Unique prefix for an WebCenter Content instance number, to avoid conflicts among multiple WebCenter Content instances (Auto Number Prefix system property).
FullText Search Option Search engine for full-text search:

None: The Oracle Content Server instance uses DATABASE.METADATA as the search engine.

Internal: If using Oracle Database, the WebCenter Content instance uses OracleTextSearch with the system database. If using Microsoft SQL Server, it will use DATABASE.FULLTEXT.

External: The Oracle Content Server instance uses OracleTextSearch with an external provider to an Oracle Database (not the system database). If you select this option, you must enter the Data Source name in the External DataSource field.

External DataSource Name of the Data Source, which you must create in Oracle WebLogic Server and target to the Managed Server, using an OCSSEARCH schema created with Repository Creation Utility (RCU).

Parent topic: Configuring WebCenter Content Settings

Completing the Imaging Configuration

You can complete the initial configuration of Oracle WebCenter Content: Imaging in an Oracle WebLogic Server domain.

This section explains the steps to complete the Imaging configuration.

  • Completing the Initial Imaging Configuration
    Before you complete the configuration of Imaging, your system should have Oracle WebCenter Content installed and configured. Imaging uses WebCenter Content for its repository.
  • Configuring the Full-Text Features in the WebCenter Content Repository
    Imaging supports two types of full-text searching under WebCenter Content: DATABASE.FULLTEXT and OracleTextSearch. Imaging can use the full-text features if you configure full-text searching in the WebCenter Content repository.
  • Setting Imaging System Security
    On a new Imaging system, the first user to log in is automatically granted full permissions. Typically, this initial user associates other users or groups, after which the initial user’s permissions are changed or revoked as needed.
  • Configuring the Imaging Viewer Cache
    The Imaging viewer can cache documents on the server outside of the repository to increase rendering speed on the client machine. Security for the cached documents is controlled by authentication for the server on which the documents are stored.
  • Installing and Configuring AXF BPM and AXF for BPEL
    Oracle WebCenter Content: AXF for BPM and Oracle Application Extensions Framework (AXF) for BPEL are installed automatically with Imaging, and AXF for BPEL is automatically deployed to the Imaging Managed Server.

Parent topic: Configuring WebCenter Content Settings

Completing the Initial Imaging Configuration

Before you complete the configuration of Imaging, your system should have Oracle WebCenter Content installed and configured. Imaging uses WebCenter Content for its repository.

Your Imaging system uses WebCenter Content 12c as its document repository. For information about configuring WebCenter Content, see Configuring WebCenter Content Domain.

Note:

In a production system, Oracle WebCenter Content applications use an external Lightweight Directory Application Protocol (LDAP) authentication provider rather than the Oracle WebLogic Server embedded LDAP server, which is part of the default configuration. If you want to reassociate the identity store for Imaging with an external LDAP authentication provider, it is easier to do this association before you complete the configuration of the Imaging Managed Server and before you connect it to the WebCenter Content 12c repository. For more information, see Reassociating the Identity Store with an External LDAP Authentication Provider.

The user who logs in first to an Imaging Managed Server is provisioned with full security throughout the server. When this user first logs in, Imaging provides a user interface to complete the configuration, including connecting to a repository or repositories and, optionally, to a workflow server.

If a value is specified in the DefaultSecurityGroup MBean before Imaging security is initialized, then when the first user logs in, the specified group as well as the user logging in is given full administrative permissions.

To complete the Imaging configuration, you have to perform all the tasks that apply to your system:

  • Configuring a WebCenter Content Repository for Imaging
    You can configure WebCenter Content 12c as the repository for Imaging. You will not be able to import or upload content to the Imaging system unless you have created a repository connection.
  • Starting the Imaging Managed Server and Accessing the Web Client
    You can access the Imaging web client after you start the Administration server and the Imaging and WebCenter Content Managed Servers.
  • Connecting to a WebCenter Content Repository
    Before Imaging can use the WebCenter Content repository, you need to configure a connection to Content Server. You can create a connection to it from Imaging.
  • Connecting to a Workflow Server
    A connection to a workflow server (Oracle SOA Suite) is required before you import the definition files. This connection is necessary for your solution to retrieve your task list. Imaging connects to a workflow server when application fields are mapped to workflow payload elements.
  • Configuring the GDFontPath MBean for a UNIX System
    For conversions to work correctly on a UNIX operating system, the operating system needs to have TrueType fonts available. If these fonts are not available on your system, you need to install them. To set the font path on a UNIX operating system, you need to configure the GDFontpath MBean. You can configure it through the System MBean Browser in Oracle Enterprise Manager Fusion Middleware Control.
  • Setting DISPLAY for the Imaging Viewer in a UNIX Exalogic Environment with Solaris 12c
    In an Exalogic environment with Solaris 12c, you need to set the DISPLAY environment variable for the Imaging Viewer to work correctly in the basic mode.
  • Importing Definitions
    At this point in the installation process, you can import previously exported Imaging definitions (applications, searches, and inputs).

Parent topic: Completing the Imaging Configuration

Configuring a WebCenter Content Repository for Imaging

You can configure WebCenter Content 12c as the repository for Imaging. You will not be able to import or upload content to the Imaging system unless you have created a repository connection.

Configuring WebCenter Content 12c to Work with Imaging

WebCenter Content 12c is installed with Oracle WebCenter Content. When a WebCenter Content Managed Server and Imaging Managed Server are configured in an Oracle WebLogic Server domain on the same host machine, the configuration of WebCenter Content 12c to work with Imaging is automatic.

If WebCenter Content is installed in a domain that is later extended with Imaging, then WebCenter Content will not be reconfigured to work with Imaging until the next restart of the WebCenter Content Managed Server. In this case, you must restart WebCenter Content before you connect to Oracle WebCenter Content Server from the Imaging web client, as described in Connecting to a WebCenter Content Repository.

If the WebCenter Content and Imaging Managed Servers are configured to run on different machines, configuring Imaging will not configure WebCenter Content to work with it. In this case, you must follow the manual configuration steps to configure WebCenter Content.

To configure WebCenter Content 12c manually to work with Imaging:
  1. Start the WebCenter Content Managed Server, as described in Starting the Managed Servers.
  2. Access Content Server.
  3. Enable the IpmRepository component:
    1. From the Administration tray or menu, select Admin Server, and then select Component Manager.
    2. On the Component Manager page, select Integration.
    3. Select IpmRepository, and click Update.

      This option is selected by default if the Oracle WebLogic Server domain is configured with Fusion Middleware Configuration Wizard. If this option is already selected, you can close Component Manager without clicking Update or restarting Content Server.

    4. Click OK.
    5. Restart Content Server.

      If you have already selected IpmRepository, you do not need to restart the server.

Configuring a File Store Provider for Content Storage

An administrator can configure a file store provider in Content Server 11g to control how and where files are stored and managed within Content Server. Instead of storing all content on a single file system, you can use a file store provider to store content across multiple file systems as well as within a database. The File Store Provider component is installed and enabled by default with WebCenter Content installation and configuration

For Imaging, you should add a file store provider to use instead of the default file store provider. Also, you should disable the traditional web layout functionality for the file store.

You can configure a file store provider for Oracle Database.

If your WebCenter Content installation uses a Microsoft SQL Server or IBM DB2 database, do not configure a file store provider. If you are configuring a WebCenter Content Managed Server with one of these databases, you need to disable the file store provider that is enabled by default for Content Server. See Managing a File Store System in Oracle Fusion Middleware Administering Oracle WebCenter Content

Configuring a File Store Provider

A file store provider can be a combination of any media supported by Content Server. Because the document storage location is not defined by the media that is being used for storage, the term volume is used to represent a storage location when an application is defined in the Imaging user interface. Imaging connects to a volume that an administrator defines and configures in Content Server. You cannot use Imaging to create or define a volume.

A Content Server administrator can configure a file store provider. See Managing the File Store Provider in Oracle Fusion Middleware Administering Oracle WebCenter Content

Disabling Web Layout Functionality for Imaging

Content Server traditionally uses a weblayout/ directory on a file system to store content in a format for viewing in a web browser, even if the main storage volume is set up in a database. This file system store is useful for making content retrieval faster for a website or for storing a secondary file that describes the primary content item, but it does not have much use in an Imaging solution. Files copied to a weblayout/ directory in an exclusively Imaging solution would never get used, taking up unnecessary storage space. Oracle recommends that you disable the web layout functionality for any file store provider that is configured for use as an Imaging volume.

Note:

If your Imaging system will use redactions, do not implement Web Layout. Users might be able to see an unredacted version of a document in the weblayout/ directory if Web Layout (IBR) is turned on in an Imaging file store provider.

An administrator can disable the web layout functionality by selecting the Is Webless File Store option on the Add/Edit Storage Rule page for a file store provider in Content Server. See Adding or Editing a Storage Rule in Oracle Fusion Middleware Administering Oracle WebCenter Content

Starting the Imaging Managed Server and Accessing the Web Client

You can access the Imaging web client after you start the Administration server and the Imaging and WebCenter Content Managed Servers.

To access the Imaging web client:
  1. Start the Imaging Managed Server, as described Starting the Managed Servers.

    Note:

    If Oracle WebCenter Content: AXF for BPM is deployed to the domain, proceed to Configuring and Verifying AXF for BPM before you perform any configuration on the Imaging server.

  2. Access the web client at this URL: http://managedServerHost:16000/imaging. Log in with the administrator user name and password.

    Note:

    This first user who connects to the Imaging system is registered as the Imaging administrator.

Connecting to a WebCenter Content Repository

Before Imaging can use the WebCenter Content repository, you need to configure a connection to Content Server. You can create a connection to it from Imaging.

To connect to a WebCenter Content repository:
  1. Open a web browser, and navigate to this website: http://managedServerHost:16000/imaging.
  2. Log in with the administrator user name and password.
  3. Navigate to the Manage Connections tray and select Create Content Server Connection from the list.
  4. Enter a name for the connection on the Basic Information page and, optionally, a description, and then click Next.
  5. Change the selections, if required, on the Connection Settings page:

    • SSL: Selected for secure SSL communications.

    • Server Port: The IDC port of the WebCenter Content instance. By default, 4444 for Imaging.

    • Use Local Content Server: Selected by default if Content Server is on the same machine as the Imaging server.

      If the servers are not installed on the same machine, configure the Content Server machine name as part of the Content Server Pool.

  6. Click Next.
  7. Enter a Connection Security value for the connection.

    Select which users and groups should have permission to access, modify, delete, or grant other users access to this connection definition. At least one user or group must have the grant access permission.

  8. Click Next
  9. At the Summary screen, click Submit.
Connecting to a Workflow Server

A connection to a workflow server (Oracle SOA Suite) is required before you import the definition files. This connection is necessary for your solution to retrieve your task list. Imaging connects to a workflow server when application fields are mapped to workflow payload elements.

To connect, the provider, port, and credential information is passed using Web Services Inspection Language (WSIL). WSIL uses the HTTP protocol and a specific XML format to allow for the discovery of the web service end points on a server. Imaging follows links in the WSIL that meet certain criteria to discover deployed composites.

The connection can be to an Oracle Business Process Management (Oracle BPM) or Business Process Execution Language (BPEL) server. For Imaging to take advantage of BPM and Oracle BPEL Process Manager within an existing domain, the domain must be extended with Oracle BPM Suite - 12.2.1.4.0. When Oracle BPM Suite is installed, it automatically selects Oracle SOA Suite - 12.2.1.4.0 as its dependency. If you want to use Oracle BPEL Process Manager and not Oracle BPM, you can extend the domain with an Oracle SOA Suite installation and configuration. See About the Oracle SOA Suite and Oracle Business Process Management Installation in Oracle Fusion Middleware Installing and Configuring Oracle SOA Suite and Business Process Management.

This section describes the procedure to configure a connection to a workflow server and register the connection in your database. For additional information, see Creating a Workflow Connection in Administering Oracle WebCenter Content: Imaging.

Configuring a Connection to a Workflow Server

If you have installed the Oracle SOA Suite for use with Imaging, such as for AXF for BPM or AXF for BPEL, you need to configure a connection to a workflow server.

To configure a connection to a workflow server:
  1. Open a web browser, and navigate to this website: http://managedServerHost:16000/imaging.
  2. Log in with the administrator user name and password.
  3. Navigate to the Manage Connections tray and select Create Workflow Connection from the list.
  4. Enter a name for the connection on the Basic Information page and, optionally, a description, and then click Next.
  5. Optionally, change one or more of the following selections on the Connection Settings page:

    • HTTP Front End Address: The front end address of the workflow server, including the listening port, which is http://<server>:8001 for Oracle SOA Suite, by default.

    • Credential Alias: The credential store key for obtaining user and password credentials for the workflow server.

    • Provider: The provider setting can be either the host name or IP address of a single machine, or a comma-separated list of host names or IP addresses for multiple machines in a cluster. The listening port and transport mechanism should be included in the setting.

  6. Click Test Connection to verify the settings.
  7. Click Next.
  8. Enter a Connection Security value for the connection.

    Select which users and groups should have permission to access, modify, delete, or grant other users access to this connection definition. At least one user or group must have the grant access permission.

  9. Click Next
  10. At the Summary screen, click Submit.
Adding the Connection to the Database

After you have created a workflow connection, enter the name of that connection in the AXF_SOLUTION_ATTRIBUTES table for your solution. For example, the parameter key for a BPEL server is named WORKFLOW_CONNECTION, and the HelloBPEL sample script uses the connection name test.

Configuring the GDFontPath MBean for a UNIX System

For conversions to work correctly on a UNIX operating system, the operating system needs to have TrueType fonts available. If these fonts are not available on your system, you need to install them. To set the font path on a UNIX operating system, you need to configure the GDFontpath MBean. You can configure it through the System MBean Browser in Oracle Enterprise Manager Fusion Middleware Control.

To configure the GDFontPath MBean for a UNIX system:
  1. Access the Imaging domain in Fusion Middleware Control by using the URL:http://adminServerHost:adminServerPort/em

    For adminServerHost, specify the name of the computer that hosts the Administration Server for your domain. For adminServerPort, specify the listen port number for the Administration Server. The default number is 7001. For example: http://myHost.example.com:7001/em

    To log in, provide the user name and password that were specified on the Configure Administrator User Name and Password screen in the Configuration Wizard.

  2. In the navigation tree on the left, expand WebLogic Domain and the deployed domain.
  3. Right-click IPM_server1, and select System MBean Browser from the menu.
  4. In the navigation tree on the System MBean Browser page, under Configuration MBeans, close the com.bea folder.
  5. Under Application Defined MBeans, expand the oracle.imaging folder.
  6. Expand the Server: IPM_server1 and config folders.
  7. Click config.
  8. Set the value of the GDFontPath attribute to the location of your True Type Fonts (TTF) files; for example: /usr/share/X11/fonts/TTF

    For systems on which Oracle WebLogic Server includes a JDK, you can find some TTF files in the JDK/jre/lib/fonts directory.

    Some standard font locations on different UNIX platforms follow:

    • Solaris SPARC: /usr/openwin/lib/X11/fonts/TrueType

    • AIX: /usr/lpp/X11/lib/X11/fonts/TrueType

    • HP-UX Itanium: /usr/lib/X11/fonts/TrueType

    • Linux: /usr/lib/X11/fonts/TrueType

  9. Click Apply.
  10. Restart Imaging.
Setting DISPLAY for the Imaging Viewer in a UNIX Exalogic Environment with Solaris 12c

In an Exalogic environment with Solaris 12c, you need to set the DISPLAY environment variable for the Imaging Viewer to work correctly in the basic mode.

To set DISPLAY for the Imaging Viewer in a UNIX Exalogic Environment with Solaris 12c:
  1. Open a new terminal window and run this command:
    xhost +
  2. In the Imaging terminal, set the DISPLAY environment variable to the server where Imaging is running and specify the port, in this format:
    servername:port
  3. Restart Imaging.
Importing Definitions

At this point in the installation process, you can import previously exported Imaging definitions (applications, searches, and inputs).

For more information, see Exporting and Importing Definitions in Administering Oracle WebCenter Content: Imaging.

For additional information about how to import definitions, see Importing Definition Files into Imaging.

Configuring the Full-Text Features in the WebCenter Content Repository

Imaging supports two types of full-text searching under WebCenter Content: DATABASE.FULLTEXT and OracleTextSearch. Imaging can use the full-text features if you configure full-text searching in the WebCenter Content repository.

For DATABASE.FULLTEXT systems, after the indexes are rebuilt, nothing needs to be done on the Imaging side. OracleTextSearch, however, requires that the index be rebuilt any time an application with FullText enabled is created, deleted, or has modifications that involve field definitions.

For more information on configuring full-text searching, see Configuring OracleTextSearch for Content Server.

For additional full-text configuration options, see Configuring the Search Index in Oracle Fusion Middleware Administering Oracle WebCenter Content.

After full-text is enabled in WebCenter Content, you will need to create an application and check the FullText option on the application. See Configuring System Properties in Oracle Fusion Middleware Administering Oracle WebCenter Content.

Setting Imaging System Security

On a new Imaging system, the first user to log in is automatically granted full permissions. Typically, this initial user associates other users or groups, after which the initial user’s permissions are changed or revoked as needed.

Note:

If you configure Imaging for use with Oracle Access Manager, you must protect the imaging/faces/ directory. Otherwise, you will not get access to the Imaging Viewer.

If security provider changes are made after this initial user login to Imaging, take the following steps to reset Imaging system security. For example, if you later change the security configuration to point to an Oracle Internet Directory provider or a Microsoft Active Directory provider, you must reset the Imaging system security.
  1. Manually create or migrate users and groups to the new external security provider, using utilities as needed. See Reassociating the Identity Store with an External LDAP Authentication Provider.
  2. Run the refreshIPMSecurity() WLST MBean command. See refreshIPMSecurity in WebCenter WLST Command Reference.

    Note:

    During the refresh, users or groups for whom matching identifying information is not found are ignored. As security changes are made, invalid users or groups are removed from the Imaging database.

Configuring the Imaging Viewer Cache

The Imaging viewer can cache documents on the server outside of the repository to increase rendering speed on the client machine. Security for the cached documents is controlled by authentication for the server on which the documents are stored.

If the server is considered secure, no additional security is necessary. If additional security is required, you can encrypt cached documents as described in Encrypting Cached Documents.

To set the Imaging viewer to use cached documents:
  1. Verify that the Imaging Viewer Cache was successfully deployed:
    1. In the WebLogic Server Administration Console, click Deployments under Domain Structure.
    2. In the imaging-vc row of the Deployments table, confirm that the State value is Active and the Health value is OK.

    If the State or Health value is different for imaging-vc, you need to fix the deployment, or redeploy the feature before you proceed.

  2. Enable viewer caching by setting the ViewerCachePath MBean to the location where the documents must be cached, as described in Configuring the GDFontPath MBean for a UNIX System. For example, to enable caching on an Imaging system that runs on a single computer, you can use the relative path imaging/ViewerCache. If no path is set, then caching of documents is disabled.

    Note:

    The ViewerCachePath MBean must be set to a location that is available to all the servers in the cluster. If the directory path is not available to all the servers, each server will cache documents locally, resulting in multiple instances of the entire cache.

  3. Specify the number of days for documents to remain in the cache location after being viewed, by setting the ViewerCacheDays MBean. Cached documents not viewed within the specified number of days are purged from the cache. If a document is viewed within the specified number of days, the ViewerCacheDays timer for that document is reset. If you set ViewerCacheDays equal to 0 (the default), you cannot purge the documents from cache.
  4. Set the ViewerCacheEnablePrecache MBean to true to cache documents when they are ingested into Imaging (pre-cache) or set the value to false to cache documents when they are first called by the viewer.
  • Changing the Viewer Cache Path
    You can move the viewer cache to a new location if the Imaging server is shut down and the new location uses the same file hierarchy as the old location.
  • Encrypting Cached Documents
    For additional security, you an configure Imaging to encrypt the cached documents. Encryption makes additional processing necessary to decrypt a document for viewing, and reduces the rendering speed. Even if you configure Imaging to encrypt the cached documents, there is a brief period of time during caching when the documents that are generated are not encrypted.
  • Disabling Encryption of Cached Documents
    You can disable the encryption of cached documents by setting the value of the ViewerCacheEnableEncryption MBean to false.

Parent topic: Completing the Imaging Configuration

Changing the Viewer Cache Path

You can move the viewer cache to a new location if the Imaging server is shut down and the new location uses the same file hierarchy as the old location.

To change the viewer cache path:
  1. Shut down the Imaging server.
  2. Move the cached files to the new location. Ensure that you preserve the file hierarchy.
  3. Set the new path in the ViewerCachePath MBean.
  4. Start the Imaging server.
Encrypting Cached Documents

For additional security, you an configure Imaging to encrypt the cached documents. Encryption makes additional processing necessary to decrypt a document for viewing, and reduces the rendering speed. Even if you configure Imaging to encrypt the cached documents, there is a brief period of time during caching when the documents that are generated are not encrypted.

To enable encryption of cached documents:
  1. Add a new password credential to the domain with Oracle Enterprise Manager Fusion Middleware Control:
    1. Select the WebLogic Server domain for Oracle WebCenter Content.
    2. From the WebLogic Domain menu, select Security, and then Credentials.
    3. Select the map oracle.imaging. If there is no map named oracle.imaging, click Create Map, specify oracle.imaging for the map name, and then select it.
    4. Click Create Key. Name the key viewer.cache, and select the type Password.
    5. Enter a user name. The user name does not need to exist in any system.
    6. Enter a password, confirm it, and then click OK.
  2. Enable encryption by setting the ViewerCacheEnableEncryption MBean, as described in Configuring the GDFontPath MBean for a UNIX System.

    Note:

    The password credential must exist on the domain before you set the ViewerCacheEnableEncryption MBean.

Disabling Encryption of Cached Documents

You can disable the encryption of cached documents by setting the value of the ViewerCacheEnableEncryption MBean to false.

Subsequent calls to the viewer causes unencrypted documents to be cached. You can decrypt and view any encrypted documents that are already in the cache if the password credential remains unaltered in the domain.

If you removed or alter the password credential, you must manually purge the encrypted documents that are still cached.

To purge the imaging.jks file:
  1. Shut down the Imaging server.
  2. Delete the cached files from the cache directory.
  3. Delete the imaging.jks file from the cache directory.
  4. Start the Imaging server.
Installing and Configuring AXF BPM and AXF for BPEL

Oracle WebCenter Content: AXF for BPM and Oracle Application Extensions Framework (AXF) for BPEL are installed automatically with Imaging, and AXF for BPEL is automatically deployed to the Imaging Managed Server.

Before you can deploy AXF for BPM to the Imaging server, you need to create the required schemas with the Repository Creation Utility. Then when the domain is created or extended, you can select AXF for BPM to use it with Imaging.

You can configure either AXF for BPM or AXF for BPEL, or both, to run on the Imaging Managed Server:

  • AXF for BPM

    The newer AXF for BPM infrastructure takes advantage of the application development and configuration capabilities that are provided by technologies such as Oracle Business Process Management (Oracle BPM), Oracle Application Development Framework (Oracle ADF), Oracle Metadata Services Repository (Oracle MDS Repository), and Oracle Business Rules to create configurable business components. These business components help administrators to configure and develop integration solutions for WebCenter Content business applications. See Configuring and Verifying AXF for BPM.

  • AXF for BPEL

    You can configure AXF for BPEL to run on the Imaging Managed Server. The older AXF for BPEL infrastructure relies on AXF database tables (Imaging tables) as the basis for configuring AXF solutions, commands, and web tools. A solution developer or solution accelerator can implement and customize these solutions, commands, and tools. See Configuring and Verifying AXF for BPEL.

For additional information about configuring and using AXF for BPM or AXF for BPEL and the AXF for BPEL database tables (Imaging tables), see Configuring the BPEL Imaging Solution in Oracle Fusion Middleware Administering the Application Adapters for Oracle WebCenter.

Configuring and Verifying AXF for BPM

Before you configure AXF for BPM with Imaging, you need to install and configure Oracle WebCenter Content and Oracle SOA Suite, and create an AXF schema with the Repository Creation Utility, as well as schemas for the following components:

  • Metadata Services

  • Oracle WebCenter Content Server - Complete

  • Oracle WebCenter Content: Imaging

  • SOA Infrastructure

  • User Messaging Service

When you create or extend the WebLogic Server domain, be sure the following product templates are selected:

  • Oracle SOA Suite

  • Oracle WebCenter Content: AXF for BPM

    Note:

    If AXF for BPM is on a separate host machine from the Oracle SOA Suite Managed Server, you need to extend the domain with Oracle WSM Policy Manager.

  • Oracle WebCenter Content: Imaging

  • Oracle Universal Content Management - Content Server (for WebCenter Content)

  • Oracle Enterprise Manager

  • Oracle BPM Suite

After you create or extend a domain to include AXF for BPM and the components and products it depends on, you can configure it to work with Imaging using the WebLogic Server Administration Console, Oracle WebLogic Server Scripting Tool (WLST), and Oracle Enterprise Manager Fusion Middleware Control. You can also set up communications with Oracle Coherence between AXF for BPM and Imaging servers running on multiple domains or machines or to prevent multicast interference between AXF for BPM and Imaging in a single domain. See Configuring AXF for BPM.

To verify that you have installed and configured the AXF for BPM infrastructure properly, AXF for BPM includes the HelloBPM solution, which uses an Oracle BPM process to verify the BPM integration. See Verifying the AXF for BPM Installation.

Configuring AXF for BPM

Use the following procedure to configure AXF for BPM with the Imaging server. You can set up the Imaging server through the WebLogic Server Administration Console, create foreign JNDI with WLST, and configure the AXF for BPM CSF key through Fusion Middleware Control.

To configure AXF for BPM to work with Imaging Managed Servers that run in a cluster or other distributed configuration, you need to set up communications with Oracle Coherence. See Oracle Coherence Communications for Imaging Clusters, Multiple Domains, or Multiple Machines. In a single domain, you can set up communications with Oracle Coherence to avoid interference from multicast traffic. See Oracle Coherence Communications for a Single Server or Domain.

To configure AXF for BPM:
  1. Set up the Imaging server through the WebLogic Server Administration Console:
    1. The Administration Server should be running. If not, start the Administration Server for your Oracle WebLogic Server domain. See Starting the Administration Server.
    2. Log in to the Administration Console.
    3. Under Domain Structure on the left, expand Environment, and click Servers.
    4. In the Servers table, click the Imaging server instance, such as IPM_server1.
    5. Click the Protocols tab.

      If the server is in production mode, click Lock & Edit in the Change Center on the left before you make changes.

    6. Click the HTTP tab and set these values:

      • Frontend Host: The name of the host machine for the Imaging server, such as myserver.example.com.

      • Frontend HTTP Port: The port number for the Imaging instance, such as 16000.

    7. Save the changes.

      If the server is in production mode, activate changes after you save them, unless you have enabled configuration editing.

  2. If the Oracle SOA Suite Managed Server is on a separate host machine from Imaging, set the targeting for the IPMDS and mds-axf data sources to the Oracle SOA Suite server:
    1. Log in to the Administration Console on the Oracle SOA Suite machine.
    2. Under Domain Structure on the left, expand Services, and click Data Sources.
    3. Select Generic Data Source from the New menu.
    4. Enter jdbc/IPMDS in the JNDI Name field.
    5. Select your database type in the Database Type list, and click Next.
    6. Configure values for Data Source Properties to match the connection of the same name on the corresponding Imaging server, including using the same schema.
    7. Test the configuration to ensure everything is valid.
    8. Click Finish.
    9. On the Configuration tab of the Summary of JDBC Data Sources page, click IPMDS.
    10. Click the Targets tab.
    11. Select the name of the Oracle SOA Suite server.
    12. Click Save.
    13. Return to the Configuration tab on the Summary of JDBC Data Sources page, and click mds-axf.
    14. Click the Targets tab.
    15. Select the name of the Oracle SOA Suite server.
    16. Click Save.
  3. If the Oracle SOA Suite Managed Server is on a separate host machine from Imaging, create a SOALocalTxDataSource data source on the Imaging server as it is set up on the Oracle SOA Suite server:
    1. Log in to the Administration Console on the Imaging machine.
    2. Under Domain Structure on the left, expand Services, and click Data Sources.
    3. On the Configuration tab of the Summary of JDBC Data Sources page, select Generic Data Source from the New menu.
    4. In the Name field, specify SOALocalTxDataSource.
    5. In the JNDI Name field, specify jdbc/SOALocalTxDataSource.
    6. Select your database type in the Database Type list, and click Next.
    7. Configure values for Data Source Properties to match the connection of the same name on the corresponding Oracle SOA Suite server, including using the same schema.
    8. Test the configuration to ensure everything is valid.
    9. Click Next to select targets.
    10. Select the name of the Imaging server.
    11. Click Finish.
  4. Create the foreign JNDI with the Oracle WebLogic Scripting Tool (WLST):
    1. Change to the WCC_ORACLE_HOME/axf_bpm/scripts directory.
    2. Edit the create-foreign-JNDI.py script by using a text editor.
    3. Set the following variables at the top of the file:
      # host to login to for executing script
var_host = "" # (-h) WebLogic Server Administration Server host name
var_hostPort = "" # (-p) Administration Server port
var_user = "" # (-u) WebLogic Server User Name
var_credential = "" # (-c) WebLogic Server Password
# JNDI settings
var_jndiURIServer = "" # (-t) JNDI target URI of Oracle SOA Suite host
var_jndiURIServerPort = "" # (-v) JNDI target URI port
var_serverTargetName = "" # (-s) Managed Server name, for targeting the Imaging server
var_jndiUser = "" # (-n) JNDI user name
var_jndiPassword = "" # (-d) JNDI password
    4. Save the file.
    5. Run the create-foreign-JNDI.py script against the Imaging server with WLST.
      The WebLogic Server should be the only server running when you execute the script, as follows:
      cd WCC_ORACLE_HOME/common/bin
./wlst.sh create-foreign-JNDI.py
  5. Configure the AXF for BPM CSF key:
    1. Log in to Oracle Enterprise Manager Fusion Middleware Control.
    2. Navigate to the WebLogic Server domain and right-click the deployed domain (base_domain by default).
    3. In the resulting menu, select Security, and then Credentials.
    4. Create a new map, specify the map name as oracle.wsm.security.
    5. Create a new key:

      • Specify a key name, such as ipmadmin.

      • Specify a valid administrator user, such as weblogic.

      • Specify the password.

      • Click OK.

Oracle Coherence Communications for Imaging Clusters, Multiple Domains, or Multiple Machines
If you are configuring AXF for BPM, you should configure communications with Oracle Coherence, which AXF for BPM utilizes. By default, the server is set up for clustering with the following settings configured in the DOMAIN_HOME/bin/setDomainEnv.sh script:
-Dtangosol.coherence.clusteraddress=224.3.1.99
-Dtangosol.coherence.clusterport=3199
-Dtangosol.coherence.log=jdk

In an Imaging cluster, you need to set up AXF for BPM communications with Oracle Coherence with a unique multicast address and port to avoid unwanted multicast traffic from interfering with the system. For more information about configuring Oracle Coherence in clusters, Using Coherence Clusters in Oracle Fusion Middleware Developing Applications with Oracle Coherence

Parent topic: Configuring AXF for BPM

Oracle Coherence Communications for a Single Server or Domain
For a single-server or domain installation, you can configure Oracle Coherence to avoid the multicast traffic of other machines by editing the DOMAIN_HOME/bin/setDomainEnv.sh script as follows:
  1. Open the DOMAIN_HOME/bin/setDomainEnv.sh script in a text editor.
  2. Perform a search for coherence to locate existing settings.
  3. Append the following two setting after any existing Oracle Coherence settings; for instance, after -Dtangosol.coherence.log=jdk:
    -Dtangosol.coherence.localhost=127.0.0.1
-Dtangosol.coherence.ttl=0
  4. Save the settings.
  5. Restart any running Managed Servers on the domain for the changes to take effect.

Parent topic: Configuring AXF for BPM

Verifying the AXF for BPM Installation

You can verify the AXF for BPM installation and configuration with the HelloBPM solution, which uses a BPM process. This section describes the procedure to deploy and use this solution.

Configuring the HelloBPM Solution

Before you can use the HelloBPM solution to validate the installation and configuration of AXF for BPM, you need to deploy and configure the solution on the Imaging Managed Server.

To configure the HelloBPM solution:
  1. Set up the database:
    1. Change to the WCC_ORACLE_HOME/axf_bpm/scripts directory.
    2. Run the AXF_HELLO_BPM_DATA.sql script while connected to the Imaging database schema as the Imaging database user, with the following three parameters, which will insert the data necessary to run the HelloBPM solution:

      • SOAMachineName:Port

      • IPMMachineName:Port

      • CSFKEY

  2. If the Oracle SOA Suite Managed Server is on a separate host machine from Imaging, you will need to manually deploy the Hello BPM process. Copy the WCC_ORACLE_HOME/axf_bpm/bpm/sca_axfHelloBPM_rev1.0.jar file to DOMAIN_HOME/soa/autodeploy/ prior to starting the Oracle SOA Suite Managed Server.
  3. Start up the remaining servers in the following order:
    1. Weblogic Server Administration Server (should already be running)
    2. Oracle SOA Suite Managed Server
    3. Imaging Managed Server
    4. WebCenter Content Managed Server
  4. Verify that a URI is set on the deployed process:
    1. Log in to Oracle Enterprise Manager Fusion Middleware Control.
    2. Navigate to the Oracle SOA Suite Managed Server, then soa-infra (soa_server1), and then default, and click axfHelloBPM.
    3. In the Component Metrics section, click SalesQuoteEntry.
    4. Click the Administration tab.
    5. If a valid URI is not set, create one with these settings:

      • Application Name: worklist

      • Host Name: The name of the host machine for the server

      • HTTP Port: The port of the host machine for the server

      • HTTPS Port: The secure port of the host machine for the server, or the default value if SSL is not configured

      • URI: /workflow/axfSolutionHelloBPM/faces/adf.task-flow?_id=SalesQuoteEntry_TaskFlow&_document=WEB-INF/SalesQuoteEntry_TaskFlow.xml

Importing Definition Files into Imaging

You can import definition files for tasks into the Imaging server through the Imaging Injector.

To import definition files into Imaging:
  1. Create the connections:
    1. Log in to Imaging as an administrator user, such as ipmadmin.

      Note:

      This first user to connect to the Imaging system is registered as the Imaging administrator. See Completing the Initial Imaging Configuration.

    2. In the navigation tree on the left, expand Manage Connections.
    3. Select Create Content Server Connection from the drop-down menu, and configure the connection:

      • On the Create Connection: Basic Information page, specify a name for the connection, and click Next.

      • On the Create Connection: Content Server Settings page, specify whether to use SSL, then specify whether to use a local Content Server (default) or specify an external server through the Content Server Pool section, and then click Next.

      • On the Create Connection: Security page, add the Administrators group with full rights, and click Next.

      • Review your settings, and click Submit.

    4. Select Create Workflow Connection from the drop-down menu, and configure the connection:

      • On the Create Connection: Basic Information page, specify a name for the connection, and click Next.

      • On the Create Connection: Workflow Settings page, specify the following information, and then click Next.

        HTTP Front End Address: Specify the fully qualified HTTP address for the Oracle SOA Suite server:
        http://managedServerHost:managedServerPort/

        Credential Alias: This should be the CSF key name that was specified in Step 5 of Configuring and Verifying AXF for BPM, such as ipmadmin.

        Provider: Specify the fully qualified t3 address for the Oracle SOA Suite Server:
        t3://managedServerHost:managedServerPort/

      • On the Create Connection: Security page, add the Administrators group with full rights, and click Next.

      • Review your settings, and click Submit.

  2. Import the definition file, WCC_ORACLE_HOME/axf_bpm/ipm into Imaging, using the definition import tool.

    For more information on uploading definitions and resolving environment configurations, including the repository connection and BPEL server connection as well as the security configurations of the applications, see About Imaging in Administering Oracle WebCenter Content: Imaging.

    1. In the navigation tree on the left, expand Tools.
    2. Select Import Definitions.
    3. Browse to and select the WCC_ORACLE_HOME/axf_bpm/ipm/HelloBPM.xml file.
    4. Click Next.
    5. On the Select Definitions step, select Action for HelloBPM Application, HelloBPM Input, and HelloBPM Search.
    6. Click Next.
    7. On the Validation step, select Choose New for the Application Security field, and select the Administrators group. Also, select the Administrators group for the Applications, Document Security, Inputs Security, and Searches Security fields.
    8. For the Workflow field, select Workflow Connection.
    9. Click Submit.
Accessing the Solution Administration Page

Before you can access the Solution Administration page, you need to set up an axfadmin group in WebLogic Server and assign your WebLogic Server user name to this group.

To access administration functions for the solution application:
  1. Open the new driver page:
    http://machinename:16000/axf/faces/pages/axfadmin.jspx
  2. Click the Command Driver link on the left.
  3. Use the following values:
    1. solutionNamespace: SalesQuoteEntry
    2. commandNamespace: StartSalesQuoteEntry
  4. Click Execute Request.
  5. Click Execute Response.
The Solution Administration page opens. Table 4-1 shows the example parameters for this page.

Table 4-1 Parameters for the Solution Administration Page

Parameter Value

solutionNamespace

SalesQuoteEntry

commandNamespace

StartSalesQuoteEntry

Username

The user name for the request.

You can access the Business Rule Editor through the Solution Administration page and use this editor to perform any customizations.

Injecting Tasks into Imaging

After you deploy the AXF for BPM process, you can inject tasks into Imaging either from the content input files, through the Imaging input agent, or from the Oracle SOA Suite server, through Oracle Enterprise Manager Fusion Middleware Control.

You can inject tasks into the HelloBPM solution from content input files that are installed with the AXF for BPM infrastructure. Injecting tasks through the Imaging input agent enables you to test solution application changes. If needed, you can modify the input files to match the HelloBPM workflows.

These content input files are in the following directory with WCC_ORACLE_HOME/axf_bpm/ipm/HelloBPM.xml, the Imaging application definition: 
$WCC_ORACLE_HOME/axf_bpm/ipm/

This directory includes three input files:

  • TestSalesQuote.pdf

  • TestSalesQuote.txt

  • TestSalesQuote.xml

The following procedure is based on the assumption that InputDirectory is left with the default configuration (/IPM/InputAgent/Input).

To inject tasks through the input agent:
  1. Copy the PDF and XML files into the DOMAIN_HOME directory, and copy the TXT file into the DOMAIN_HOME/IPM/InputAgent/Input directory (default configuration). You also might need to change file permissions so that InputAgent has access to these files. See Enabling Input Agent in Administering Oracle WebCenter Content: Imaging.

    Within the specified time interval (15 minutes by default), the input agent picks up the input files and creates a document with metadata values from the text input file, an image from the PDF file, and supporting content from the XML file.

    Based on the workflow configuration in place with the HelloBPM solution, a task is created for the document that displays in the BPM task list.

  2. In the task list, click the newly injected task to view its details in the solution application.
  3. As needed, modify the metadata values in the text input file before injecting the input files again. For example, you might inject a task with missing account information to work with its human task flow.
Configuring and Verifying AXF for BPEL

To configure AXF for BPEL to work with Imaging Managed Servers that run in a cluster or other distributed configuration, you need to configure the Java Object Cache (JOC) to be distributed to all of the Managed Servers. See Clustering for AXF in Imaging Managed Servers.

For verification that the AXF for BPEL infrastructure is properly installed, AXF for BPEL includes two simple solutions:

  • HelloWorld, a basic solution that returns a Hello string.

  • HelloBpel, a solution that includes a BPEL process to verify the BPEL integration.

Verifying the AXF for BPEL Installation and Configuration with HelloWorld

Follow these steps to enable the HelloWorld solution:
  1. As user who owns the Imaging schema, run the insertHelloCommand.sql script from one of the following directories.

    • UNIX path:

      MW_HOME/WCC_ORACLE_HOME/axf/drivers/HelloWorld/dbscripts

    • Windows path:

      MW_HOME\WCC_ORACLE_HOME\axf\drivers\HelloWorld\dbscripts

    Note:

    For IBM DB2 only, add the following line to beginning of the insertHelloCommand.sql script before you run it:
    CONNECT TO soadb USER am3_ipm USING oracle;
  2. Access the driver page of the AXF for BPEL web application using the following URL:
    http://host:port/imaging/faces/Driver.jspx
  3. Enter the following values:

    • Solution Namespace: HelloWorld

    • Command Namespace: Hi

    • User Name:jcooper

    Note:

    This user name is valid only if you are using the application server's built-in jazn.xml security.

  4. Click Execute Command.

    An AXF for BPEL response should display with a populated Conversation ID. If the response is returned, the AXF for BPEL infrastructure is functioning correctly, and commands can be added and executed.

Verifying the AXF for BPEL Installation and Configuration with HelloBpel

The HelloBpel solution includes a BPEL process and a SQL script to set up the HelloBPEL solution namespace for use by that process. The BPEL process and database script are in the following directories.
  • UNIX path:
    MW_HOME/WCC_ORACLE_HOME/axf/drivers/HelloBpel

  • Windows path:

    MW_HOME\WCC_ORACLE_HOME\axf\drivers\HelloBpel

To enable the HelloBpel solution:

  1. Run one of the following HelloBPEL SQL scripts:

    • UNIX scripts:

      MW_HOME/WCC_ORACLE_HOME/axf/drivers/HelloBpel/dbscripts
/oracle/insertHelloBPELData.sql
      MW_HOME/WCC_ORACLE_HOME/axf/drivers/HelloBpel/dbscripts
/sqlserver-db2/insertHelloBPELData.sql

    • Windows scripts:

      MW_HOME\WCC_ORACLE_HOME\axf\drivers\HelloBpel\dbscripts
\oracle\insertHelloBPELData.sql
      MW_HOME\WCC_ORACLE_HOME\axf\drivers\HelloBpel\dbscripts
\sqlserver-db2\insertHelloBPELData.sql

    If you are using Oracle Database, then run the script from the oracle directory.

    If you are using an IBM DB2 or Microsoft SQL Server database, then run the script from the sqlserver-db2 directory.

    For IBM DB2 only, before you run the HelloBPEL SQL script, make the following changes to it:

    • Add this line to beginning of the script:

      CONNECT TO soadb USER am3_ipm USING oracle;

    • Change the following line to specify whatever the actual BPEL connection is in the Imaging Manage Connections section:

      Insert into AXF_SOLUTION_ATTRIBUTES (SOLUTION_NAMESPACE,PARAMETER_KEY,PARAMETER_VALUE) values ('HelloBPEL','BPEL_CONNECTION','test');
  2. Run the insertHelloBPELData.sql script.
  3. With Oracle JDeveloper, open HelloBPEL.jws from following directory:

    • UNIX path:

      MW_HOME/WCC_ORACLE_HOME/axf/drivers/HelloBpel/bpel

    • Windows path:

      MW_HOME\WCC_ORACLE_HOME\axf\drivers\HelloBpel\bpel

    Deploy the process to your BPEL server. For assistance with this task, consult the JDeveloper documentation.

    Note:

    The HelloBPEL sample solution assigns instances to a group named California by default. You need to add the California group to the myrealm security realm through the Oracle WebLogic Server Administration Console.

    If you are using an alternate identity store, such as Oracle Internet Directory, you can change the group assignment by modifying the HelloBpelHumanTask.task file within JDeveloper before deployment.

  4. Access the driver page of the AXF for BPEL web application by using the following URL:
    http://host:port/imaging/faces/Driver.jspx
  5. In the AXF Command Driver screen, enter the following values:

    • Solution Namespace: HelloBPEL

    • Command Namespace: StartHelloBPEL

    • User Name: A valid Imaging user; for example, weblogic

    The preceding Imaging user needs to be part of a group named California. If this group does not exist, then create it, and add the user to the group.

  6. Click Execute Command.
    A response should be displayed in the response screen.
  7. Click Execute Response, and sign in when prompted.

    The AXF Task List screen should be displayed. If there are no tasks in the task list, open the BPEL Console, create a new instance of HelloBPELProcess, and refresh the task list.

Configuring Capture

The Capture System Administrator requires system administration privileges to configure and monitor an Oracle WebCenter Enterprise Capture system environment. The configuration consists of tasks such as starting the Capture Managed Server, assigning roles to Capture users in Fusion Middleware Control, and modifying system-level settings through MBeans.

This appendix explains the configuration tasks in detail.

  • About Completing the Oracle WebCenter Enterprise Capture Configuration
    The Capture System Administrator who performs the installation and initial configuration must have system administration permissions, including access to Oracle Enterprise Manager Fusion Middleware Control and Oracle WebLogic Server. Before anyone can use Oracle WebCenter Enterprise Capture, a system administrator must associate users from the LDAP credential store for the WebLogic Server domain with the Capture roles in Fusion Middleware Control.
  • Completing the Initial Configuration of Oracle WebCenter Enterprise Capture
    The Capture System Administrator performs the initial configuration of Capture in a WebLogic Server domain. In addition to starting the Capture Managed Server, the configuration steps also include assigning roles to users and modifying system-level settings.

Parent topic: Configuring WebCenter Content Settings

About Completing the Oracle WebCenter Enterprise Capture Configuration

The Capture System Administrator who performs the installation and initial configuration must have system administration permissions, including access to Oracle Enterprise Manager Fusion Middleware Control and Oracle WebLogic Server. Before anyone can use Oracle WebCenter Enterprise Capture, a system administrator must associate users from the LDAP credential store for the WebLogic Server domain with the Capture roles in Fusion Middleware Control.

The roles CaptureWorkspaceManager, CaptureWorkspaceViewer, and CaptureUser are automatically added to the default WebLogic Server policy store for the domain. The Capture System Administrator can use the file/XML-based policy store, an Oracle Internet Directory policy store, or an Oracle Database policy store and manage the policy store through Fusion Middleware Control.

Through Fusion Middleware Control, you can also configure system settings and loggers for Capture.

Parent topic: Configuring Capture

Completing the Initial Configuration of Oracle WebCenter Enterprise Capture

The Capture System Administrator performs the initial configuration of Capture in a WebLogic Server domain. In addition to starting the Capture Managed Server, the configuration steps also include assigning roles to users and modifying system-level settings.

Starting the Capture Managed Server

The first step to complete Capture configuration is to start the Capture Managed Servers.

Assigning Roles to Capture Users

Before anyone can use Capture, the Capture System Administrator needs to assign users from the LDAP credential store to the Capture roles in the policy store. You can do this through the Application Roles page in Fusion Middleware Control.

To assign roles to Capture users, see Assigning Capture Roles in Oracle Enterprise Manager in Oracle Fusion Middleware Administering Oracle WebCenter Enterprise Capture.

Modifying System-Level Settings

You can modify system-level configuration settings for Capture, including system properties and SMTP settings for e-mail, through Fusion Middleware Control. The settings on this page configure the Capture MBeans for the domain, which you can also modify with Oracle WebLogic Scripting Tool (WLST) commands.

The following WLST commands also enable you to access or modify system-level settings:

  • listCaptureConfig

  • getCaptureConfig

  • setCaptureConfig

These are online WLST commands that you can use while connected to the Administration Server for the domain. To connect, you need to run the wlst.sh script from the Oracle WebCenter Content home directory.

To modify a Capture system-level setting with a WLST command:
  1. Start the Administration Server for your Oracle WebLogic Server domain.
  2. Sign in to the Oracle WebLogic Server Administration Server.
  3. Navigate to the Oracle WebCenter Content home directory at MW_HOME/WCC_ORACLE_HOME
  4. Run WLST.
    cd common/bin
    ./wlst.sh
  5. Sign in and then enter a custom Capture command:
    wls:/offline> connect() 
Please enter your username :weblogic 
Please enter your password : XXXXXXXXXXXXX 
Please enter your server URL [t3://localhost:7001] 
 :t3://host_name:16401 
Connecting to t3://host_name:16401 with userid weblogic ... 
Successfully connected to Managed Server 'capture_server1' that belongs to domain 
'domainName'. 
 
wls:/domainName/serverConfig> setCaptureConfig('CaptureSystemID','CAPTURE_02')

Attribute 'CaptureSystemID' changed to "CAPTURE_02'
 
wls:/domainName/serverConfig> exit()