Provisioning requirements for Unica Campaign, Engage, and UBX

Before administrators can configure the integration, IBM Provisioning must prepare Engage, and UBX for integration. Unica Campaign also requires some configurations for integration.

Information that IBM Provisioning provides to administrators

Administrators who are configuring the integration need the following information, which IBM Provisioning can provide:

  • The host name, SSL port number, and alias of the server that customers use to access IBM Engage. For example: https://engage1.silverpop.com:443. Unica Campaign administrators need this information to configure WebSphere for use with Engage.
  • The Client Refresh Token: This was sent to the Engage Org Admin (the integration user) by email when Engage was provisioned. Unica Campaign administrators need this information to configure data sources.
  • Credentials (login and password) associated with the Engage Client ID, Engage Client Secret, Engage FTP, and Engage Client Refresh Token. Unica Campaign administrators need this information to configure data sources.
  • The UBX API URL that was established for the UBX account. UBX Toolkit administrators need this value to configure the config.properties file (ubx.api.service.url=http://<server-name>:<port>).

The following sections provide details about how each component is provisioned.

Unica Campaign

The following actions are performed by either the IBM Certified Systems Integrator or the Unica Unica administrator:
  • A partition is defined in Unica Marketing Platform for use by an IBM Engage Organization. Example: partition1
  • An integration user (System Administrator account) is defined in Unica Marketing Platform. Example: asm_admin

IBM Engage provisioning

IBM Provisioning team ensures that the following actions are completed for IBM Engage:

  • A primary user (Org Admin) is designated as the integration user. This may or may not be the same integration user that is defined in Unica Campaign.
  • Unica Campaign Integration is enabled for the Unica Campaign partition. During provisioning, an email is sent to the Engage integration user. The email contains the Client Refresh Token, which the Unica Campaign administrator needs to configure a user account and data sources.
  • UBX Integration is enabled for IBM Engage, based on the Marketing Database ID of the IBM Engage Organization.
    Note: If you are using more than one channel, you can provide the database ID for any of the channels. Engage will publish events from all databases to UBX for use in Unica Campaign.
  • Add Account Access is enabled for the Unica Campaign application.

IBM UBX provisioning

IBM Provisioning creates and provisions a UBX account on your behalf.

If you do not have an account, contact the UBX Account Provisioning team by email at ubxprovisioning@wwpdl.vnet.ibm.com .

IBM Provisioning ensures that the following actions are completed for IBM UBX:

  • Unica Campaign is registered as an endpoint.
  • Event types are registered for email.
  • Event types are registered for SMS and Push, if your organization purchased those capabilities.
  • One of the flexible databases for Engage is registered as an endpoint.
    Note: You can register any of the databases that are used for each channel. Engage will publish events from all the available databases that are used in the setup.

Your fully provisioned account includes the following elements:

  • UBX user account, including credentials to log in to the UBX user interface.
  • A URL to call external UBX APIs.
  • An endpoint-level UBX authentication key for Unica Campaign. (Note: An account-level UBX authentication key is not required.)