database.type

Database type, see http://activiti.org/userguide/#supporteddatabases
Mainly used for Activiti and Database creation:

oracle

mssql

h2

Default: mssql

database.name

MSSQL: Name of the created database

e.g. database.name=hsx_1.4

Oracle: SID or ServiceName of the Oracle DB

e.g. database.name=XE

Default: database.name=hsx_1.4

database.server

Hostname of the database serverDefault: database.server=localhost

database.port

Port number of the database server

Default: MSSQL defaul is database.port=1433

database.username

User name for the database connection
CAUTION: Oracle needs the username in uppercase letters.

database.password

Password for the database connection

database.systemUser

Only for ORACLE Database Installation.

User which has the permission to create other users/tablespaces, is needed only to run the database
creation script, feel free to remove this property after successfull script execution.

e.g. database.systemUser=SYSTEM

database.systemUser

Only for ORACLE Database Installation.

password for the above specified database system user

database.data.dir

Specifies the operating-system path to the database data file.

database.data.size

Oracle:

Specify the size of the database data tablespace file in bytes. Use K, M, G, or T to specify the size in kilobytes,
megabytes, gigabytes, or terabytes. Specify a whole number; do not include a decimal.

MSSQL:

Is the initial size of the database data file. The kilobyte (KB), megabyte (MB), gigabyte (GB), or terabyte (TB) suffixes can be used.
The default is MB. Specify a whole number; do not include a decimal. The minimum value for size is 512 KB.

Default:

database.data.size=128MB 

database.data.size.growth

Oracle:

specify the size in bytes of the next increment of disk space to be allocated automatically
when more extents are required. Use K, M, G, or T to specify the size in kilobytes, megabytes,
gigabytes, or terabytes.Specify a whole number; do not include a decimal.

MSSQL:

Specifies the growth increment of the databases data file. It is the amount of space added to the database data
file each time new space is needed. Specify a whole number; do not include a decimal. A value of 0 indicates no growth.
The value can be specified in MB, KB, GB, TB, or percent (%). If a number is specified without an MB, KB, or % suffix,
the default is MB. When % is specified, the growth increment size is the specified percentage of the size of the database
data file at the time the increment occurs.

Default:

database.data.size.growth=64MB 

database.log.dir

Only for MSSQL Database Installation.

Specifies the operating-system path to the database log file.

database.log.size

Only for MSSQL Database Installation.

Is the initial size of the database log file. The kilobyte (KB), megabyte (MB), gigabyte (GB), or terabyte (TB)
suffixes can be used. The default is MB. Specify a whole number; do not include a decimal. The minimum value for size is 512 KB.

Default:

database.log.size=128MB 

database.log.size.growth

Only for MSSQL Database Installation.

Specifies the growth increment of the databases log file. It is the amount of space added to the database log file
each time new space is needed. Specify a whole number; do not include a decimal. A value of 0 indicates no growth.
The value can be specified in MB, KB, GB, TB, or percent (%). If a number is specified without an MB, KB, or % suffix,
the default is MB. When % is specified, the growth increment size is the specified percentage of the size of the
database log file at the time the increment occurs.

Default:

database.log.size.growth=64MB

database.temp.dir

Only for ORACLE Database Installation.

Specifies the operating-system path to the database temporary tablespace file.

database.temp.size

Only for ORACLE Database Installation.

Specify the size of the database temporary tablespace file in bytes. Use K, M, G, or T to specify the size in kilobytes,
megabytes, gigabytes, or terabytes. Specify a whole number; do not include a decimal.

Default:

database.temp.size=128MB

database.temp.size.growth

Only for ORACLE Database Installation.

specify the size in bytes of the next increment of disk space to be allocated automatically when more extents are required.
Use K, M, G, or T to specify the size in kilobytes, megabytes, gigabytes, or terabytes.Specify a whole number; do not include a decimal.

Default:

database.temp.size.growth=64MB

database.index.dir

Only for ORACLE Database Installation.

Specifies the operating-system path to the database index tablespace data file.

database.index.size

Only for ORACLE Database Installation.

Specify the size of the database index tablespace data file in bytes. Use K, M, G, or T to specify the size in kilobytes,
megabytes, gigabytes, or terabytes. Specify a whole number; do not include a decimal.

Default:

database.data.size=128MB 

database.index.size.growth

Only for ORACLE Database Installation.

specify the size in bytes of the next increment of disk space to be allocated automatically when more extents are required.
Use K, M, G, or T to specify the size in kilobytes, megabytes, gigabytes, or terabytes.Specify a whole number; do not include a decimal.

Default:

database.data.size.growth=64MB 

database.url

JDBC database URL connection string. Generally starts with "jdbc:". Examples:

jdbc:oracle:thin:@databaseServer:1521:sid

jdbc:jtds:sqlserver://databaseServer:1433;DatabaseName=HENRI

jdbc:h2:~/.hsp/database/dev;FILE_LOCK=NO´

Default:

automatically set though database.type declaration.

${database.url.${database.type}}

database.url.oracle

If you want to use Oracle's ServiceName please adjust this setting to

jdbc:oracle:thin:@${database.server}:${database.port}/${database.name}

Default:

jdbc:oracle:thin:@${database.server}:${database.port}:${database.name}

database.driverClassName

Java class name of the JDBC driver to use. See the JDBC driver manual for details. Supported values are:

oracle.jdbc.driver.OracleDriver

net.sourceforge.jtds.jdbc.Driver

org.h2.Driver

Default: automatically set though database.type declaration.

database.driverClassName=${database.driverClassName.${database.type}}

persistence.xmlLocation

Location pointing to the Hibernate XML configuration file.
This is a SPRING resource path, more information:
http://static.springsource.org/spring/docs/current/spring-framework-reference/html/resources.html

Example:

file:///C:/Informatica/SupplierPortal/configuration/persistence-mssql.xml

Default:

persistence.xmlLocation=file:///${hsx.configurationArea}/persistence-${database.type}.xml

where ${hsx.configurationArea} and ${database.type} are variables which get replaced on runtime.

persistence.unitName

Name of the Hibernate persistence unit. Same as defined in persistence.xml. Example

default

Default: default

Database connection pool settings
(since 8.0.6.02)

Settings for the database connection pool. Typically, Supplier Portal doesn't execute expensive and long lasting operations on database level (import jobs are handled in Product 360 server).
However, for high load scenarios with many concurrent users, the defaults should be updated.
Detailed explanation of the ObjectPool parameters: https://commons.apache.org/proper/commons-pool/api-1.6/org/apache/commons/pool/impl/GenericObjectPool.html

# Maximum number of active connections that can be allocated at the same time
database.pool.maxActive=8
# Maximum number of connections that can remain idle
database.pool.maxIdle=8
# Minimum number of idle connections in the pool
database.pool.minIdle=0
# Maximum amount of time (in milliseconds) the borrowObject method should block before throwing an exception when the pool is exhausted. Use -1 to make the pool wait indefinitely.
database.pool.maxWait=-1
# Whether or not the pool will validate objects before they are borrowed from the pool
database.pool.testOnBorrow=true
# Whether or not the pool will validate objects before they are returned to the pool
database.pool.testOnReturn=false

# The SQL query that will be used to validate connections from this pool before returning them to the caller.
# MSSQL Server
database.pool.validationQuery=select 1
# H2
#database.pool.validationQuery=select 1
# Oracle
#database.pool.validationQuery=select 1 from dual

import.autoImportDefault

Configures the default auto import policy.
New suppliers (invited or registered) get this value as default. It can be changed in the UI by the portal administrator.
Options are

• MANUAL_IMPORT

• AUTO_IMPORT_NO_ERRORS

• AUTO_IMPORT_NO_WARNINGS

Default:

MANUAL_IMPORT

import.automaticImportExecutionDelay

Can be configured at supplier level to trigger an import after a successful test run.
The execution is delayed by the given number of milliseconds.

restartUploadWizardWhenFinished

Configures what happens to suppliers once they finished uploading their data.
If set to false, user will be brought to the timeline after clicking through the upload wizard.
if set to true, the wizard will start from the beginning with the same catalog context.

hpm.restUri

REST base URL to Product 360 - Server. For host name and web server port see your Product 360 - Server configuration. Example:

http://hpmServer:1501/rest

hpm.systemUserName

Internal HPM user name that is used to trigger Product 360 - Server communication (e.g. start a test run) for supplier users.
For all communication triggered by portal admins the corresponding Product 360 - Server credentials are being used.

hpm.systemUserPassword

Internal Product 360 - Server user password

hpm.requestChunkSizeInBytes

Chunk size in bytes for HTTP file transfer to Product 360 - Server.

Example value: 1048576

Default:

1048576

hpm.webClientUri

Base URL of the Product 360 - Web. Only used if permission.itemeditor is true. Example:

http://hpmserver:1501/pim/webaccess

hpm.embedded.itemeditor

Global switch to enable/disable embedded item editor view.
Options are TRUE and FALSE:
- TRUE: item editor for supplier users appears embedded within Supplier Portal
- FALSE: items editor for supplier users appears in a separate browser tab

hmm.restUri

REST base URL to Product 360 - Media Manager.
For host name and web server port see your Product 360 - Media Manager configuration.
Example: http://hmmServer:8080/rest/rest

hmm.requestChunkSizeInBytes

Chunk size in bytes for HTTP file transfer to Product 360 - Media Manager.

Example value: 1048576

Default: 1048576

mail.enabled

Global switch to enable/disable mail functionality (boolean value).
If true, the following parameters need to be used for mail server configuration.
(It does not make much sense to use Product 360 - Supplier Portal without a mail server.)

Default: false

mail.protocol

Mail protocol as passed to javax.mail.

Example value: smtp

Default: smtp

mail.serverHost

Mail server host.

Example value:

smtp.company.com

mail.serverPort

Mail server port. Example:

25

Default: 25

mail.senderAddressDefault

The default sender address for mails. Will be used and displayed as mail sender. Has to follow a valid email pattern.
Example value:

admin@company.com

mail.username

User name if the mail server demands authentication. Can be empty otherwise.

mail.password

User password for mail server authentication.

mail.templateFolderPath

Directory which contains mail templates that overwrite the default templates provided within the war file.
You can also download the default templates using this link.

Default: file:///${hsx.configurationArea}/mailTemplates/

fileStorageService.rootDirectory

Folder pointing to the root directory for all binary files.
Make sure that the folder exists and that there is enough space available.
In production environments this directory should point to a fail-safe volume (e.g. RAID).

Default: C:/Informatica/PIM/SupplierPortal/filestorage

fileshare.adapter.home.dir

Path to the Digital Asset Management System (DAM) home folder where the media assets from Product 360 - Supplier Portal shall be sent to.
The user running the Tomcat server for Product 360 - Supplier Portal needs to have read/write access to that folder.
Existing files will be overwritten. Links are not supported as part of the directory.

Examples:

C:/Informatica/PIM/SupplierPortal/DAM
//ServerName/ShareFolder

Default: C:/Informatica/PIM/SupplierPortal/DAM

fileshare.adapter.supplier.subfolder

Create a supplier sub-folder. If true, a sub-folder for the specific supplier (if not already existing) will be created in the DAM home folder.
The name of the folder is the supplier identifier. If false, the DAM home folder root is used.

Default: true

fileshare.adapter.catalog.subfolder

Create a catalog sub-folder. If true, a sub-folder of the supplier folder (if not already existing) will be created.
The name of the folder is the catalog identifier.
If supplier sub-folder is false and catalog sub-folder is true, it will be implicitly assumed that supplier sub-folder is true.

Default: true

fileshare.adapter.unzip.images

If true, the media archive will be unzipped before it is uploaded to the specific folder.
Otherwise the zipped file is placed at the specific folder.

Default: false

fileshare.adapter.post.copy.step

If defined, a batch script is called after the previous upload steps are completed.
This property defines the batch script (including path) or is empty if no post copy step is needed. Examples:

C:/Informatica/PIM/SupplierPortal/bin/MyBatchScript.bat
//ServerName/ShareFolder/BIN/MyBatchScript.bat

mam.mapping.available

Allows to hide the special MAM mapping to upload images. If false, this mapping will not be shown,
e.g. Product 360 - Supplier Portal can be used without any MAM system as back-end.

Default: true

mam.mapping.name

The name of the MAM mapping. This is displayed to the supplier user in the first step of the upload process.
As mappings from Product 360 - Server cannot be shown in more than one language, the name of the MAM mapping is unique too.

Default: Media Assets

mam.mapping.text

A longer description text for the MAM mapping.

Default: Use this mapping to provide your media files.

mam.mapping.datasource.name

The name of the first and only mapping datasource.

Default: Zipped media files

mam.mapping.datasource.text

A longer description text for the mapping datasource.

Default: A zip archive containing all media assets.

i18n.defaultUiLocale

Default locale of the system in JAVA syntax. This value is used as default for new users.

Example value: en_US

Default: en_US

i18n.availableUiLocales

Property is not used in Product 360 7.0.04

List of all available locales in JAVA syntax, separated by comma.

Example value: de_DE,en_US

Default: de_DE,en_US

i18n.defaultDataLocale

The default language (locale) that is used for language specific data, f.e. catalog names.

The format is ISO 3166-1 alpha-2.

Default: en_US

i18n.availableDataLocales

The languages (locales) that are used for language specific data, f.e. all languages for which catalog names are maintained.

The format is ISO 3166-1 alpha-2.

Default: de_DE,en_US,fr_FR,ru_RU,nl_NL,sv_SE,fi_FI,es_ES,no_NO

synchronizePendingImportRunJob.trigger.cronExpression

Timer settings for the Product 360 - Server sync job following the cron expression pattern.
This job polls Product 360 - Server for updates of running test runs / import runs.
If such a run is finished, the Product 360 - Supplier Portal workflowmail continues.
Example value to run every 10 seconds:

0,10,20,30,40,50 * * * * ?

Default:

# Run every 10 seconds

0,10,20,30,40,50 * * * * ?

synchronizePendingImportRunJob.lockAtMost (since 8.1.1)

Defines how long (in ms) the job lock should be kept in case the machine which obtained the lock died before releasing it.
This is just a fallback, under normal circumstances the lock is released as soon the tasks finishes.
Negative value means default (1 hour)

Default: 9000 (ms) = 9s

removeOldImportFiles.trigger.cronExpression

Timer settings for the old import files cleanup job following the cron expression pattern.
This job removes product data and media data import files which overpass a specific amount of days.
Example value to run every 10 seconds:

0,10,20,30,40,50 * * * * ?

Default:

# run every night at 01:00 a.m.

0 0 1 * * ?

removeOldImportFiles.lockAtMost (since 8.1.1)

Defines how long (in ms) the job lock should be kept in case the machine which obtained the lock died before releasing it.
This is just a fallback, under normal circumstances the lock is released as soon the tasks finishes.
Negative value means default (1 hour)

Default: 3600000 (ms) = 1h

removeOldImportFiles.productFiles.olderThan

Configuration of the import files cleanup job
Remove all product data import files older than x days

Default: 365

removeOldImportFiles.mediaFiles.olderThan

Configuration of the import files cleanup job

Remove all media data import files older than x days

Default: 365

hostAdressWithAppRoot

An URL pointing to the root of the web app. This URL is used in mails that contain a link to the application.
Normally contains the absolute path including context path plus the suffix "/html/".

If you are using SAML authentication and the property: saml.supplierCreationStrategy is set to APPROVAL_WORKFLOW,
this url is also used in mails that contain a link to the application.

Example value:

http://hsxServer:9090/hsx/html/

Default: http://127.0.0.1:9090/hsx/html

resetPasswordRedirectTargetUrl

(since 8.1.0.01)

Defines a destination URL to which a user gets redirected after reseting a password. It's an optional setting and in default its left EMPTY so that users get logged-in with the new password and redirected onto the Supplier Portal dashboard.

In case of a customized "reset password" workflow this could be changed and the confirmation button after setting a new password redirects to a different URL. In this case the user is NOT logged in automatically and instead redirected to the configured URL.

Example value:

http://example:8080/landingPage.html

Default: <empty>

logoutUrl

(since 8.1.0.02)

Defines a destination URL to which a user gets redirected after logout and timeout. It's an optional setting and in default its left EMPTY. By default the user gets redirected to the Supplier Portal login page.

It is possible to enable the logout URL only for specific user roles. The logout redirect is only active if the current user matches at least one of the defined user roles of property logoutUrlActiveRoles.

Example value:

http://www.informatica.com

Default: <empty>

logoutUrlActiveRoles

(since 8.1.0.02)

Defines a list of user roles to enable the logout redirect defined in property logoutUrl.

Property is only relevant if logoutUrl is defined and Supplier Portal runs without SAML.

Example value:

ROLE_SUPPLIER_USER,ROLE_SUPPLIER_ADMIN,ROLE_BROKER_USER,ROLE_PORTAL_ADMIN

Default: ROLE_SUPPLIER_USER,ROLE_SUPPLIER_ADMIN,ROLE_BROKER_USER

content.filter.enabled

Global switch to enable/disable content filtering of all uploaded files.

If enabled, the parameter content.filter.accepted.mime.types provides a white list of all accepted file types.

Default: true

content.filter.accepted.mime.type

List of accepted mime types for content filtering of uploaded files.
All other files will be rejected during upload.
A list of valid mime types can be found here: http://www.iana.org/assignments/media-types/media-types.xhtml

Default:application/xml,
text/csv,
application/vnd.ms-excel,
application/vnd.openxmlformats-officedocument.spreadsheetml.sheet,
application/vnd.ms-excel.sheet.macroenabled.12,
image/png,
image/jpeg,
image/gif,
application/pdf,
application/gzip,
application/zip

image.resize

The width uploaded user avatar images will be resized to.

Default: 256

image.resize.height

The height uploaded user avatar images will be resized to.

Default: 256

Default values for mail notifications of new feed messages
(can be individually changed per user in personal settings)

Supplier:

feednotification.supplier.USER_REQUEST

Notify if new user message has been committed to the timeline that is visible for that supplier (boolean value).

feednotification.supplier.USER_REGISTRATION

Notify if a new user has registered for that supplier (boolean value).

feednotification.supplier.TEST_RUN_COMPLETE

Notify if a test run has been completed for that supplier (boolean value).

feednotification.supplier.IMPORT_RUN_COMPLETE

Notify if an import run has been completed for that supplier (boolean value).

Default values for mail notifications of new feed messages
(can be individually changed per user in personal settings)
Portal Administrator:

feednotification.portal.USER_REQUEST

Notify if a new user message has been committed to the timeline (boolean value).

feednotification.portal.USER_REGISTRATION

Notify if a new user has registered to the portal (boolean value).

feednotification.portal.TEST_RUN_COMPLETE

Notify if a test run has been completed (boolean value).

feednotification.portal.IMPORT_RUN_COMPLETE

Notify if an import run has been completed (boolean value).

feedfilter.type

Default filter settings for all users.
Use one or more of the FeedTypes comma separated (USER_REQUEST, USER_REGISTRATION, etc.)
or leave it empty for all.

remove.feeds.older.than

Configuration of the timeline cleanup job. Remove all feeds older than x days.

Example value for 1 year: 356

Default: 365

removeOlderFeedsJob.trigger.cronExpression

Cron trigger when this job should run following the cron expression pattern.

Example value for every night at 2 a.m.:

0 0 2 * * ?

Default:

# run every night at 02:00 a.m.

0 0 2 * * ?

removeOlderFeedsJob.lockAtMost (since 8.1.1)

Defines how long (in ms) the job lock should be kept in case the machine which obtained the lock died before releasing it.
This is just a fallback, under normal circumstances the lock is released as soon the tasks finishes.
Negative value means default (1 hour)

Default: 60000(ms) = 1min

workflowCleanupJob.maxAgeInWeeks

Configuration of the workflow cleanup job. This job removes old workflow instances that have not
been changed in the defined period of time. Remove workflows older than x weeks.

Example value for 2 weeks: 2

Default: 2

workflowCleanupJob.trigger.cronExpression

Cron trigger when this job should run following the cron expression pattern.

Example value to run every night at 3 a.m.:

0 0 3 * * ?

Default:

# run every night at 03:00 a.m.

0 0 2 * * ?

workflowCleanupJob.lockAtMost (since 8.1.1)

Defines how long (in ms) the job lock should be kept in case the machine which obtained the lock died before releasing it.
This is just a fallback, under normal circumstances the lock is released as soon the tasks finishes.
Negative value means default (1 hour)

Default: 60000(ms) = 1min

workflowCleanupJob.processDefinitionKeys

The workflow names that should be considered when searching for unfinished running workflow instances.
Normally the workflow name (sometimes called processDefinitionKey or processDefinitionId)
can be found in the following line of the workflow bpmn xml:

<process id="invitation" name="invitation">

If you add new workflows and want unfinished instances to be cleaned up, add the workflow name to this list.

Default: invitation,importIntoHpm

global.permission.itemeditor

Global switch to enable/disable item editor functionality. New suppliers (invited or registered) get this value as default. It can be changed in the UI for each supplier separately by the portal administrator.
Please check for communication settings Supplier Portal => Product 360 Server
Possible values:

• EDIT: items can be edited via item editor

• READ: items can be viewed read only via item editor

• RESTRICTED: items cannot be viewed and edited. Only portal admin can do any permission changes for a supplier.

• DISABLED: items cannot be seen. An item editor does not exist at all.

Default: RESTRICTED

global.permission.suppliertasks

Global switch to enable/disable the access to tasks assigned to Supplier Organization from Supplier Portal.
Possible values:

• ENABLED: access to supplier tasks is enabled for the whole Supplier portal.

• DISABLED: access to supplier tasks is disabled for the whole Supplier portal.

Default: DISABLED

permissions.portalAdmin

Defines a comma separated list of permissions which will be assigned to the portal admin role on startup. Possible values are:

• INVITE_SUPPLIER

• VIEW_IMPORT_MANAGER

• MANAGE_SUPPLIER_USER

• MANAGE_SUPPLIER

• START_DRY_RUN

• MANAGE_BROKER_USER
  
  

Default:

INVITE_SUPPLIER,VIEW_IMPORT_MANAGER,MANAGE_SUPPLIER_USER,MANAGE_SUPPLIER,START_DRY_RUN,MANAGE_BROKER_USER

To get more detailed information on how to handle role permissions see the Customize User Interface.

permissions.supplierAdmin

Defines a comma seperated list of permissions which will be assigned to the portal admin role on startup. Possible values are:

• START_DRY_RUN

• MANAGE_SUPPLIER_USER

Default:

START_DRY_RUN,MANAGE_SUPPLIER_USER

To get more detailed information on how to handle role permissions see the Customize User Interface.

permissions.broker

Defines a list of permissions which will be assigned to the broker role on startup. Possible values are:

• START_DRY_RUN

Default:

START_DRY_RUN

invitation.link.hash.validity.duration.hour

Defines expiration time of (re)set password link in hours. Default is two hours.

urlToken.maxAge

For url token authentication. Defines the time slot after that an issued token expires.
Expired tokens cannot be used for authentication anymore. Value is in seconds.

Default: 60

license.maximumActiveUsers

The number of total active supplier users allowed. If more users are created (e.g. during invitation or registration),
a warning will be displayed in the UI and written in the log file.

Default: 50

uiCustomizaton.file

Defines the location ui customization file that allows to contribute new ui elements.
An example and further details can be found in the Accelerators package under "Customize_User_Interface.html".

Default: file:///${hsx.configurationArea}/uiCustomization.json

dataModelCustomization.file

Defines the location of the custom fields file that allows to contribute additional data model fields.
An example and further details can be found in the Accelerators package under "Customized_Data_Model_for_Supplier_Data.html".

Default: file:///${hsx.configurationArea}/dataModelCustomization.json

registrationCustomization.defaultCatalogName

Defines the name of the default catalog which is created while activating a supplier over Supplier Hub.
The pattern {SupplierName} is going to be replaced by the supplier's name on runtime.

Default: {SupplierName} - default Catalog

workflows.customizationFolderPath

Location of the folder containing customized workflows.

Default: file:///${hsx.configurationArea}/workflows/

keystore.location

Defines the file location of the keystore to use

keystore.password

Defines the password of the keystore defined via ${keystore.location} property

wrongLogin.maxAttempts

(since 8.2)

Maximum number of wrong logins are that allowed per Supplier Portal server.If the number is reached the user gets locked for the duration specified by the property wrongLogin.lockDuration. This affects all types of users. After restarting the server the user is unlocked again.Please note that the login attempts are not synced between multiple Supplier Portal servers. If the login requests are distributed to different Supplier Portal servers it is possible that a the user gets locked after (wrongLogin.maxAttempts * number of servers) attempts.
Default value: 10

wrongLogin.lockDuration

(since 8.2)

Defines the duration in minutes how long the user gets locked after user reaches the defined maximum number of wrong logins (wrongLogin.maxAttempts).
After restarting the server the user is unlocked again.
Default value: 30

loadbalancer.schema

Defines the file http transport protocol schema, either http or https

loadbalancer.contextPath

The supplier portal context path must be set and start with a forward slash

Default: /hsx

loadbalancer.serverName

The load balancer server name

loadbalancer.port

The load balancer server port

saml.supplierCreationStrategy

Define the strategy how to create suppliers, if SAML authentication is used.

Possible values are:

• AUTOMATIC: Supplier and supplier users will be created automatically.

• APPROVAL_WORKFLOW: Supplier and supplier users will be created with the registration workflow.

Default value is AUTOMATIC

global.permission.ECCnetAccess

(since 8.0.6.01)

Global switch to enable/disable the ECCnet access from Supplier Portal.
Possible values:

• ENABLED: ECCnet access is enabled. Means that by default ECCnet access is enabled for newly created suppliers. However, the portal administrator can revoke ECCnet access from the supplier.

• RESTRICTED: ECCnet access is available, but by default ECCnet access is disabled for newly created suppliers. However, the portal administrator can give ECCnet access to the supplier.

• DISABLED: ECCnet access is disabled for the whole Supplier portal.

Default: DISABLED

atmosphere.enabled

Can be used to turn push notifications off. Turn it off in case of issues in the network infrastructure, like proxies which are not deal with long running requests correctly.
If set to false, users will not get notifications about new timeline messages unless refreshing the page explicitly or during navigation.
Default value: true

atmosphere.defaultTransport

Default transport mode for server-side push notifications. Only applies, if atmosphere.enabled is true.
Details: https://github.com/Atmosphere/atmosphere/wiki/atmosphere.js-API
Possible values: long-polling, streaming, jsonp, sse, websocket
Default value: streaming

atmosphere.fallbackTransport

Fallback transport mode for server-side push notifications. Only applies, if atmosphere.enabled is true.
Fallback is used where there's an issue when estabilishing a connection to the server using the default mode.
Details: https://github.com/Atmosphere/atmosphere/wiki/atmosphere.js-API
Possible values: long-polling, streaming, jsonp, sse, websocket
Default value: long-polling

job.threadPoolSize

Set the Job Frameworks thread pool size.

Default: 10

job.threadNamePrefix

Set the job frameworks thread name prefix.

Default: JobThread

job.defaultLockAtMostFor

Scheduled (like import job synchronization,etc) jobs get locked to be sure to execute them only once at the same time.
By setting defaultLockAtMostFor you make sure that the lock is released even if the node dies and make sure it's not executed more than once in the configured time duration (in minutes).
Please note that if the job takes longer than the configured time duration, it will be executed again.

Default: 15