Locate
the [appserverdomain]/config/config.xml file and make a backup
copy of it.
In
the WebLogic Server Administration Console, under Domain Structure,
click Environment > Servers and, in the right pane,
click the name of your server.
Click
the Configuration tab and then click Server Start.
Under
Change Center, click Lock & Edit.
(Only for FileNet 4.x)
In the Arguments box, enter the following text, and then click Save.
-Dwasp.location= <configuration files location>
For
example, using a default FileNet Application Engine installation
on a Windows operating system, add this Java option:
-Dwasp.location=C:/Progra~1/FileNet/AE/CE_API/wsi
Locate
the adobe-component-ext.properties file in the [appserverdomain] folder
(if the file does not exist, create it).
Add a new system property that provides the location of these
FileNet Application Engine JAR files:
For Filenet 4.x add
following JAR files.
For
FileNet 5.0 add following JAR files
Jace.jar
javaapi.jar
log4j.jar
pe.jar
stax-api.jar
xlxpScanner.jar
xlxpScannerUtils.jar
Note: Add
the pe.jar file only if your deployment uses the IBMFileNetProcessEngineConnector
service. The new system property should reflect this structure:
[component id].ext=[JAR files and/or folders]
For example, using a default FileNet
Application Engine installation on a Windows operating system, add
the following system property on a new line with no line breaks
and end the line with a carriage return:
Note: The
following text contains formatting characters for line breaks. If
you copy this text to a location outside this document, remove the
formatting characters when you paste it to the new location.
com.adobe.livecycle.ConnectorforIBMFileNet.ext=
C:/Program Files/FileNet/AE/CE_API/lib2/javaapi.jar,
C:/Program Files/FileNet/AE/CE_API/lib2/log4j-1.2.13.jar
(FileNet Process Engine Connector only) Configure the connection
properties for the process engine as follows:
Using
a text editor, create a file with the following content as a single
line and end the line with a carriage return:
RemoteServerUrl = cemp:http://[contentserver_IP]:[contentengine_port]/ wsi/FNCEWS40DIME/
Save the file as WcmApiConfig.properties in a separate folder,
and add the location of the folder that contains the WcmApiConfig.properties
file to the adobe-component-ext.properties file.
For example,
if you save the file as c:/pe_config/WcmApiConfig.properties, add
the path c:/pe_config to the adobe-component-ext.properties file.
Note: The filename is case-sensitive.
If
a custom JAAS configuration file is being used, add the following
lines in the custom JAAS configuration file:
FileNetP8 {weblogic.security.auth.login.UsernamePasswordLoginModule
required authOnLogin=true;};
FileNetP8WSI {com.filenet.api.util.WSILoginModule required;};
FileNetP8Engine
{weblogic.security.auth.login.UsernamePasswordLoginModule required
authOnLogin=true;};
FileNetP8Server
{weblogic.security.auth.login.UsernamePasswordLoginModule required
authOnLogin=true;};
You can determine
whether a custom JAAS configuration file is used from the value
of the
-Djava.security.auth.login.config property in the application server start command.(FileNet
Process Engine Connector only) If your deployment uses the FileNet Process
Engine Connector, do one of these tasks, as applicable to your configuration:
If your deployment uses a custom JAAS file, add the following
line to the custom JAAS file:
FileNetP8 {com.filenet.api.util.WSILoginModule required;};
If your deployment does not use a custom JAAS file, use a
text editor to create a file with the following content:
FileNetP8 {com.filenet.api.util.WSILoginModule required;};
Save
the file as jaas.conf.WSI and add the location of the file as the
following Java option in the WebLogic Server start command:
-Djava.security.auth.login.config=<JAAS file location>
For
example, if you save the file as C:/pe_config/jaas.conf.WSI, add
the following Java option:
-Djava.security.auth.login.config=C:/pe_config/jaas.conf.WSI
Open
the config.xml file and locate the <credential-encrypted>
value for the managed server’s User domain. If there is no value
for this element, open the backup copy of the config.xml file you
create in step 1 and copy the <credential-encrypted> value.
Paste
the value to the new config.xml file, then save and close it.
If the application server is not currently running, start
the server. Otherwise, stop and then restart the server.
Open a web browser and enter this URL:
http://[host]:[port]/adminui
Log in using the default user name and password:
User name:
administrator
Password: password
Click Services > LiveCycle ES3 Connector for IBM FileNet.
Provide all of the required FileNet repository information
and, under Repository Service Provider Information, select IBM FileNet Repository Provider.
If
your deployment uses the optional process engine service, under
Process Engine Settings, select Use Process Engine Connector Service and
specify the process engine settings. For more information, click
the Help link in the upper-right corner of the page.
Note: The credentials that you provide in this step
are validated later when you start the IBM FileNet repository services.
If the credentials are not valid, an error is thrown and the services
will not start.
Click Save and navigate to Services > Applications and Services > Service Management.
Select
the check box next to each of these services and then click Start:
IBMFileNetAuthProviderService
IBMFileNetContentRepositoryConnector
IBMFileNetRepositoryProvider
IBMFileNetProcessEngineConnector (if configured)
If
any of the services do not start correctly, verify the Process Engine
settings.
Do one of the following tasks:
To use the FileNet
Authorization service (IBMFileNetAuthProviderService) to display
content from a FileNet object store in the Resources view of Workbench,
continue with this procedure. Using the FileNet Authorization service
overrides the default LiveCycle authorization and must be configured
to log in to Workbench by using FileNet credentials.
To use the LiveCycle repository, log in to Workbench by using
the LiveCycle super administrator credentials (by default, administrator and password). The
credentials provided in step 16 use the default LiveCycle authorization service
for accessing the default repository in this case.
Restart your application server.
Log in to Administration Console and click Settings > User Management > Domain Management.
Click New Enterprise Domain and then type a domain
ID and name. The domain ID is the unique identifier for the domain.
The name is a descriptive name for the domain.
When
using DB2 for your LiveCycle database, the maximum permitted length
of the ID is 100 single-byte (ASCII) characters or 50 double-byte
characters or 25 four-byte characters. (See “Adding enterprise domains”
in Administration Help.)
Add a custom authentication provider:
Click Add Authentication.
In the Authentication Provider list, select Custom.
Select IBMFileNetAuthProviderService and then click OK.
Add an LDAP authentication provider:
Add an LDAP directory:
Click Add Directory and,
in the Profile Name box, type a unique name, and then click Next.
Specify values for the Server, Port, SSL, Binding,
and Populate page with options. If you select User for
the Binding option, you must also specify values for the Name and Password fields.
(Optional) Select Retrieve Base DN to retrieve base
domain names, as required. When finished, click Next.
Configure the user settings, click Next, configure
group settings as required, and then click Next.
For
details about the settings, click Help link in the
upper-right corner of the page.
Click OK to exit the Add Directory page, and then
click OK again.
Select the new enterprise domain and click Sync Now.
Depending on the number of users and groups in your LDAP network
and the speed on your connection, the synchronization process may
take several minutes.
(Optional) To verify the status of the
synchronization, click Refresh and view the status in the Current Sync State column.
Navigate to Settings > User Management > Users and Groups.
Search for users that were synchronized from LDAP and perform
these tasks:
Select one or more users and click Assign Role.
Select one or more LiveCycle roles and click OK.
Click OK a second time to confirm the role assignment.
Repeat
this step for all users you want to assign roles to. For more information, click
the Help link in the upper-right corner of the page.
Start Workbench and log in using the following credentials
for the IBM FileNet repository:
User name:[username]@[repository_name]
Password: [password]
The
FileNet object store should now be visible in the Resources view
within Workbench. If you do not log in using the username@repository name, Workbench
attempts to log in to the default repository specified in step 16.
(Optional) If you intend to install the LiveCycle Samples
for Connector for IBM FileNet, create a FileNet object store named Samples and
install the samples in that object store.
After
you configure Connector for IBM FileNet, it is recommended that
you see LiveCycle Administration Help for information about configuring
Workbench functions properly with your FileNet repository.
