IBM Content Collector for SAP (ICCSAP) supports Business Automation Content Services on Cloud (BACSoC) as a repository. This document provides the steps for setting up a new ICCSAP server to use this feature.
- Set ICCSAP server for using BACSoC Application Program Interface (API)
- Configure Content Platform Engine (CPE) in BACSoC
- Configure workflow in BACSoC
- Configure ICCSAP server
- Configure ICCSAP server with on-premise ICN
- Download the relevant CPE API package from the BACSoC user portal.
- Follow the Content Platform Engine APIs Getting Started guide from the CPE API package to configure CPE API access to BACSoC using a functional ID.
- Log onto Administration Console for Content Engine (ACCE) with administrator privileges in the BACSoC environment where you want to make the configuration changes and navigate to the Object Store.
- Create a connection point and an isolated region. Refer to creating extra connection points and isolated regions for more information.
- Create a P8 queue inside the isolated region. Refer to configuring workflow queues for more information.
- Create properties in the Property Templates folder under Data Design. Refer to creating properties for the list of properties to be created.
- Create a document class in the Classes folder under Data Design. Refer to step 5 in Configuring FileNet P8 for use with ICCSAP for more information.
- If the archived documents are to be organized in folders, create the required folders. Refer to working with folders for more information.
- Create Subscription. Refer to creating a subscription for more information.
- Create In-basket. Refer to creating in-basket for more information.
- Download the Process Designer tool from the CPE Tools package from the BACSoC user portal.
- Follow the instructions from the Getting Started Guide in the CPE Tools package to set up Process Designer.
- Configure workflow using Process Designer and Process Console. Refer to creating P8 queues and workflows for more information.
|P8USER||<BACSoC functional ID that has access to CPE in BACSoC>|
|P8ODMAIN||<BACSoC CPE Domain Name>|
|OBJECTSTORE||<BACSoC CPE Object Store Name>|
<BACSoC CPE URL>
https://<tenant instance virtual host>.bpm.ibmcloud.com/ecm/<dev|test|run>/wsi/FNCEWS40MTOM/?useBasicAuth=true
|DEFAULT_P8DOCCLASS||<BACSoC CPE Document Class>|
|DEFAULT_FOLDER||<BACSoC ICCSAP Default Path>|
|P8DOCCLASS||<BACSoC CPE Ddocument Class>|
|PE_USERID||<BACSoC functional ID that has access to CPE in BACSoC>|
|PE_CONNECTPOINT||<BACSoC Connection Point>|
|PE_QUEUENAME||<BACSoC CPE Queue>|
|REPINFOCLASSES||<BACSoC CPE Document Class>|
Point to the following JAR files that are extracted from the BACSoC CPE API package:
- Configure the ICCSAP server instance in on-premise ICN. Refer to getting started with configuration feature for more information.
- Use the Web Service Index (WSI) endpoint of BACSoC CPE in the logical archives section.
- Configure Archiving Profile, Document Profile, and Index Profile. Refer to basic and advanced functions for more information.
- Run Archiving, Document Linking, and Index Transfer tasks.
05 November 2019