Configuring Archival Source

Configuring Archival Source Database

Configure the source Database (DB) from which Data will be archived. The DB is directly used to create summarization and job related data.

Note: Ensure the details are under db: sourceDB: section

Yaml Config Sample:

db:
  sourceDB:
    source: "jdbc"
    connection:
    #
    # Oracle configuration
    #
      url: "jdbc:oracle:thin:@<hostname>:<port>:<service_name>"
      username: "<username>"
      password: "<passwd>"
      poolName: "myoracle"
      initializationFailTimeout: -1
      connectionTimeout: 20000

Refer to https://helidon.io/docs/v4/se/guides/dbclient for more details.

Configuring Archival Source API

Configure the Siebel server Application where EAI component is enabled for the Data Archival to access the Data APIs. The Data APIs in this server is used to query the data that is archived and to delete the data once archived.

Note: Ensure the details are under app: section

• numberOfParallelSubJobs: Number of parallel sub jobs to be run at a time in the helidon Server. This will depend on your hardware.
• batchSize: Number of records to be processed by a sub job as a batch.

Yaml Config Sample:

app:
  numberOfParallelSubJobs: 1
  hostname: <siebel_server_host>
  port: <Siebel_server_port>
  batchSize: 1

Configuring Siebel Security

security: Type of security implemented in Siebel EAI Component. Example: sso

Define the details for the required security type required.

sso: 
    userspec: <SIEBEL_SSO_USERSPEC>
    anonusername: <SIEBEL_USERNAME>

Refer to, https://helidon.io/docs/v4/se/guides/security-oidc for more details on security.

Configuring Archival Target

1. Configure the Archival Targets for the Data Archival. Two types of targets are supported: FileSystem and Database.

   1. Configure the target DBs under archivalTarget: targetDB: section as DB1, DB2, ...

   2. Configure the target FileSystems under archivalTarget: targetFileSystem: section as FT1, FT2, ...

      Note: NFS/FS path that can be accessed from the machine hosting the Helidon server should be provided for targetfileSystem

Yaml Config Sample:

archivalTarget:
  targetDB:
    DB1:
    source: "jdbc"
    connection:
    #
    # Oracle configuration
    #
      url: "jdbc:oracle:thin:@<hostname>:<port>:<service_name>"
      username: "<username>"
      password: "<passwd>"
      poolName: "myoracle"
      initializationFailTimeout: -1
      connectionTimeout: 20000

    DB2:
    source: "jdbc"
    connection:
    #
    # Oracle configuration
    #
      url: "jdbc:oracle:thin:@<hostname>:<port>:<service_name>"
      username: "<username>"
      password: "<passwd>"
      poolName: "myoracle"
      initializationFailTimeout: -1
      connectionTimeout: 20000
  targetfileSystem:
    FT1: "<Path1>"
    FT2: "<Path2>"

Configuring AI Summarization

Configure the Server where Siebel AI Services are set up for AI summarization under ai: section

Yaml Config Sample:

ai:
  hostName: <hostname>
  port : <port>
  compartmentId: "<Compartment ID>"

Refer to Artificial Intelligence (AI) Services for Siebel CRM for AI Setup and configurations.

Configuring AI Summarization Scheduler

Configure the time slot between which the AI summarization job has to be scheduled under aiScheduler: section. Format: HH:MM:SS

Yaml Config Sample:

aiScheduler:
  startTime: "00:00:00"  # HH:mm:ss
  endTime: "00:00:00"    # HH:mm:ss

Configuring Siebel System Preferences

1. Update the HostURL in the Administration - Application > System Preferences.

   • System Preference Name: Data Archive Service URL
   • System Preference Value: https://<host name>:<port name>/
   Note: Update the host name and port name where the siebel-data-archival.jar is running.
2. Restart Siebel Server after adding System preference.