This chapter explains how to complete the initial configuration of Oracle WebCenter Content: Imaging in an Oracle WebLogic Server domain.
This chapter includes the following sections:
Section 6.2, "Configuring the Full-Text Features in the WebCenter Content Repository"
Section 6.5, "Installing and Configuring AXF for BPM and AXF for BPEL"
Before you complete the configuration of Imaging, your system needs to have Oracle WebCenter Content installed and configured. Imaging uses WebCenter Content for its repository.
Your Imaging system will use WebCenter Content 11g as its document repository. For information about configuring WebCenter Content 11g, see Chapter 3, "Configuring Oracle WebCenter Content Applications," Chapter 4, "Completing the WebCenter Content Configuration," and Section 6.1.1.1, "Configuring WebCenter Content 11g to Work with Imaging."
Note:
In a production system, Oracle WebCenter Content applications need to 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 before you complete the configuration of the Imaging Managed Server and before you connect it to the WebCenter Content 11g repository. For more information, see Section 3.9, "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 is given full administrative permissions as well as the user logging in.
To complete the Imaging configuration, you need to perform all of the following tasks that apply to your system:
Starting the Administration server and the WebCenter Content Managed Server, as described in Chapter 10, "Verifying the Oracle WebCenter Content Configuration"
Starting the Imaging Managed Server and Accessing the Web Client
Setting DISPLAY for the Imaging Viewer in a UNIX Exalogic Environment with Solaris 11g
You can configure WebCenter Content 11g as the repository for Imaging.
Note:
You will not be able to import or upload content to the Imaging system unless you have created a repository connection.
WebCenter Content 11g 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 11g 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, as described in Section 10.3, "Restarting a Managed Server," before connecting to Oracle WebCenter Content Server from the Imaging web client, as described in Section 6.1.3, "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 11g manually to work with Imaging:
Start the WebCenter Content Managed Server, as described in Section 10.2, "Starting Managed Servers."
Access Content Server, as described in Section 4.3.1, "Starting Content Server."
Enable the IpmRepository component:
Choose Admin Server from the Administration tray or menu, then Component Manager.
On the Component Manager page, select Integration.
Select IpmRepository, and click the Update button.
This option is selected by default if the Oracle WebLogic Server domain was configured with Fusion Middleware Configuration Wizard. If this option is already selected, you can close the Component Manager without clicking Update or restarting Content Server.
Click the OK button to enable this feature.
Restart Content Server, as described in Section 10.3, "Restarting a Managed Server."
If IpmRepository was already selected, you do not need to restart the server.
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.
For more information, see ”Managing a File Store System” in Oracle Fusion Middleware Administering Oracle WebCenter Content.
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 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 defined and configured in Content Server by an administrator. You cannot use Imaging to create or define a volume.
A Content Server administrator can configure a file store provider. For more information, see ”Configuring the File Store Provider” in Oracle Fusion Middleware Administering Oracle WebCenter Content.
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 disabling the web layout functionality for any file store provider that is configured for use as an Imaging volume.
Caution:
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. For more information, see ”Adding or Editing a Storage Rule” in Oracle Fusion Middleware Administering Oracle WebCenter Content.
After you start the Administration server and the Imaging and WebCenter Content Managed Servers, you can access the Imaging web client.
To access the Imaging web client:
Start the Imaging Managed Server, as described in Section 10.2, "Starting Managed Servers."
Note:
If Oracle WebCenter Content: AXF for BPM is deployed to the domain, proceed to Section 6.5.1, "Configuring and Verifying AXF for BPM," before performing any configuration on the Imaging server.
Access the web client at this URL: http://managedServerHost:16000/imaging
Log in with the administrator user name and password.
Note:
This first user to connect to the Imaging system is registered as the Imaging administrator.
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:
Open a web browser, and navigate to this website:
http://managedServerHost:16000/imaging
Log in with the administrator user name and password.
Navigate to the Manage Connections tray, and choose Create Content Server Connection from the list.
Enter a name for the connection on the Basic Information page and, optionally, a description, and then click Next.
You can change the selections and on the Connection Settings page:
SSL: Selected for secure SSL communications
Server Port: The IDC port of the WebCenter Content instance, 4444 for Imaging by default
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, you will need to configure the Content Server machine name as part of the Content Server Pool.
Click Next.
Enter a Connection Security value for the connection.
Select which users and groups should have permission to access, modify, delete, or grant others access to this connection definition. At least one user or group must have the grant access permission.
Click Next.
At the Summary screen, click Submit.
A connection to a workflow server (Oracle SOA Suite) is required before you import the definition files. This connection will be 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 - 11.1.1.0. When Oracle BPM Suite was installed, it automatically selected Oracle SOA Suite - 11.1.1.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. For more information about the installation and configuration steps for Oracle SOA Suite and Oracle BPM, see the Oracle Fusion Middleware Installation Guide for Oracle SOA Suite and Oracle Business Process Management Suite.
The following procedures describes how to configure a connection to a workflow server and register the connection in your database. For additional information, see ”Creating a Workflow Connection” in Oracle Fusion Middleware Administering Oracle WebCenter Content: Imaging.
If you installed the Oracle SOA Suite for use with Imaging (noted in Section 2.4, "Using the Installer for Oracle WebCenter Content"), 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:
Open a web browser, and navigate to this website:
http://managedServerHost:16000/imaging
Log in with the administrator user name and password.
Navigate to the Manage Connections tray, and choose Create Workflow Connection from the list.
Enter a name for the connection on the Basic Information page and, optionally, a description, and then click Next.
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.
Click Test Connection to verify the settings.
Click Next.
Enter a Connection Security value for the connection.
Select which users and groups should have permission to access, modify, delete, or grant others access to this connection definition. At least one user or group must have the grant access permission.
Click Next.
At the Summary screen, click Submit .
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.
For conversions to work correctly on a UNIX operating system, it 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:
Access the Imaging domain in Fusion Middleware Control at the following 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, supply the user name and password that were specified on the Configure Administrator User Name and Password screen in the configuration wizard.
In the navigation tree on the left, expand WebLogic Domain and the deployed domain.
Right-click IPM_server1, and choose System MBean Browser from the menu.
In the navigation tree on the System MBean Browser page, under Configuration MBeans, close the com.bea folder.
Under Application Defined MBeans, expand the oracle.imaging folder.
Expand the Server: IPM_server1 and config folders.
Click config.
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
Click Apply.
Restart Imaging, as described in Section 10.3, "Restarting a Managed Server."
In an Exalogic environment with Solaris 11g, you need to set the DISPLAY environment variable for the Imaging Viewer to work correctly in basic mode.
To set DISPLAY for the Imaging Viewer in a UNIX Exalogic Environment with Solaris 11g:
Open a new terminal window and run this command:
xhost +
In the Imaging terminal, set the DISPLAY environment variable to the server where Imaging is running and the port, in this format:
servername:port
Restart Imaging, as described in Section 10.3, "Restarting a Managed Server."
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 Oracle Fusion Middleware Administering Oracle WebCenter Content: Imaging.
For additional information about how to import definitions, see Section 6.5.1.2.2, "Importing Definition Files into Imaging."
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 first. 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 Section 4.5, "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. For more information, see ”Configuring System Properties” in Oracle Fusion Middleware Administering Oracle WebCenter Content.
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 his or her 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. Failure to do so would prevent 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 Imaging system security.
Manually create or migrate users and groups to the new external security provider, using utilities as needed.
For more information, see Section 3.9, "Reassociating the Identity Store with an External LDAP Authentication Provider."
Run the refreshIPMSecurity() WLST MBean command.
For more information, see the Oracle Fusion Middleware WebLogic Scripting Tool 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.
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 they are stored. If the server is considered secure, no additional security is necessary. If additional security is required, cached documents can be encrypted, as described in Section 6.4.2, "Encrypting Cached Documents."
To set the Imaging viewer to use cached documents:
Verify that the Imaging Viewer Cache was successfully deployed:
In the WebLogic Server Administration Console, click Deployments under Domain Structure on the left,
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 proceeding.
Enable viewer caching by setting the ViewerCachePath MBean to the location where documents should be cached, using the method described in Section 6.1.5, "Configuring the GDFontPath MBean for a UNIX System." For example, to enable caching on an Imaging system running on a single computer, the relative path imaging/ViewerCache can be used. If no path is set, then caching of documents is disabled.
Note:
The ViewerCachePath MBean should be set to a location available to all servers in the cluster. If the directory path is not available to all servers, then each server will cache documents locally, resulting in multiple instances of the entire cache.
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. Setting ViewerCacheDays equal to 0 (the default) prevents the cache from being purged.
Set the ViewerCacheEnablePrecache MBean to true to cache documents when they are ingested into Imaging (precache) or to false to cache documents when they are first called by the viewer.
You can move the viewer cache to a new location provided the Imaging server is shut down and the new location uses the same file hierarchy as the old location.
Shut down the Imaging server.
Move the cached files to the new location, preserving the file hierarchy.
Set the new path in the ViewerCachePath MBean.
Start the Imaging server.
If additional security is required, Imaging can be configured to encrypt cached documents. Encryption makes additional processing necessary to decrypt a document for viewing and reduces rendering speed. Even if Imaging is configured to encrypt the cached documents, there is a brief period of time during caching when generated documents are not encrypted.
To enable encryption of cached documents:
Add a new password credential to the domain with Oracle Enterprise Manager Fusion Middleware Control:
Select the WebLogic Server domain for Oracle WebCenter Content.
From the WebLogic Domain menu, select Security and then Credentials.
Select the map oracle.imaging. If no map named oracle.imaging exists, click Create Map, enter oracle.imaging for the map name, and then select it.
Click Create Key. Name the key viewer.cache, and select the type Password.
Enter a user name. The user name does not need to exist in any system.
Enter a password, confirm it, and then click OK.
Enable encryption by setting the ViewerCacheEnableEncryption MBean, using the method described in Section 6.1.5, "Configuring the GDFontPath MBean for a UNIX System."
Note:
The password credential must exist on the domain before you set the ViewerCacheEnableEncryption MBean.
Encryption of cached documents can be disabled by setting the ViewerCacheEnableEncryption MBean to false. Subsequent calls to the viewer will cause unencrypted documents to be cached. Any encrypted documents still in the cache can be decrypted and viewed provided the password credential remains in the domain unaltered.
Purging the imaging.jks File If the Password Credential Is Removed or Altered
If the password credential is removed or altered, encrypted documents still cached must be manually purged.
To purge the imaging.jks file:
Shut down the Imaging server.
Delete the cached files from the cache directory.
Delete the imaging.jks file from the cache directory.
Start the Imaging server.
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, as described in Section 2.2.2, "Creating Schemas for Oracle WebCenter Content Applications." Then when the domain is created or extended, you can select AXF for BPM to use it with Imaging, as described in Chapter 3, "Configuring Oracle WebCenter Content Applications."
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 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. Administrators can use these business components to configure and develop integration solutions for WebCenter Content business applications.
For more information, see Section 6.5.1, "Configuring and Verifying AXF for BPM."
AXF for BPEL
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.
For more information, see Section 6.5.2, "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 Oracle Fusion Middleware Administering the Application Adapters for Oracle WebCenter.
Before you configure AXF for BPM with Imaging, you need to install and configure 11gR1 (11.1.1.8.0) 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, the domain will need to be extended 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. Section 6.5.1.1, "Configuring AXF for BPM," describes how to do this. It also describes how to 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.
For verification that the AXF for BPM infrastructure is properly installed and configured, AXF for BPM includes the HelloBPM solution, which uses an Oracle BPM process to verify the BPM integration. Section 6.5.1.2, "Verifying the AXF for BPM Installation," describes how to deploy and use this solution.
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, as Section 6.5.1.1.1, "Oracle Coherence Communications for Imaging Clusters, Multiple Domains, or Multiple Machines," describes. In a single domain, you can set up communications with Oracle Coherence to avoid interference from multicast traffic, as Section 6.5.1.1.2, "Oracle Coherence Communications for a Single Server or Domain," describes.
Set up the Imaging server through the WebLogic Server Administration Console:
The Administration Server should already be running. If not, start the Administration Server for your Oracle WebLogic Server domain, as described in Section 10.1, "Starting the Administration Server."
Log in to the Administration Console.
Under Domain Structure on the left, expand Environment, and click Servers.
In the Servers table, click the Imaging server instance, such as IPM_server1.
Click the Protocols tab.
If the server is in production mode, you need to click the Lock & Edit button in the Change Center on the left before you can make changes on this tab.
Click the HTTP subtab.
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
Save the changes.
If the server is in production mode, you need to activate changes after you save them, unless configuration editing is enabled.
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:
Log in to the Administration Console on the Oracle SOA Suite machine.
Under Domain Structure on the left, expand Services, and click Data Sources.
Choose Generic Data Source from the New menu.
Enter jdbc/IPMDS in the JNDI Name field.
Select your database type in the Database Type list, and click Next.
Configure values for Data Source Properties to match the connection of the same name on the corresponding Imaging server, including using the same schema.
Test the configuration to ensure everything is valid.
Click Finish.
On the Configuration tab of the Summary of JDBC Data
Sources page, click IPMDS.
Click the Targets tab.
Select the name of the Oracle SOA Suite server.
Click Save.
Return to the Configuration tab on the Summary of JDBC Data
Sources page, and click mds-axf.
Click the Targets tab.
Select the name of the Oracle SOA Suite server.
Click Save.
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:
Log in to the Administration Console on the Imaging machine.
Under Domain Structure on the left, expand Services, and click Data Sources.
On the Configuration tab of the Summary of JDBC Data
Sources page, choose Generic Data Source from the New menu.
Enter SOALocalTxDataSource in the Name field.
Enter jdbc/SOALocalTxDataSource in the JNDI Name field.
Select your database type in the Database Type list, and click Next.
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.
Test the configuration to ensure everything is valid.
Click Next to select targets.
Select the name of the Imaging server.
Click Finish.
Create foreign JNDI with the Oracle WebLogic Scripting Tool (WLST):
Change to the WCC_ORACLE_HOME/axf_bpm/scripts directory.
Edit the create-foreign-JNDI.py script using a text editor.
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
Save the file.
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
Configure the AXF for BPM CSF key:
Log in to Oracle Enterprise Manager Fusion Middleware Control.
Navigate to the WebLogic Server domain and right-click the deployed domain (base_domain by default).
In the resulting menu, choose Security and then Credentials.
Create a new map:
Specify the map name, oracle.wsm.security.
Create a new key:
Specify a key name, such as ipmadmin.
Specify a valid administrator user, such as weblogic.
Specify the password.
After you specify the key name, user, and password, click OK.
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, see the Oracle Coherence Developer's Guide.
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:
Open the DOMAIN_HOME/bin/setDomainEnv.sh script in a text editor.
Perform a search for "coherence" to locate any existing settings.
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
Save the settings.
Restart any running Managed Servers on the domain for the changes to take effect.
You can verify the AXF for BPM installation and configuration with the HelloBPM solution, which uses a BPM process. The following sections describe how to deploy and use this solution:
Section 6.5.1.2.2, "Importing Definition Files into Imaging"
Section 6.5.1.2.3, "Accessing the Solution Administration Page"
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:
Set up the database:
Change to the WCC_ORACLE_HOME/axf_bpm/scripts directory.
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:
SOAMachineName:Port
IPMMachineName:Port
CSFKEY
This will insert the data necessary to run the HelloBPM solution.
If the Oracle SOA Suite Managed Server is on a separate host machine from Imaging, the Hello BPM process will need to be manually deployed.
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.
Start up the remaining servers in the following order. For more information about starting the servers, see Section 10.2, "Starting Managed Servers," and Section 10.4, "Using Node Manager with Oracle WebCenter Content."
Weblogic Server Administration Server (should already be running)
Oracle SOA Suite Managed Server
Imaging Managed Server
WebCenter Content Managed Server
Verify that a URI is set on the deployed process:
Log in to Oracle Enterprise Manager Fusion Middleware Control.
Navigate to the Oracle SOA Suite Managed Server, then soa-infra (soa_server1), and then default, and click axfHelloBPM.
In the Component Metrics section, click SalesQuoteEntry.
Click the Administration tab.
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
You can import definition files for tasks into the Imaging server through the Imaging Injector.
To import definition files into Imaging:
Create the connections:
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. For more information, see Section 6.1, "Completing the Initial Imaging Configuration."
In the navigation tree on the left, expand Manage Connections.
Choose 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.
Choose 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 specified in Section 6.5.1, "Configuring and Verifying AXF for BPM,", Step 5, 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.
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 Oracle Fusion Middleware Administering Oracle WebCenter Content: Imaging.
In the navigation tree on the left, expand Tools.
Choose Import Definitions.
Browse to and select the WCC_ORACLE_HOME/axf_bpm/ipm/HelloBPM.xml file.
Click Next.
On the Select Definitions step, select the Action for HelloBPM Application, HelloBPM Input, and HelloBPM Search.
Click Next.
On the Validation step, select Choose New for the Application Security field, and select the Administrators group. Also choose the Administrators group for the Applications, Document Security field, Inputs Security field, and Searches Security field.
For the Workflow field, select Workflow Connection.
Click Submit.
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. For information about creating a group and adding a user to a group, see "Manage users and groups" in the WebLogic Server Administration Console Online Help.
To access administration functions for the solution application:
Open the new driver page:
http://machinename:16000/axf/faces/pages/axfadmin.jspx
Click the Command Driver link, on the left.
Use the following values:
solutionNamespace: SalesQuoteEntry
commandNamespace: StartSalesQuoteEntry
Click the Execute Request button.
Click the Execute Response button.
The Solution Administration page opens. Table 6-1 shows the example parameters for this page.
Table 6-1 Parameters for the Solution Administration Page
| Parameter | Value |
|---|---|
|
|
|
|
|
|
|
|
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. For more information, see Oracle Fusion Middleware Administering the Application Adapters for Oracle WebCenter.
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:
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.
For more information, see ”Enabling Input Agent” in Oracle Fusion Middleware 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.
In the task list, click the newly injected task to view its details in the solution application.
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.
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. For more information, see Section 6.5.2.1, "Configuring the Java Object Cache for AXF for BPEL in Distributed 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
See Section 6.5.2.2, "Verifying the AXF for BPEL Installation and Configuration with HelloWorld."
HelloBpel, a solution that includes a BPEL process to verify the BPEL integration
See Section 6.5.2.3, "Verifying the AXF for BPEL Installation and Configuration with HelloBpel."
For AXF for BPEL in Imaging Managed Servers that run in a cluster, you need to configure a Java Object Cache (JOC) to be distributed to all of the Managed Servers. You can use HA Power Tools from the Oracle WebLogic Server Administration Console to configure the JOC for all of the Imaging Managed Servers that run in distributed mode.
Note:
After configuring the Java Object Cache, restart all affected Managed Servers for the configurations to take effect. For more information, see Section 10.3, "Restarting a Managed Server."
In the following instructions, MW_HOME represents the path to a Middleware home, where Oracle Fusion Middleware is installed, and DomainHome represents the path to the Oracle home for an Oracle WebLogic Server domain.
To configure the Java Object Cache for a cluster of distributed Managed Servers:
Enable HA Power Tools in the Oracle WebLogic Server Administration Console:
Copy the following two WAR files from the MW_HOME/oracle_common/hapowertools directory to the DomainHome/console-ext directory:
powertools-core.war
powertools-configurejoc.war
For example:
cd middlewarehome cp oracle_common/hapowertools/powertools-co* user_projects/domains/base_domain/console-ext/
Restart the Oracle WebLogic Server Administration Server.
For more information, see Section 10.1, "Starting the Administration Server," and Section 10.3, "Restarting a Managed Server."
Access the Oracle WebLogic Server Administration Console (at http://adminServerHost:adminServerPort/console), and click the name of your domain in the left navigation tree.
The HA Power Tools tab appears on the Settings page for the domain.
Configure the distributed cache:
On the Settings page for your domain in the Administration Console, click the HA Power Tools tab.
On the Configure JOC tab, select Configure JOC for Clusters.
In the Cluster Name field, choose a cluster name from the list.
In the Discover Port field, enter the listener port number for the cluster.
In the Hosts field, enter the names of all the Managed Server hosts, separated by commas.
Click the Configure JOC button.
Restart the cluster of Managed Servers.
Verify the JOC distributed cache mode:
From the Middleware home on the host for one of the Managed Servers, run the CacheWatcher utility, as in the following example:
java -classpath oracle_common/modules/oracle.javacache_11.1.1/cache.jar:oracle_common/modules/oracle.odl_11.1.1/ojdl.jar oracle.ias.cache.CacheUtil watch -config=user_projects/domains/base_domain/config/fmwconfig/servers/IPM_server2/javacache.xml
In this example, the class paths for the two JAR files are relative to the current directory (MW_HOME).
The javacache.xml file is the file used by one of the Imaging servers that is participating in the JOC distributed cache. For a distributed Java cache with either virtual or physical IP addresses, the listener address needs to be set in javacache.xml. Each of the files should contain all the distributor location entries but only one <listener-address> entry, set to the same port number for every cache member, as follows:
<listener-address port="portNumber1" host="hostName1"/> <distributor-location ssl="true" port="portNumber1" host="hostName1"/> <distributor-location ssl="true" port="portNumber1" host="hostName2"/> <distributor-location ssl="true" port="portNumber1" host="hostName3"/> <distributor-location ssl="true" port="portNumber1" host="hostName4"/>
Enter the lc command to list the cache information:
INFO: JOC is initialized from oracle.ias.cache.CacheUtil.main, . . .
cache> lc
In the output from the lc command, check that the Distributor Table shows an entry for each member of the distributed cache.
Enter the exit command to stop the CacheWatcher utility.
For more information, see ”Using HA Power Tools” and ”Running CacheWatcher” in Oracle Fusion Middleware High Availability Guide.
Follow these steps to enable the HelloWorld solution:
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;
Access the driver page of the AXF for BPEL web application using the following URL:
http://host:port/imaging/faces/Driver.jspx
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
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.
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:
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');
Run the insertHelloBPELData.sql script.
With Oracle JDeveloper 11g, 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.
Access the driver page of the AXF for BPEL web application using the following URL:
http://host:port/imaging/faces/Driver.jspx
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.
Click Execute Command.
A response should be displayed in the response screen.
Click Execute Response, and log 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.