Content Collector for SAP Applications

You can move a traditional on-premises installation to a containerized deployment. However, note that Content Collector for SAP Applications does not support a hybrid environment; you cannot have a traditional on-premises installation and a containerized deployment working together in synchronization. Nevertheless, you can have both the types of installations as two separate instances.

Before you begin

  • Go through the preparing and configuring processes.
  • Most of your configuration is done during completing the post-deployment tasks.
  • The Content Collector for SAP Applications daemon starts along with your container and enables you to use IBM® Content Navigator to configure and control your Content Collector for SAP Applications instance, unlike the traditional on-premises installation where using the daemon is optional.
  • Containerized Content Collector for SAP Applications only supports using the containerized Content Platform Engineas a repository.

About this task

To configure your Content Collector for SAP Applications instance, you can either import an existing configuration (.ini file) using the Import function in IBM Content Navigator and modify it or create a new one.

When you create a Content Collector for SAP Applications instance, you set the service name. That setup automatically populates most of the container-specific configuration for you.

Perform the following to complete your configuration:

Procedure

  1. Specify your existing SAP server details in the SAP server section of the configuration.
  2. Specify appropriate values in the Logical archives section of the configuration.
  3. Save the configuration.
  4. Click Start to start the Content Collector for SAP Applications instance.