Initialize Profile and Feed Metadata

Create baseline profile and feed metadata by using supported Detect CLI commands.

Before you begin

  • Before creating metadata, complete post-install configuration and verify application server settings in Post Installation Configurations on Application Servers.
  • Validate configuration files and environment values.
  • Verify runtime environment values in setenv.sh or setenv.bat, including a valid JDK17 path for JAVA_HOME and correct installation paths for product components.
  • Create sample json files for baseline profile, feed application metadata, feed mapper and destinations endpoints. refer to Unica Detect Admin's Guide for sample json templates.

About this task

Complete the following steps to initialize profile, feed application, feed parser mappings, and destination metadata.

Procedure

  1. Validate configuration files and environment values. Verify that CLI connection properties in detect-cli.properties are updated for your Platform and Detect endpoints and credentials.
    Detect CLI Properties
    Path: DetectHome/tools/detect-cli.properties

    Ensure these fields are pre-filled:

    • platform.baseUrl: Unica Platform URL.
    • detect.baseUrl: Detect Server REST API URL.
    • platform.clientId: Generated ASM client ID.
    • platform.clientSecret: Generated ASM client secret.
    • platform.userid: Authorized manager username (e.g., asm_admin).
  2. Run this command to confirm CLI initialization is successful before creating metadata, and to view help menu options in the response.
    Windows:
    CliTool.bat --help
    Linux :
    ./CliTool.sh --help
  3. Create the baseline profile.
    Windows
    CliTool.bat create-profile -f "<profile_payload.json>"
    Linux
    ./CliTool.sh create-profile -f "<profile_payload.json>"
  4. Create feed application metadata.
    Windows
    CliTool.bat create-feed-application -f "<feed_application_payload.json>"
    Linux
    ./CliTool.sh create-feed-application -f "<feed_application_payload.json>"
  5. Create feed parser mappings in bulk.
    Windows
    CliTool.bat create-feed-parser-mappings-bulk -f "<feed_parser_mappings_payload.json>"
    Linux
    ./CliTool.sh create-feed-parser-mappings-bulk -f "<feed_parser_mappings_payload.json>"
  6. Create a destination endpoint.
    Windows
    ./CliTool.bat create-destination -f "<destination_payload.json>"
    Linux
    ./CliTool.sh create-destination -f "<destination_payload.json>"
  7. Validate templates and connector metadata. 
    ./CliTool.sh get-all-message-templates
./CliTool.sh get-all-connector-templates
    Important: Use only module-supported command syntax as documented in the Feed Application, Feed Parser Mapping, and Destination command references.
  8. Before starting the engine, update port number for seed-nodes parameter in the <DetectHome>/conf/engine/pekko/application.conf file.
    For example: 
    cluster {
seed-nodes = ["pekko://DetectEngine@BLMYCLDTL16181:11111"]
    Note: Use the same port number to start or stop the engine.
  9. To run the engine in background, run the command:. 
    ./engineScript.sh start <port>
  10. To stop the Detect engine, run the command: 
    ./engineScript.sh stop <port>