Campaign configurations
To configure Campaign for Cloud Native Unica, make the necessary modifications to the campaign-configMap.yaml file.
To access the campaign-configMap.yaml file, navigate to /unica/templates/ in the Unica charts folder. Open the file and make modifications to the following parameters:
Parameter name | Parameter description |
---|---|
CAMPAIGN_JNDI_NAME | JNDI name for Campaign. |
CAMPAIGN_POOL_NAME | Pool name for Campaign. |
PRODUCT_OPTS_CAMPAIGN | Product specific options for Campaign. |
CAMPAIGN_PRODUCT_NAME | The name assigned for Campaign. |
CAMPAIGN_WAR_NAME | The name of the WAR file. |
CAMPAIGN_APPLICATION_NAME | The name of the main application. For example, Unica. |
CAMPAIGN_DOMAIN_USERNAME | The domain username for Campaign. |
CAMPAIGN_DOMAIN_PASSWORD | The domain password for Campaign. |
USER_DB2_HOST_NAME | The host name of the DB2 user. |
CAMP_MAX_HEADER_SIZE | The maximum size allowed for the header. For example, 8192. |
Parameter name | Parameter description |
---|---|
CAMPAIGN_DATABASE_HOST | Host system details of the system hosting the Campaign database. |
CAMPAIGN_DATABASE_PORT | Port number of the Campaign database. |
CAMPAIGN_DATABASE_NAME | Name of the Campaign database. |
CAMPAIGN_DATABASE_USERNAME | Username to access the Campaign database. |
CAMPAIGN_DATABASE_PASSWORD | Password to access the Campaign database. |
DB2_CLIENT_INSTALL_COMMAND | Command to install the DB2 client on listener pod. |
DB2_CLIENT_INSTALL_COMMAND_SCRIPT | Note: Use the scripts configured on Unica
helm charts to install any other database clients automatically
and seamlessly. Path of the test scripts to install client
on listener pod (/bin/sh/db2.sh). |
DB2_SETUP_FILE | Path of the tar/gz file of client |
DB2_RESPONSE_FILE | Path of response file to install client. |
LD_LIB_PATH | Path to the required shared libraries in the environment configuration script, setenv.sh, for Campaign. |
SETENV_COMMAND1 | Setting the variables for setenv.sh in the listener you can provide the command. |
SETENV_COMMAND2 | Setting the variables for setenv.sh in the listener you can provide the command. |
SETENV_COMMAND3 | Setting the variables for setenv.sh in the listener you can provide the command. |
CAMPAIGN_DS_INITIAL_SIZE | The initial size of the Campaign datasource connection pool. |
CAMPAIGN_DS_MIN_IDLE | The minimum number of idle connections (not connected to a database) in the Campaign datasource connection pool. |
CAMPAIGN_DS_MAX_IDLE | The maximum number of idle connections (not connected to a database) in the Campaign datasource connection pool. Any idle connections, which exceeds the configured value, will be removed from the pool. |
CAMPAIGN_DS_MAX_TOTAL | The maximum number of connections that the Campaign datasource can hold. If the number of connection requests exceed the configured value, the connection will be refused. |
CAMPAIGN_DS_STATEMENT_CACHE_SIZE | Maximum number of statements that can be cached in the Campaign datasource. Statement caching improves performance by caching executable statements that are used repeatedly. |
MARIADB_CLIENT_INSTALL_COMMAND | Command to install the MariaDB client on the listener pod. |
MARIADB_CLIENT_INSTALL_SCRIPT | Note: Use the scripts configured on Unica
helm charts to install any other database clients automatically
and seamlessly. Path of the test scripts to install
database client on the listener pod
(/docker/unica/mariadb.sh). You can write
the set of command in this file to install the client and it is
executed during the startup of the listener
pod.Example
|
ORACLE_CLIENT_INSTALL_SCRIPT | Note: Use the scripts configured on Unica
helm charts to install any other database clients automatically
and seamlessly. Path of the test scripts to install
database client on the listener pod
(/docker/unica/oracle.sh). You can write
the set of command in this file to install the client and it is
executed during the startup of the listener
pod.Example
|
SQLSERVER_CLIENT_INSTALL_SCRIPT | Note: Use the scripts configured on Unica
helm charts to install any other database clients automatically
and seamlessly. Path of the test scripts to install client
on listener pod (/bin/sh/sqlserver.sh). |
USER_DB2_PORT | The port number to access the DB2 database. |
USER_DB2_DB_NAME | The name of the DB2 database user. |
USER_DB2_DB_USER | The username of the DB2 database user. |
USER_DB2_DB_USER_PASSWORD | The password for the DB2 database user. |
ASM_User_For_DB2_Credentials | The asm_admin credentials for DB2
datasource. |
ASM_User_NZ_Data_Source_Name | The asm_admin user configured for the NZ
datasource. |
ASM_User_For_SQLSERVER_Credentials | The asm_admin credentials for SQL Server
datasource. |
ASM_User_SQLSERVER_Data_Source_Name | The asm_admin user configured for the SQL Server
datasource. |
ASM_User_DB2_Data_Source_Name | The asm_admin user configured for the DB2
datasource. |
ASM_User_ORA_Data_Source_Name | The asm_admin user configured for the Oracle
datasource. |
ASM_User_For_ORA_Credentials | The asm_admin credentials for the Oracle
datasource. |
USER_ORA_DB_USERNAME | The username of the Oracle database user. |
USER_ORA_DB_USER_PASSWORD | The password of the Oracle database user. |
USER_ORA_PORT | The port number of the of the configured database user. |
USER_ORA_SID | The SID details of the Oracle user. |
ASM_User_NZ_Data_Source_Name | The asm_admin user configured for the NZ
datasource. |
ASM_User_For_NZ_Credentials | The asm_admin credentials for the NZ
datasource. |
USER_NZ_DB_USERNAME | The username of the NZ database user. |
USER_NZ_DB_USER_PASSWORD | The password for the NZ database user. |
USER_NZ_HOST_NAME | The host name of the NZ database user. |
USER_NZ_PORT | The port number to access the NZ database. |
USER_NZ_DB_NAME | The database name of the NZ database user. |
USER_MARIA_HOST_NAME | The host name of the MariaDB database user. |
USER_SQLSERVER_DB_NAME | The database name of the SQL Server database user. |
USER_SQLSERVER_HOST_NAME | The host name of the SQL Server database user. |
USER_SQLSERVER_PORT | The port number to access the SQL Server database. |
USER_SQLSERVER_NAME | The host name of the SQL Server database user. |
USER_SQLSERVER_USER | The username of the SQL Server database user. |
CAMPAIGN_DSN_NAME | The dbanme value of the respective
database. |
ORACLE_ODBC_DRIVER | The path or the location of the Oracle ODBC driver on your system. |
DB_TEMPLATE | The name of the database template used. This is used for configuring ODBC connection in Oracle. |
Parameter name | Parameter description |
---|---|
CAMPAIGN_URL | The URL to access Campaign. |
CAMP_HOST_NAME | The system host name of Campaign. |
CAMP_MANAGEMENT_PORT | The management port number for the Campaign system. |
CAMP_MANAGEMENT_HTTPS_PORT | The management HTTPS port number for the Campaign system. |
CAMP_AJP_PORT | The AJP port number for the Campaign system. |
CAMP_HTTP_PORT | The HTTP port number for the Campaign system. |
CAMP_HTTPS_PORT | The HTTPS port number for the Campaign system. |
CAMP_RECOVERY_ENV_PORT | The recovery environment port number of the Campaign system. |
CAMP_STATUS_MANAGER_PORT | The status manager port number of the Campaign system. |
CAMP_MIN_HEAP | The maximum heap size allocated for Campaign. |
CAMP_MAX_HEAP | The maximum heap size allocated for Campaign. |
Parameter name | Parameter description |
---|---|
LISTENER_HOST_NAME | The hostname of the Listener. |
LISTENER_PORT | The port number of the Listener. |
LISTENER_TYPE | Specify the type of Listener. |
CLUSTER_DOMAIN | Define the cluster domain. For example, listener.default.svc.cluster.local. |
SSL_FOR_PORT2 | SSL server port 2. |
SERVER_PORT2 | Server port 2. |
MASTER_LISTENER_PRIORITY | Define the Listener priority. |
LOAD_BALANCE_WEIGHT | The load balance weight of the Listener. |
CAMP_HOSTNAME | The host name of the Campaign system. |
CAMPPORT | The deployment port for Campaign. |
CLUSTER_DEPLOYMENT | Set TRUE if clustered deployment is supported or
FALSE if clustered deployment is not
supported. |
ORACLE_CLIENT_SETUP_FILE_EXTRACT_COMMAND | The command to extract the Oracle tar/gz client setup file |
DB2_CLIENT_SETUP_FILE_EXTRACT_COMMAND | The command to extract the DB2 tar/gz client setup file |