Content

Sharing documents with users outside of your organization

Sharing documents
Viewing shared documents – external users
Administration
Planning
Roadmap for configuring external content sharing
Setting up your external LDAP realm
Configuring WebSphere Application Server for external share
Configuring FileNet P8 Platform
Configuring IBM Content Navigator
Additional Content Platform Engine configuration
Configuring external share in a container environment

Sharing documents

IBM Content Navigator users can share content with external users. Note that to share a document, you must be the owner of the document and also have the Manage permissions privilege.

To share a document:

1. Select the document that you want to share, right-click, and click Share.

2. In the Share dialog, look up the name of the external user recipient. The eligible users are provided for selection as you type. You can enter more than one recipient.

3. Add a subject and a personal message to explain the shared content.

4. Set the view and download permissions and the optional expiration settings. After the expiration date passes, the shared document is no longer visible to the recipient. If no expiration date is set, the recipient has access to the document indefinitely.

   The best practice is to set an expiration date at the time of the share. At a later date, you can also add or change an expiration date on a share.

   If you do not set an expiration date and the share is no longer needed, the issuer or supervisor must delete the share manually.

5. After you complete all the settings, click Send.

As an internal user, you can also review the content that you have already shared with external users.

To view what you have already shared

1. From your repository desktop, in the feature drop-down menu, click Share.
2. From the My Shares list, click a document to see what users you have shared the content with, view their permissions and expiration date settings, and make updates to the share settings.

Note: If you re-share a document with a user for a second or subsequent time, the user does not receive another notification of the share. However, changes you make to the view and download permissions or expiration details are updated on the share.

If you select an expiration date for a shared document, the system automatically removes the privileges to the document for the external users. Otherwise, the share has to be manually revoked when the document no longer needs to be shared.

Viewing shared documents – external users

The external users receive an email that includes a link to accept the share. When the user clicks to accept the share, the desktop configured by the IBM Content Navigator administrator opens. The desktop provides two tabs

• Shared with Me
• Pending Shares

New shares are listed in the Pending Shares tab. The user must accept the share to see the document.

To view a list of all of the documents that have been shared with them, users can click the All link in the breadcrumb. Clicking on a document in the list opens the  document.

Administration

An administrator can configure the IBM Content Navigator environment to enable the sharing of content from a FileNet P8 Platform repository with users that are external to your organization. The configuration tasks include defining a special desktop that will be used by the external users to access any shared content.

After the administrator configures the environment to support external sharing, the internal users can specify content that they want to share with external users. An email template is used to generate a message to the external user with a link to accept the content share. The share issuer can choose the level of access the external user has to the content, and how long the shared content will be available to the user. The external user can also see a list of all the content that has been shared with them.

Planning

Note the following requirements and constraints for configuring external sharing:

• You must designate or create a separate, customer-managed LDAP directory realm for identifying the external users. The internal and external LDAP directory realms must be federated. The directory realms can be any of the types that are supported in a FileNet P8 Platform environment. However, because of the need for two separate and distinct directory configurations, IBM Virtual Member Manager is not supported.
  • The LDAP short name for a user must be unique across all LDAP realms that are configured in your domain. For details, see the following information: https://www.ibm.com/support/knowledgecenter/en/SSNW2F_5.5.0/com.ibm.p8.security.doc/p8psd000.htm
  • Your dedicated external LDAP directory realm must include the mail attribute for users, including the email address of the user.
  • It is recommended that the LDAP directory realm include settings to map the User Display Name attribute to displayName.
• You cannot use external share in an IBM Content Navigator 3.0.4 instance that requires use of the Task Manager, because Task Manager requires JAX-RS 1.1 and External Share requires JAX-RS 2.0. If you need both capabilities, configure each feature in a separate instance of IBM Content Navigator.

  In Content Navigator 3.0.5 and later, Task Manager also uses JAX-RS 2.0 and there is no longer a requirement to configure separate Content Navigator instances for Task Manager and External Share.

• WebSphere Application Server V9.0 with JAX-RS 2.0 configured is required for external share. For more details about configuring JAX-RS 2.0, see the following information: https://www.ibm.com/support/knowledgecenter/SSEQTP_9.0.0/com.ibm.websphere.base.doc/ae/rwbs_jaxrs2.0_goal_deploying.html
• Document share supports only view or view and download operations for external users.
• Accessibility constraint – Users relying on keyboard navigation will not be able to use Shift + F10 to access the context menu on Windows 10 systems. Users must navigate to the action button instead.
• For IBM Content Navigator, external share can only be used on one P8 domain. However, multiple repositories in the domain can be enabled for share.
• For the IBM Content Navigator user interface, the following are not supported for the external desktop:
  • Themes
  • “Classic” user interface style
• External sharing is currently supported with an English user interface only. The feature functionality is available in other locales, but with an English language interface.
• The initial share enablement must be configured by a P8 domain administrator. After the initial enablement, an IBM Content Navigator administrator with object store administration privileges can enable share on additional repositories.
• A separate IBM Content Navigator external desktop is required for each repository that is enabled for use with the external share feature.

Roadmap for configuring external content sharing

To use external share, the following prerequisite updates must be installed and deployed:

• 5.5.1.0-P8CPE-IF001
• 3.0.4.0-ICN-IF001

To enable the sharing of content with external users, perform the following high level steps. Detailed information is provided in the rest of this document. Note that not all the steps apply to container deployments, see Configuring external share in a container environment for further details.

• Configure or designate a customer-managed LDAP directory realm to manage your external users. Note that FileNet P8 Platform and IBM Content Navigator do not manage this LDAP realm. See Setting up your external LDAP for additional information.
• Ensure that your application server is correctly prepared for external share. These settings include adding the external LDAP realm and configuring LTPA keys. (LTPA keys are not needed in container deployments.) See Configuring WebSphere Application Server for external share for additional information.
• Configure external share settings on FileNet P8 Platform by using the Administration Console for Content Platform Engine. Settings in the administration console include configuring the additional LDAP directory realm for external users and properties that are specific to external content sharing. See Configuring FileNet P8 Platform for additional information.
• Configure IBM Content Navigator to allow external shares. See Configuring IBM Content Navigator for additional information.
• Enable external shares by installing the Share plugin, enabling the P8 repository, and setting appropriate permissions.
• Set up the external sharing capability for users by adding the share menu actions, creating a custom desktop for external users, and optionally customizing the email template for sharing. See Configuring IBM Content Navigator .
• You will also need to make IBM Content Navigator available to the external users, outside of the firewall. This task is typically done by a network administrator.

Setting up your external LDAP realm

Set up or designate an LDAP realm that is separate from the directory realm that manages internal users for your organization. The LDAP server can be any type that is supported by FileNet P8 Platform and IBM Content Navigator. However, because of the need for two separate and distinct directory configurations, IBM Virtual Member Manager is not supported.

If you choose to use the same LDAP server (or the same set of LDAP servers set up for replication) to host both internal and external user organizations, make sure that

• The internal and external user subtrees are not in any ancestor-descendant relationship.
• The two subtrees, if they stem from a single LDAP domain root, are independent of one another.
• The external realm name is the same for both the Content Platform Engine and IBM Content Navigator installations.
• The external realm name is different from the internal realm name.

You use Administration Console for Content Platform Engine (ACCE) to configure the external LDAP.

Remember to include the following requirements in your LDAP setup:

• The LDAP short name for a user must be unique across all LDAP realms that are configured in your domain. For details, see the following information: https://www.ibm.com/support/knowledgecenter/en/SSNW2F_5.5.0/com.ibm.p8.security.doc/p8psd000.htm
• The internal and external LDAP directory realms must be federated.
• Your dedicated external LDAP directory realm must include the mail attribute for users, including an email address, to support the email notification feature.

It is also recommended that the LDAP directory realm include settings to map the User Display Name attribute to displayName.

Configuring WebSphere Application Server for external share

The external share capability is only supported for WebSphere Application Server V9.0 with JAX-RS 2.0. If you are configuring external share in a container environment, skip this section.

To support external sharing, make or confirm the following configuration modifications on your application server:

• A shared LTPA token is configured for Content Platform Engine and IBM Content Navigator. For details, see the following information: https://www.ibm.com/support/knowledgecenter/en/SSEUEX_3.0.4/com.ibm.installingeuc.doc/eucin016.htm
• On the Content Platform Engine, set the following JVM arguments:

  -DFileNet.WSI.AutoDetectLTPAToken=true

  -Dcom.filenet.authentication.token.userid=sso:ltpa

• The customer-maintained external user LDAP directory realm is associated with the application server. For details, see the following information:

  https://www.ibm.com/support/knowledgecenter/SSNW2F_5.5.0/com.ibm.p8.install.doc/p8pin310.htm

• The HTTPOnly setting is disabled. For details, see the following information:

  https://www.ibm.com/support/knowledgecenter/en/SSEUEX_3.0.4/com.ibm.installingeuc.doc/eucin019.htm

• The IBM Content Navigator external share desktop URL is secured.

  Securing the IBM Content Navigator external share desktop URL is recommended when exposing the feature to the open internet to allow external users access to the desktop.

  Securing the desktop URL can be accomplished in many ways depending on the IT security technology and deployment architecture you are using. At the very edge of your perimeter, most external firewalls have the capability of doing URL filtering to limit access to a specific application URL. Using URL filtering, access from the internet can be limited to the IBM Content Navigator external share desktop configured on an IBM Content Navigator instance installed in the DMZ (i.e., https://server/navigator/?desktop=ExternalShare).

  With this type of configuration, only the Share URL is allowed or forwarded to the web server. Additionally, you can further secure access at the web server level residing in the DMZ to also limit the external share URL by using capabilities in the web server like Apache's rewrite and location capabilities.

  Again, with this web server configuration only the IBM Content Navigator external desktop and the Share URL pattern will be forwarded to the IBM Content Navigator application server residing behind the internal firewall.

Configuring FileNet P8 Platform

You add the external LDAP directory realm  and configure the email server using the Administration Console for Content Platform Engine (ACCE).

Adding the external LDAP directory realm

Provide information about the LDAP directory realm for external users using ACCE.

To add the new LDAP directory realm for external users

1. In ACCE, open the domain, and click the Directory Configuration tab.
2. Click New, and add information about the LDAP directory realm that has been configured for external users.
3. In the Properties, set the value for the Principal Category property to External.
4. Set the value for the Exclude From Authenticated Users property to True.

   This setting prevents external users from accessing any content with the #AuthenticatedUsers permission setting.

Note: The User Display Name attribute is recommended to be set to the LDAP display name. For ADAM, for example, the setting is set to displayName.

Configuring an email server

You configure an email server so that notifications can be sent to external users that content is available to them.

To configure the email server:

1. In the Administration Console for Content Platform Engine (ACCE), open the domain, and click the SMTP Subsystem tab.
2. Click Enable email services.
3. Supply the necessary values for your email server.

Configuring IBM Content Navigator

To make IBM Content Navigator aware of the external user LDAP directory server, add a new "Configure the Connection to Your LDAP Server" task in the IBM Content Navigator Configuration Manager. Then run the new task to configure the external LDAP.

Next, install the plugin to enable the external sharing capability and configure sharing for your repositories as needed.

To install the Share plug-in

1. Log in to the IBM Content Navigator Administration Desktop as a user with FileNet P8 domain administrator permissions.
2. From the desktop, click Plug-ins > New Plug-in.
3. Enter the path to the plugin:
   • On-premises environment (example): /opt/IBM/ECMClient/plugins/sharePlugin.jar
   • Container environment: /opt/ibm/extShare/plugins/sharePlugin.jar
4. Load the plug-in and save your changes.
5. Specify the REST API URL:
   • For an on-premises environment, you can enter either an absolute or a relative URL. For the relative URL, enter /contentapi/rest/share/v1
   • For a container deployment, only an absolute path is allowed, for example, http://icp-host:<external-share-port>/contentapi/rest/share/v1
6. Click the Verify button to ensure that the URL that you specified accesses the REST API.

Notes:

• The IBM Content Navigator URL and the REST API URL must both be either HTTP or HTTPS.
• The context root, by default, is the /contentapi folder in the IBM Content Navigator installation path. If you are not in a container environment, using a relative URL is preferable because that value works no matter where you installed IBM Content Navigator.

To configure a repository for external share

1. In the Repositories list, click the name of the repository where you want to enable sharing, then click Configure Share.
2. Add the appropriate settings for the share configuration
   • External URL: The IBM Content Navigator URL that external users will access for the share desktop.
   • External desktop: Provide a desktop name and ID. A new desktop is created for you. You can also choose an existing desktop, but you must modify the desktop to remove any functions that are not available for external users. For more information, see Creating an external share desktop .
   • Consent agreement: Optionally add the text that share recipients will see when they are invited to accept a content share. To format the message, use HTML tags in the text that you enter.
3. Click OK to complete the repository configuration.

Repositories that are configured for share display a check mark in the listing. If you uncheck a repository, this action does not remove the configuration for the external share capability. Instead, it makes the Share action unavailable for users of that repository. Users who had previously shared content from that repository can still view and monitor their shared content, and external recipients can still access the content that was shared with them before the repository setting was updated.

Adding the share capability in the internal desktop

If you plan to enable external sharing in an existing internal desktop, you must add the Share capability to the desktop.

To update a desktop for Share capabilities:

1. From the Administration desktop, click Desktops.
2. Double-click the desktop where you want to add the Share capability.
3. Click Layouts.
4. Under Desktop Features, check the box for the Share feature.

Note: You cannot add the Share feature to a desktop unless the desktop includes a repository that is configured for Share.

Configuring the share menu action

If you have already created custom context menus for interacting with documents, edit those menus directly to add the Share action as needed. This example updates the default document context menu. Update any menu where you want the Share action included.

To add the Share menu action to your document context menu:

1. In the Administration Desktop, click Menus.
2. Search for and make a copy of the Default document context menu.
3. Provide a name and description for the menu copy.
4. Use the actions tool to add the Share action to the existing menu actions list.
5. From the Administration Desktop, click Desktops and select the internal desktop where you want to add the updated context menu.
6. Click the Menus tab, and locate the Document context menu.
7. Use the drop-down list to select your updated Share context menu.
8. Make these changes to any desktop where you want to include the Share option.

You can repeat these steps to add the Share action to other context menus, such as the Default teamspace content list context menu or the Default attachments document context menu.

Creating an external share desktop

You should configure a desktop with a limited scope for external recipients to interact with their shared content.

This desktop is opened when users log into the web client to view documents that have been shared with them. The Share plug-in must be enabled on this desktop. The desktop must be associated with the IBM Content Navigator web application that the external URL you configured points to, and include only the share enabled repository where the shared documents are stored, and the Share feature interface elements.

It is recommended that you use the External User Layout to limit the features to Share only, and set the Banner tools context menu setting to: Default Share plug-in banner tools context menu.

To configure an external share desktop

1. From the Administration desktop, click Desktops.
2. Double click the desktop that you want to configure for external share, or create a new desktop.
3. Add only the repository that was configured for external share. For external users, only one repository should be available in the external desktop.
4. For Layout, select External User Layout, and select the Share feature. This layout excludes core features like browse and search that external users should not use.
5. On the Menus tab, set the Banner tools context menu setting to Default Share plug-in banner tools context menu.

Additional Content Platform Engine configuration

Configuring security (Recommended)

You can control who can see share instances by selectively granting the share permission. For example, you might want to leave the share permission off large groups like #AuthenticatedUsers, and instead allow only supervisors to see the contents of the share records.

To update the security on Document Share:

1. In the Administration Console for Content Platform Engine (ACCE), navigate to Data Design > Classes > Other Classes > Abstract Persistable > Share > Document Share.
2. Add or remove user and group permissions for the class.

Configuring the sweep policy for Share (Optional)

To enforce the expiration date on shared content, the share feature includes a new sweep and a sweep disposition policy that checks for share instances at specified intervals and takes appropriate actions. You can edit the policy to change the intervals for the sweep actions.

To review and edit the sweep

1. In the Administration Console for Content Platform Engine (ACCE), navigate to Sweep Management > Sweep Policies > Disposal Policies > Share Disposition Policy.
2. On the General tab, review the Filter expression to determine whether you want to update any settings for the following items:

   (DateCreated + TimeSpan(30,'days') < Now() AND ClbShareRecipientResponse=0 AND ClbShareExpiryDate IS NULL) OR(ClbShareRecipientResponse=2 AND ClbShareRecipientResponseDate + TimeSpan(30,'days') < Now() )  OR  (Now() > ClbShareExpiryDate) OR NOT (ClbShareRecipient SATISFIES (Id IS NOT NULL)) OR NOT (ClbShareIssuer SATISFIES (Id IS NOT NULL))

   For example:

   • Rule for pending deletion - Customer has not accepted share. The default is 30 days and can be modified.

     (DateCreated + TimeSpan(30, 'days') &lt; Now() AND ClbShareStatus=0)

   • Rule for rejected status - Customer rejects the share. The default is 30 days and can be modified.

     (ClbShareRecipientResponse=2 AND ClbShareRecipientResponseDate + TimeSpan(30,'days') < Now() )

   • Rule for expired timer – share will be removed. (Removal happens when the sweep is run, not necessarily on the exact time or day.)

     Now() &gt; ClbShareExpiryDate

   • Rule for bad recipient

     NOT (ClbShareRecipient SATISFIES (Id IS NOT NULL))

   • Rule for bad issuer

     NOT (ClbShareIssuer SATISFIES (Id IS NOT NULL))

   Note: As a best practice, if you need to remove an issuer from the LDAP directory server, make sure that all shares are changed to the new issuer first. If you do not, the share records are removed.

3. Save your changes.
4. Navigate to Sweep Management > Policy Controlled Sweeps > Share.
5. If necessary, update the schedule for when the sweep runs. With the default setting, the sweep runs continuously. You can create a schedule if you want the sweep to run less often.
6. Save your changes.

Customizing the email template (Optional)

You can customize the email template that you use for share invitations.

To customize the email template

1. In the Administration Console for Content Platform Engine (ACCE), open the object store.
2. Navigate to Email Templates, then open the email template you want to update.
3. Include any changes or customizations that you want to make, and save your changes. The email template for Share includes the following parameters:
   • HTML_LANG

     Inserts the language code of the locale in which the email is being formatted.  The locale of the share issuer is used when formatting the html text.

     Example: <html ... lang="en" xml:lang="en" ...>

   • HTML_DIR

     Inserts either "ltr" or "rtl" into the html text and is used to support RTL languages.

     Example: <html ... dir="ltr">

   • TRANSACTION_ID

     The Transaction Id that potentially ties multiple documents together being shared at the same time.  This is typically used as part of the accept URL that is specified at the time an administrator enables and configures the share feature but the parameter can also be a part of the email body.

   • ISSUER_NAME

     The name of the person issuing the share or shares.

   • RECIPIENT_NAME

     The name of the person receiving the share or shares.

   • EXPIRATION_DATE

     If there is an expiration date, an appropriately formatted date identifying when the share expires.

   • EXPIRATION_DATE_DISPLAY

     Inserts either "show" or "none" into the html text depending on whether there is an expiration date set.  This can be used to show or hide a section of the html displaying the expiration date.

     Example (with an empty expiration date): <div style="display: none;">This share expires: <span style="color: #a6266e;"></span></p></div>

   • SUBJECT

     The subject specified by the issuer of the share.  This is typically used as the one (and only) parameter of the Subject text of the email but it can also be inserted into the body of the email.

   • MESSAGE

     The message specified by the issuer of the share.

   • COUNT

     The number of documents being shared.

   • RESOURCES

     Some appropriately formatted text with the partial names of the documents being shared.  This is not included in the default email template as it may not be desirable to show the names of the documents until the recipient has accepted the shares.  But this text can be included if the document names are not considered sensitive.

     Example 1: Document One

     Example 2: Document One, Document Two

     Example 3: Document One, Document Two and one other file

     Example 4: Document One, Document Two and 2 other files

   • ACCEPT_LINK

     The URL that if followed by the recipient will accept the shares; This URL is specified at the time an administrator enables and configures the share feature.

   • CONSENT_STATEMENT

     Text that comprises a consent statement that the user agrees to when they accept the shares; this statement is also specified at the time an administrator enables and configures the share feature.

Configuring external share in a container environment

If you are using Content Platform Engine and IBM Content Navigator in a container environment, you must perform many of the same steps to configure your system as described in the earlier section of this notice. You must also take additional configuration steps to enable the feature in the container environment.  The following differences apply for a container environment:

• After you update the IBM Content Navigator and Content Platform Engine containers to the iFix001 level, you must also deploy the additional external share container.
• Before you add the LDAP directory realm for external users to the Administration Console for Content Platform Engine (ACCE) and to IBM Content Navigator using the IBM Content Navigator Configuration Manager, you add it as an XML file in the configuration overrides directory for the containers.
• You configure database information for the external share plugin.
• You configure a cors.xml file in the external share plugin to enable cross origin resource sharing.

Prerequisites

Use the instructions providing in the readmes to deploy the following containers:

• Content Platform Engine 5.5.1 iFix 001 container
• IBM Content Navigator 3.0.4 iFix 001 container
• External Share 3.0.4 iFix 001 container

Make sure that your updated Content Platform Engine and IBM Content Navigator deployments are working together before you deploy the external share container, and then configure external sharing.

Configuring LDAP for a container environment

In the container environment, before you can you add the external user LDAP realm in the Administration Console for Content Platform Engine (ACCE) and in the IBM Content Navigator Configuration Manager, you add the external realm as an additional LDAP.xml file in the configuration overrides directory for each component.

To add the external LDAP directory

1. Navigate to the /configDropins/override directory for your Content Platform Engine container deployment.
2. Create a copy of the LDAP.xml file, for example, LDAPext.xml.
3. Modify the copy of the XML file by adding the details for your external LDAP directory server.
4. Save the updated copy of LDAPext.xml in the overrides directory.
5. Copy the LDAPext.xml file into the /configDropins/override directory for the IBM Content Navigator container deployment.
6. Copy both the original LDAP.xml and the new LDAPext.xml file into the /configDropins/override directory for the external share container deployment.

Important: The two LDAP XML files must be present in the /configDropins/override directory for Content Platform Engine, IBM Content Navigator, and for the external share container. The realm name in the LDAPext.xml file must be the same in each copy, and must be different from the realm name in the original LDAP.xml file.

The steps and requirements for setting up the external-user LDAP directory realm  are the same for on-premises and container environments. Follow the steps in Setting up your external LDAP , then return to complete the container-specific steps that follow.

Configuring the database files

The external share container requires access to the IBM Content Navigator database.  Use the following steps to enable the Share container to access the IBM Content Navigator database.

To add the required database files

1. Copy the following items from the IBM Content Navigator <pvc-icn-dir>/configDropins/override directory:
   • IBM Content Navigator database XML file (ICNDS.xml)
   • JDBCDriver.xml
   • JDBC database drivers
2. Paste the items into the /configDropins/override directory for the external share container.

Configuring the cors.xml file

Cross origin resource sharing (CORS) allows requests from a different URL to be processed by the REST service that is running in the share container, and allows responses to be returned. You enable the resource sharing by updating and adding the cors.xml file to the /configDropins/override directory for the external share container.

To add the cors.xml file:

1. Copy the cors.xml sample file from the following Github location:

   https://github.com/ibm-ecm/container-samples/tree/master/extShare/configDropins/overrides

2. Save the copy to the /configDropins/override directory for your external share container.
3. Edit the allowedOrigins parameter and enter the IBM Content Navigator domain name. The domain name consists of HTTP (non-SSL) or HTTPS (SSL), and the IBM Content Navigator host name and port that matches the requests coming from the client.

   For example:

   <cors domain="/contentapi/rest/share/v1"
   allowedOrigins="http://myicn:9080“
   allowedMethods="GET, DELETE, PUT, POST, OPTIONS"
   allowedHeaders="Connection,Pragma,Cache-Control,Navigator-Client-Build,XSRFtoken,Origin,User-Agent,Content-Type,Content-Length,Navigator-Client-Identity,Accept-Control-Request-Method,Accept-Control-Request-Headers,Accept,Referer,Accept-Encoding,Accept-Language,DNT,Host,Content-Length,Cache-control,Cookie"
   exposeHeaders="Content-Length,Content_Type,Content-Language,X-Powered-By,Date,Allow,Transfer-Encoding,$WSEP,DNT,Access-Control-Allow-Credentials,Access-Control-Allow-Headers,Access-Control-Allow-Max-Age,Access-Control-Allow-Methods,Access-Control-Allow-Origin,Access-Control-Expose-Headers,Connection,Cache-control,Cookie"
   allowCredentials="true"
   maxAge="3600" />

Note: Do not modify any parameter values other than the allowedOrigins value.

You can add both HTTP and HTTPS values for the allowedOrigins value. Use a comma to separate multiple values for the entry. Trailing slashes (/) are not allowed.

After you have enabled the external share container, you can continue to enable the external share capabilities in IBM Content Navigator and Content Platform Engine as described in the previous sections. Start with Configuring FileNet P8 Platform .