System settings

system.name

This is a mandatory property. It specifies the name of the system, e.g. Test System /Productive System / Demo / Poad etc.
Blanks will be replaced with _. Best practice: use 0-9A-Za-z.-

filestorage.dir.shared

Folder which has to be accessible by each Product 360 server. In case of a single server system, the folder does not have to be a shared one

filestorage.default

Default file storage implementation. Currently only SMB is available. SMB stores the files using the SMB file protocol

filestorage.import

File storage implementation for import files, default is also SMB

filestorage.import.path

Path for the import files used by the SMB file storage implementation

filestorage.mime

File storage implementation for mime files, default is also SMB. Applies only to the Classic Media Asset Provider.

filestorage.mime.path

Path for the import files used by the SMB file storage implementation. Applies only to the Classic Media Asset Provider.

filestorage.export

File storage implementation for export files, default is also SMB

filestorage.export.path

Path for the export files used by the SMB file storage implementation

filestorage.shared

File storage implementation for various shared files, default is also SMB

filestorage.shared.path

Path for various shared files used by the SMB file storage implementation

upload.root.local

Path for the service api file upload

filestorage.dataquality

File storage implementation for data quality (DQ) files, default is also SMB

filestorage.dataquality.path

Path for the data quality (DQ) files used by the SMB file storage implementation

filestorage.bpm

File storage implementation for Informatica BPM (Workflow) files, default is also SMB

filestorage.bpm.path

Path for Informatica BPM (Workflow) files used by the SMB file storage implementation

queue.default.type

The message queue type which will be used. Currently only type "ActiveMQ" is supported

queue.default.writer.count

Number of threads which can write on the queue

queue.default.consumer.count

Number of threads which can read from the queue

queue.default.url

The base url and port to access the message queue. For example: tcp://localhost:61616

queue.default.username

Username to authenticate against the message queue

queue.default.password

Password to authenticate against the message queue

queue.default.message.format

Message format which will be used for writing messages into the queue. Possible values are: "XML" or "JSON"

queue.default.label

Human readable label to display the queue in Product 360

queue.default.name

Technical name to identify the queue by Product 360 and third party applications

queue.default.selector

(optional) String which can be used to configure which messages are consumed. Other messages are left in the queue for consumption by other consumers. Eg. "JMSPriority=1" (consumes only messages that have priority 1), "WorkflowName=BPM1" (consumes only messages that have the header value 'WorkflowName' set to 'BPM1').

Note: ActiveMQ assumes any value that starts with 'JMS' to be a JMS header.

queue.default.delivery.delay

Defines the duration [ms] after that the message will be made available to consumers to the message queue. Default is 50 [ms] in a multi server environment and 0 in a single server environment. This allows value changes to the persistence to propagate to all server nodes before e.g. a workflow instance is started.
Note: This setting needs the message queue server to have scheduling support enabled. (This is not default)

queue.batchapi.type

The message queue type which will be used. Currently only type "ActiveMQ" is supported

queue.batchapi.writer.count

Number of threads which can write on the queue

queue.batchapi.consumer.count

Number of threads which can read from the queue

queue.batchapi.url

The base url and port to access the message queue. For example: tcp://localhost:61616

queue.batchapi.username

Username to authenticate against the message queue

queue.batchapi.password

Password to authenticate against the message queue

queue.batchapi.message.format

Message format which will be used for writing messages into the queue. Possible values are: "XML" or "JSON"

queue.batchapi.name

Technical name to identify the queue by Product 360 and third party applications (P360_BATCH_API)

queue.batchapi.label

Human readable label to display the queue in Product 360 (Batch API)

queue.batchapi.delivery.delay

Defines the duration [ms] after that the message will be made available to consumers to the message queue. Default is 10000 [ms] in a multi server environment and 0 in a single server environment. This allows value changes to the persistence to propagate to all server nodes before e.g. a workflow instance is started.
Note: This setting needs the message queue server to have scheduling support enabled. (This is not default)

infa.bpm.base.url

REST The base url to the Informatica BPM instance in the form http://[server]:[port]/active-bpel

infa.bpm.workflows.path

REST The workflows path. Will be used together with the property infa.bpm.base.url to find the endpoints

infa.bpm.user

REST The username for accessing the Informatica BPM instance. Only required if basic authentication on BPM side is configured

infa.bpm.password

REST The password for accessing the Informatica BPM instance. Only required if basic authentication on BPM side is configured

com.heiler.ppm.bpm.server/proxy

REST QUEUE Allows to track any call from the server to the Informatica BPM system using a proxy like Fiddler web debugger, example is localhost:8888, this property is disabled by default

infa.bpm.queue.jms.connection.username

REST The username for accessing the ActiveMQ service

infa.bpm.queue.jms.connection.password

REST The password for accessing the ActiveMQ service

infa.bpm.queue.jms.queue.suffix

REST A suffix that will be appended to the default queue name ("infa.bpm"). The suffix can contain characters a-z, 0-9

infa.bpm.trigger.queue.ids

QUEUE Comma separated list of queue ids of all queues which will be available in the trigger configuration. The first queue in this list is representing the default response queue, which is used e.g. if queue messages do not specify any queue id. Queue configuration settings are described in the "Informatica Queue Settings" section where "default" can be exchanged with any queue id.

infa.bpm.consumer.serviceapi.queue.ids

QUEUE Comma separated list of queue ids on which a service API consumer is applied to. Each queue consumer can have its own settings regarding thread count and message selector, which also allows to define multiple consumer on the same physical queue with different message selectors and different thread counts.

inbox.hotfolders

Local folder in which the incomming files should be placed, shares are not supported.

inbox.processingfolder

inbox.archivefolder

Local folder of the processed inbox files, shares are not supported

inbox.errorfolder

Local folder of the failed files, shares are not supported

license.customer.file.local

Local path to the license file. Please contact the Informatica Partner Management to obtain a license file.

license.customer.key

Appropriate customer key (in case of multiline keys, use backslash at the end of the line)

mime.defaultProvider

Identifier of the media asset provider. Possible values are HLR which corresponds to the Classic Provider or HMM for the Product 360 - Media Manager. Default is HLR

repository.default.language

The default language of the repository regarding all language specific aspects like e.g. default logical key language. Possible values: Key synonyms of the corresponding language entries defined in the repository enumeration "Enum.Language", e.g. "de" or "en_US" - default is German, if property does not exist.

mail.host

Host name of the e-mail server

mail.port

If the mail server uses the standard port for the protocol, this property can be left empty.

mail.protocol

E-mail protocol used, currently only SMTP is supported

mail.user

If the e-mail server requires authentication, then the properties "mail.user" and/or "mail.password" must be set.

mail.password

context.sessioninactiveinterval

http session timeout sec. if not set no timeout is defined

http.client.proxy

The base URL of the reverse proxy (e.g. Apache WebServer). Mandatory if web links used in email notifications.

fulltextsearch.enabled

Full-text search can be enabled (default) or disabled by setting either true or false.
If the full-text search is enabled, ensure you setup the Elasticsearch integration properties.

fulltextsearch.rest.url

URL path to the Elasticsearch REST server.

E.g. fulltextsearch.rest.url = http://localhost:9200,http://localhost:9201

fulltextsearch.rest.user

Login name of the Elasticsearch REST server.

fulltextsearch.rest.password

Login password of the Elasticsearch REST server.

fulltextsearch.rest.allow.self-signed.certificate

Allows self-signed certificate only if you use https.

audittrail.rest.url

URL path to the Elasticsearch REST server.

E.g. audittrail.rest.url = http://localhost:9200,http://localhost:9201

audittrail.rest.user

Login name of the Elasticsearch REST server.

audittrail.rest.password

Login password of the Elasticsearch REST server.

audittrail.rest.allow.self-signed.certificate

Allows self-signed certificate only if you use https.

audittrail.mode

Audit trail can be set up with the below modes -

audittrail.installation.type

Audit trail can have below installation types -

audittrail.threadpool.size

The maximum number of threads available for audit trail processors.

This property should have a value that is the same as db.default.pool.maxPoolSize

audittrail.backup.restoration.mode

This setting will synchronize the Product 360 records in the relational database and their corresponding audit trail data in Elasticsearch.

Default: false

NOTE: Set to "true" only when Product 360 - Server starts after recovering from a disaster.

db.default.type

MSSQL
This property should never be changed!

db.default.server

The host name of the Microsoft SQL Server;
Change this in case you have a separate database server

db.default.port

Port of the Microsoft SQL Server instance, usually this is 1433

db.default.user

User name of the database user

db.default.password

Password of the database user

db.default.dir

Base folder for the database schema and database transaction log files (also used by the database setup)
Note: This folder needs not to be local to the application server but to the database server!

db.default.dir.data

Folder for the database schema files (*.mdf) Note: This folder needs not to be local to the application server but to the database server!

db.default.dir.log

Folder for the transaction log files (*.ldf) Note: This folder needs not to be local to the application server but to the database server.

db.default.data.size

Default size in MB allocated for a database schema; adapt this setting to your needs

db.default.data.size.growth

Default increment value in MB allocated when space for a database schema is insufficient; adapt this setting to your needs

db.default.log.size

Default size in MB allocated for a database transaction log file; adapt this setting to your needs

db.default.log.size.growth

Default increment value in MB allocated when space for a database transaction log file is insufficient; adapt this setting to your needs

Default increment value in MB allocated when space for a database schema is insufficient; adapt this setting to your needs

db.default.schema.prefix

Usually, this property needs not to be changed. The common prefix for all Product 360 - Server schemas; it must be in capital and start with a latin character

db.default.schema.suffix

Usually, this property needs not to be changed. The common suffix for all Product 360 - Server schemas; it must be in capital, and start with a latin character
This property is helpful to distinguish between productive and test schemas (e.g. _PRO and _TEST)

db.default.debug.show_sql

Usually, this property needs not to be changed. Generated SQL statements during runtime will be shown in the log file. This is a debugging feature which will slow down the application drastically if turned on.

db.default.rowPrefetchSize

Affects the default prefetch size which is especially important for mass data retrival. In SQL Server there is usually no need to change that.

db.default.pool.hibernate.dialect

The corresponding dialect for your MSSQL version

For MSSQL 2016: com.heiler.ppm.persistence.db.internal.dialect.SQLServer2016

For MSSQL 2014: com.heiler.ppm.persistence.db.internal.dialect.SQLServer2012

db.default.type

ORACLE
Never change this property!

db.default.database

Oracle Service Name

db.default.server

The host name of the Oracle server;
change this in case you have a separate database server.

db.default.port

Port of the Oracle instance, usually this is 1521

db.default.password

Password for the created schema users

db.default.dir

Base folder for the database schema and database transaction log files, used by the database setup too
Note: This folder needs not to be local to the application server but to the database server.

db.default.dir.data

Folder for the database schema files
Note: This folder needs not to be local to the application server but to the database server.

db.default.dir.temp

Folder for the database transaction log files
Note: This folder needs not to be local to the application server but to the database server.

db.default.dir.index

Folder for the index tablespaces
Note: This folder needs not to be local to the application server but to the database server.

db.default.data.size

Default size in MB allocated for a database schema; adapt this setting to your needs

db.default.data.size.growth

Default increment value in MB allocated when space for a database schema is insufficient; adapt this setting to your needs

db.default.temp.size

Default size in MB allocated for a database transaction log file; adapt this setting to your needs

db.default.temp.size.growth

Default increment value in MB allocated when space a transaction log file is insufficient; adapt this setting to your needs

db.default.index.size

Default size in MB allocated for an index tablespace; adapt this setting to your needs

db.default.index.size.growth

Default increment value in MB allocated when space for an index tablespace is insufficient; adapt this setting to your needs

db.default.schema.prefix

The common prefix for all Product 360 - Server schemas; it must be in capital letters! Note that the resulting tablespace name (prefix + <MAIN|MASTER|SUPPLIER> + suffix) must not be longer than 24 characters.

db.default.schema.suffix

The common suffix for all Product 360 - Server schemas; it must be in capital letters! Note that the resulting tablespace name (prefix + <MAIN|MASTER|SUPPLIER> + suffix) must not be longer than 24 characters.
This property is helpful to distinguish between productive and test schemas (e.g. _PRO and _TEST).

db.default.debug.show_sql

Generated SQL statements during runtime will be shown in the log file. This is a debugging feature which will slow down the application drastically.

db.default.rowPrefetchSize

Affects the default prefetch size which is especially important for mass data retrival.
This value might be modified in case you have a lot of memory. The oracle driver is allocating the complete, theoretically needed memory for a single round trip.
In case you run into memory problems because of the Oracle database access, you might want to decrease this property. See also the How to enable Java Management Extensions (JMX).

db.default.pool.hibernate.dialect

The corresponding dialect for your Oracle version.
Currently only one value, no need to change.

com.heiler.ppm.persistence.db.internal.dialect.Oracle12c

db.default.pool.statementCacheSize

The size of the underlying SQL statement cache. Increasing this value might help increasing performance however it will also lead to more memory consumption on the database server.

db.default.pool.connectionTimeout

The maximum number in milliseconds that the appliaction will wait for a connection from the pool (lowest acceptable connection timeout is 250 ms).
If this time is exceeded without a connection becoming available, a SQLException will be thrown.

Default: 2000 (2 seconds)

db.default.pool.idleTimeout

Controls the maximum amount of time in milliseconds that a connection is allowed to sit idle in the pool. This setting only applies when minPoolSize is defined to be less than maxPoolSize.
Idle connections will not be retired once the pool reaches minPoolSize connections.

Whether a connection is retired as idle or not is subject to a maximum variation of +30 seconds, and average variation of +15 seconds. A connection will never be retired as idle before this timeout.
A value of 0 means that idle connections are never removed from the pool. The minimum allowed value is 10000ms (10 seconds).

Default: 60000 (1 minute)

db.default.pool.minPoolSize

Controls the minimum number of idle connections that will constantly be maintained in the pool.

Default: 5

db.default.pool.maxPoolSize

Controls the maximum size that the pool is allowed to reach, including both idle and in-use connections. Basically this value will determine the maximum number of actual connections to the database.
A reasonable value for this is best determined by observing the corresponding environment.

When the pool reaches this size, and no idle connections are available, calls to getConnection() will block for up to connectionTimeout milliseconds before timing out.
Before throwing a PoolExhaustException, the connection pool will grow to the maximum size specified by the maxPoolOverflowSize property.

Default: 100

db.default.pool.maxLifetime

Controls the maximum lifetime of a connection in the pool. An in-use connection will never be retired, only when it is closed will it then be removed.
A value of 0 indicates no maximum lifetime (infinite lifetime), subject of course to the idleTimeout setting.

Default: 0 (unlimited)

db.default.pool.maxPoolOverflowSize

This is the maximum limit a target connection pool can stretch to.

Default: 120

db.default.pool.maxRetryBeforeOverflow

This is the maximum number of retries attempts before trying to strech the target connection pool.

Default: 10

db.default.pool.validationTimeout

Controls the maximum amount of time in milliseconds that a connection will be tested for aliveness. This value must be less or equal than the connectionTimeout .
Lowest acceptable validation timeout is 250 ms.

Default: 2000 (2 seconds)

db.default.pool.validationQuery

SQL query that can be used by the pool to validate connections before they are returned to the application.
If specified, this query MUST be an SQL SELECT statement that returns at least one row.

Default:
MSSQL: SELECT 1
ORACLE: SELECT 1 FROM DUAL

db.default.pool.leakDetectionThreshold

Controls the amount of time in milliseconds that a connection can be out of the pool before a message is logged indicating a possible connection leak.
A value of 0 means leak detection is disabled. Lowest acceptable value for enabling leak detection is 2000 (2 seconds).

Default: 600000 (10 minutes)

db.default.pool.leaseTimeTreshold

Specifies a time threshold in milliseconds for the connection lease. When the time limit is exceeded a log entry will be generated.

Default: 2000 (2 seconds)

db.default.pool.registerMbean

Controls whether or not JMX Management Beans ("MBeans") are registered or not.

Default: true

db.default.pool.registerMetrics

Controls whether or not Micrometer metrics are enabled or not.

Default: true

db.default.pool.reportMetricsInterval

Controls the amount of time in milliseconds after which metrics are being updated (only in case metrics are enabled).

Default: 5000 (5 seconds)

org.quartz.jobStore.driverDelegateClass

Driver delegates understand the particular ‘dialects’ of varies database systems.

Default:
MSSQL: org.quartz.impl.jdbcjobstore.MSSQLDelegate
ORACLE: org.quartz.impl.jdbcjobstore.oracle.OracleDelegate

org.quartz.jobStore.selectWithLockSQL

Must be a SQL string that selects a row in the “LOCKS” table and places a lock on the row.

Default:
MSSQL: SELECT LOCK_NAME FROM {0}LOCKS WITH (UPDLOCK,ROWLOCK) WHERE LOCK_NAME = ?
ORACLE: SELECT * FROM {0}LOCKS WHERE SCHED_NAME = {1} AND LOCK_NAME = ? FOR UPDATE

network

Root element of the network configuration, contains one or more nodes

identifier

Unique identifier of the node within the network. See -Dppm.nodeIdentifier command line argument below!

pim-server1

host

The host name / IP address this node runs on. Note: Do not use localhost or similar addresses. The host name or IP address in this attribute must be visible from all nodes in the cluster. In case the server has the CLIENTS_SERVER role, it also must be visible from the desktop clients.

default-role

Default role(s) each server node must have at start time. Available roles are CLIENTS_SERVER, JOB_SERVER, MQ_CONSUMER_SERVER, PRIORITY_JOB_SERVER. The server roles can not be modified during runtime of the server.

CLIENTS_SERVER. JOB_SERVER, MQ_CONSUMER_SERVER,PRIORITY_JOB_SERVER

useHttps

Enables/disables the SSL protocol. Default is false - in case you want to enable it, you need to provide a valid SSL certificate

maxIdleTime

Configures the maximum idle time of all Jetty server connectors.
Replaces the com.heiler.ppm.http.jetty.multicontext/maxIdleTime setting in plugin_customization.ini.
Since 8.0.03.01.

200000

port

HTTP port to be used for the web server

useNio

Use SelectChannelConnector based on non blocking input-output (default is true)

port

SSL port

keystore

Properties for the SSL certificate

password

keyPassword

needClientAuth

wantClientAuth

protocol

algorithm

keystoreType

name

Sets the name that will be assigned to any session tracking cookies created on behalf of the application represented by the ServletContext from which this SessionCookieConfig was acquired.

NOTE: Changing the name of session tracking cookies may break other tiers (for example, a load balancing frontend) that assume the cookie name to be equal to the default JSESSIONID, and therefore should only be done cautiously.

domain

Sets the domain name that will be assigned to any session tracking cookies created on behalf of the application represented by the ServletContext from which this SessionCookieConfig was acquired.

path

Sets the path that will be assigned to any session tracking cookies created on behalf of the application represented by the ServletContext from which this SessionCookieConfig was acquired.

comment

Sets the comment that will be assigned to any session tracking cookies created on behalf of the application represented by the ServletContext from which this SessionCookieConfig was acquired.

As a side effect of this call, the session tracking cookies will be marked with a Version attribute equal to 1.

httpOnly

Marks or unmarks the session tracking cookies created on behalf of the application represented by the ServletContext from which this SessionCookieConfig was acquired as HttpOnly.

A cookie is marked as HttpOnly by adding the HttpOnly attribute to it. HttpOnly cookies are not supposed to be exposed to client-side scripting code, and may therefore help mitigate certain kinds of cross-site scripting attacks.

secure

Marks or unmarks the session tracking cookies created on behalf of the application represented by the ServletContext from which this SessionCookieConfig was acquired as secure.

One use case for marking a session tracking cookie as secure, even though the request that initiated the session came over HTTP, is to support a topology where the web container is front-ended by an SSL offloading load balancer. In this case, the traffic between the client and the load balancer will be over HTTPS, whereas the traffic between the load balancer and the web container will be over HTTP.

maxAge

Sets the lifetime (in seconds) for the session tracking cookies created on behalf of the application represented by the ServletContext from which this SessionCookieConfig was acquired.

maxThreads

Maximum number of threads in pool that can be created (optional setting).
Replaces the http.maxThreads setting in server.properties.

512

maxIdleThreadTime

Maximum idle time in milliseconds for threads in pool (optional setting).
Replaces the http.maxIdleThreadTime in server.properties.

60000

bufferSize

Request buffer size in bytes (optional setting).
Replaces the com.heiler.ppm.http.jetty.multicontext/request.bufferSize setting in plugin_customization.ini.

16384

headerSize

Request header size in bytes (optional setting).
Replaces the com.heiler.ppm.http.jetty.multicontext/request.headerSize setting in plugin_customization.ini.

102400

bufferSize

Response buffer size in bytes (optional setting).
Replaces the com.heiler.ppm.http.jetty.multicontext/response.bufferSize setting in plugin_customization.ini.

32768

headerSize

Response header size in bytes (optional setting).
Replaces the com.heiler.ppm.http.jetty.multicontext/response.headerSize setting in plugin_customization.ini.

6144

port

Port to be used for the data grid connection.

defaultRequestTimeout

Timeout in milliseconds for requests in communication framework

300000 (5 min.)

port

Port for incoming / outgoing connections regarding internal communication

1712

useTLS

true in case the communication between desktop client and server and in between servers should be encrypted using a certificate. If set to true the keyStore element must also be defined (see below). False or omitted to not use TLS encryption.

false

connectTimeout

The timeout in milliseconds when connecting to the host. A value of 0 is interpreted as an infinite timeout. The connection will then block until established or an error occurs.

0

tcpNoDelay

Disables (= true!) resp enables (= false) the so-called Nagle's algorithm

true

keepAlive

Causes a packet (called a "keepalive probe") to be sent to the connected system if a long time (by default, more than 2 hours) passes with no other data being sent or received. This packet is designed to provoke an ACK response from the peer.

true

reuseAddress

Enables (=true) the reuseAddress option. Default is false.

When a TCP connection is closed the connection may remain in a timeout state for a period of time after the connection is closed (typically known as the TIME_WAIT state or 2MSL wait state). For applications using a well known socket address or port it may not be possible to bind a socket to the required SocketAddress if there is a connection in the timeout state involving the socket address or port.

It is not recommended to enable this option without prior consultation of the Informatica Support.

false

maxQueueSize

Maximum size of the request/event processing queue. New processing threads will be created only when the queue is full

100

maxCoreThreads

The maximum number of core threads that are processing request/events. Roughly speaking this is a hint for the thread scheduling strategy which denotes expected number of requests/events to be concurrently processed in a 'normal' operation mode. Scheduling strategy will tend to keep this number of threads in a ready-to-run state. Consider maxQueueSize together with this parameter. For more details concerning scheduling algorithm consult Java SDK ThreadPoolExecutor

100

maxThreads

The maximum number of threads that are processing request/events. This is a hard limit (in comparison with maxCoreThreads). If this value is reached, server will start rejecting requests

1000

keepAliveTime

Time in milliseconds that the thread scheduling strategy will wait, before reducing number of idle threads down to maxCoreThreads. This value protects from the situations when average number of required threads is higher than
maxCoreThreads and scheduling strategy is constantly recreating threads, because it tries to reduce number of threads down to maxCoreThreads

300000 (5 min.)

doPrestartAllCoreThreads

Flag value which instructs node to start all core threads on initialization. Usually this value should not be changed from its defaults (which is false). The reason to set this value to true could be the situation when all clients connect to the server together during a short period of time.

false

identifier

Short identifier of the service

PIM_8.0

name

Name of the service

Informatica PIM_8.0

port

Port for the JMX communication

55555

oid

Object id of the node in the cluster. Each node must have a unique oid.

1.1 (first node)
1.2 (second node)
and so on...

file

Path to the keystore file which contains the certificate for the SSL/TLS encrypted communication. The path might be relative to the configuration directory of the server.
For example: In case the server application is installed here: C:/Informatica/Product360/server the configuration folder would be C:/Informatica/Product360/server/configuration/HPM. In case you set the file element to certificates\keystore.jks it is expected to be at C:/Informatica/Product360/server/configuration/HPM/certificates/keystore.jks.
Alternatively you can define an absolute path.

password

The password for the keystore