Default Value

ISO-8859-1

Possible Values

Any possible character set encoding such as UTF-8 etc.

Selection Criteria

Specifies the default character set encoding to be used by all activities while parsing the data. However, you can also define the character set encoding at each activity level. Character set encoding defined at the activity level always takes precedence. To know more about character set encoding, refer to the Configuring Character Set Encoding section of Adeptia Suite Developer Guide.

Default Value

INFO,console,jdbc

Possible Values

A combination of valid log level along with the appenders.

Selection Criteria

This property specifies the default logging level of System and Process flow log.
For example INFO,console, jdbc: INFO indicates the logging level and console and jdbc indicates appender. The data can go to console, jdbc, or file.
You can also define the logging level at each Process flow level. Logging level, defined at process flow level always takes precedence.

Default Value

INFO

Possible Values

ERROR/INFO/DEBUG

Selection Criteria

This property specifies the default logging level of Event log.

Default Value

com.mchange.v2.log.FallbackMLog

Default Value

WARNING

Default Value

ERROR

Default Value

false

Possible Values

true/false

Selection Criteria

By default both system and application logs are written together in one file. All Kernel logs are written into Kernelapplication.log and all Webrunner logs are written into WebRunnerapplication.log file.
If this property is set to true, only application logs (run time logs) are written in to these files. All System logs are written into Kernelsystem.log and Webrunnersystem.log files. When this property is enabled, the File Logging properties also come into effect.

Default Value

org.apache.log4j.consoleAppender

Possible Values

Any implementation of console Appender

Selection Criteria

ConsoleAppender appends log events to System.out or System.err using a layout specified by the user. The default target is System.out.

Default Value

comorg.apache.log4j.jdbcplus.jdbcAppender.adeptia.indigo.logging.CustomJDBCAppender

Possible Values

Any implementation of JDBC Appender

Selection Criteria

The JDBC Appender writes messages into a database via JDBC. Multiple configuration options and parameters are supported.

Default Value

jdbc:hsqldb:hsql://127.0.0.1:2477As specified during installation

Possible Values

Any valid JDBC URL

Selection Criteria

Specifies the JDBC URL to connect to log database. This property is automatically populated as per the value given in the Log Database Configuration step during installation.

Default Value

org.hsqldb.jdbcDriverAs per the log database selected during installation.

Possible Values

JDBC Driver of the log database, which is used to store the logs.

Selection Criteria

This value is provided by the JDBC driver used to connect to the log database. This property is automatically populated as per the log database server type selected at the time of installation.

Default Value

saAs specified during installation

Possible Values

Any user name, which has permission to create tables, and insert records in the log database.

Comments

This property is automatically populated as per the user name specified in the Log Database Configuration step at the time of installation.

Default Value

As specified during installation?

Possible Values

NA

Selection Criteria

This property is automatically populated using the password specified in the Log Database Configuration step at the time of installation.

Default Value

HSQLAs specified during installation

Possible Values

NA

Selection Criteria

This property is automatically populated as per the password specified in the Log Database Configuration step at the time of installation.

Default Value

com.adeptia.indigo.logging.DbcpPoolConnectionHandler

Possible Values

NA

Selection Criteria

Connector used to establish connection with log4j JDBC Appender

Default Value

org.apache.log4j.RollingFileAppender

Possible Values

Any implementation of FileAppender

Selection Criteria

RollingFileAppender is used to backup the log files when they reach a certain size

Default Value

WebrunnerSystem.log

Possible Values

Any valid file name with .log extension.

Selection Criteria

Name of the file, in which webrunner logs are written.

Default Value

KernelSystem.Log

Possible Values

Any valid file name with .log extension.

Selection Criteria

Name of the file, in which Kernel logs are written.

Default Value

10

Possible Values

Any positive integer and depends on the number of old logs to keep

Selection Criteria

When the log file reaches up to a specified size, it is renamed for backup purpose and a new file is created to store the new logs. The property specifies how many backup files to keep, before they are deleted.

Default Value

10 MB1 MB

Possible Values

Maximum size of the Kernel and WebRunner log files individually.

Selection Criteria

When the log file reaches this size, it is archived and a new file is created to store the logs.

Default Value

As specified during installationjdbc:hsqldb:hsql://127.0.0.1:2477?

Possible Values

Any valid JDBC URL

Selection Criteria

Specifies the JDBC URL to connect to the archival log database. This property is automatically populated as per the value given in the Log Database Configuration step during installation.

Default Value

As per the log database selected during installationorg.hsqldb.jdbcDriver.

Possible Values

JDBC Driver of the log database, where the logs are archived.

Selection Criteria

Determines the JDBC driver used to connect to the log database. This property is automatically populated as per the log database server type selected at the time of installation.

Default Value

As specified during installationsa

Possible Values

Any user name, which has permission to create tables and insert records in the log database.

Comments

This property is automatically populated from the user name specified in the Log Database Configuration step at the time of installation.

Default Value

As specified during installation

Possible Values

NA

Selection Criteria

This property is automatically populated using the password specified in the Log Database Configuration step at the time of installation.

Default Value

As specified during installationHSQL

Possible Values

NA?

Selection Criteria

This property is automatically populated as per the password specified in the Log Database Configuration step at the time of installation.

Default Value

SecretKeys.Keystore

Possible Values

Any valid JCEKS Keystore

Selection Criteria

SecretKeys.Keystore is a protected database that holds keys that are generated when user creates the Secret Key entity. These keys are used for Encryption, Decryption and Schema services.
Access to a keystore is guarded by a password defined in the abpm.security.secretkeypassword.encrypt property. You cannot change this password. In addition, each private key in a keystore can be guarded by its own password.

Default Value

etc/security

Possible Values

Any absolute or relative path from ServerKernel folder.

Selection Criteria

Represents the folder path where security related folders are stored viz. Keystore, secret keys etc.

Default Value

0

Possible Values

Any positive integer.

Selection Criteria

Represents the number of days after which the password expires. A value of 0 ensures that the password does not expire.

Default Value

5

Possible Values

Any positive integer.

Selection Criteria

Represents the number of days before the Adeptia User password expiry, the expiry warning is to be displayed. This warning is displayed at login.

Default Value

no

Possible Values

yes/no

Selection Criteria

Indicates the comment that is added after an activity, is saved or edited. You can enter the reason for the add action or edit action.

Image Removed

If you enable/disable comments when you are already working in Process Designer or Data Mapper applet, you need to restart the respective applet.

Default Value

etc/jaas.config

Possible Values

Any file containing the login module configurations

Selection Criteria

Valid login modules

Comments

Specifies which Login Modules should be used for the Adeptia Suite application, and in what order the Login Modules should be invoked

Default Value

smtp

Possible Values

smtp/mapi

Selection Criteria

Select smtp if the outgoing mail server is using the SMTP protocol.
Select mapi if outgoing mail is using MAPI protocol. For example, Exchange Server

Default Value

Depends on the value given in the Mail Server Configuration steps during installation

Possible Values

IP address or hostname of the SMTP Server

Selection Criteria

Applicable only when smtp is defined as mail protocol. This property is automatically populated using the value given in the Mail Server Configuration step during installation. However, you can also manually define it, if needed.

Default Value

Adeptia

Possible Values

Domain Name, in which exchange server is configured.

Selection Criteria

Applicable only when MAPI is defined as the mail protocol. This property is automatically populated from the value given in the Mail Server Configuration step during installation. However, you can also manually define it, as needed.

Default Value

CDOHOSTMachine

Possible Values

IP Address or Host name of the machine, which is configured as CDOHOST to allow communication between Adeptia Suite and Exchange Server.

Selection Criteria

Applicable only when MAPI is defined as mail protocol. CDOHOST allows Adeptia Suite to communicate with Exchange server.

Default Value

Depends on the value given in the Mail Server Configuration steps during installation.

Possible Values

Any email address, which can be used to send the mail notifications.

Selection Criteria

This property is automatically populated from the value given in the Mail Server Configuration step during installation. However, you can also define it, as needed.

Default Value

Depends on the value given in the Mail Server Configuration steps during installation.

Possible Values

User ID of the mail account, which is mentioned in systemAdminEmailID property.

Selection Criteria

This property is automatically populated using the value given in the Mail Server Configuration step during installation. However, you can also manually define it.

Default Value

Depends on the value given in the Mail Server Configuration steps during installation.

Possible Values

Password of the mail account, which is mentioned in systemAdminEmailID property.

Selection Criteria

This property is automatically populated as per the value given in the Mail Server Configuration step during installation. However, you can also manually define it, as needed.

Default Value

Password

Possible Values

Subject string with which mail notification will be sent

Selection Criteria

This value is used as the subject for mail notifications, which are sent by Adeptia Suite each time you change your mail password.

Default Value

Depends on the value given in the Mail Server Configuration steps during installation.

Possible Values

yes/no

Selection Criteria

Select yes if the specified mail server requires a secure connection. Select no if the specified mail server does not require a secure connection.

Default Value

Depends on the value given in the Mail Server Configuration steps during installation.

Possible Values

SMTP port used by Mail Server

Selection Criteria

This property is automatically populated as per the value given in the Mail Server Configuration step during installation. However, you can also manually define it, as needed.

Default Value?

Possible Values?

Selection Criteria?

Default Value

Blank

Possible Values

Any string as per the naming convention policy of your organization.

Selection Criteria

Prefix appended to an activity name

Default Value

no

Possible Values?

Selection Criteria?

Default Value

ldap://ldapServerName:portNumber

Possible Values?

Selection Criteria?

Default Value

NA

Possible Values?

Selection? Criteria

Default Value

Subtree

Possible Values

Selection Criteria

Default Value

NA

Possible Values?

Selection Criteria?

Default Value

NA?

Possible Values

Selection Criteria

Default Value

NA

Possible? Values

Selection Criteria?

Default Value

NA

Possible Values?

Selection Criteria?

Default Value

NA

Possible Values?

Selection Criteria?

Default Value

NA

Possible? Values

Selection Criteria?

Default Value

NA

Possible Values?

Selection Criteria?

Default Value

no

Possible Values

yes/no

Selection Criteria?

Default Value

NA

Possible Values?

Selection Criteria?

Default Value

yes

Possible Values?

Selection Criteria?

Default Value

NA

Possible Values?

Selection Criteria?

Default Value

NA

Possible Values?

Selection? Criteria

Default Value

NA

Possible Values?

Selection? Criteria

Default Value

NA

Possible Value?s

Selection Criteria?

Default Value

NA

Possible Values?

Selection? Criteria

Default Value

NA

Possible? Values

Selection? Criteria

Default Value

NA

Possible Values?

Selection Criteria?

Default Value

NA

Possible? Values

Selection Criteria?

Default Value

NA

Possible Values?

Selection Criteria?

Default Value

no

Possible Values

yes/no

Selection Criteria?

Default Value

yes

Possible Values

yes/no

Selection Criteria?

Default Value

yes

Possible Values

yes/no

Selection Criteria?

Default Value

no

Possible Values

yes/no

Selection Criteria

This option is used to enable or disable a multitenant environment.

Default Value

yes

Possible Values

yes/no

Selection Criteria

NA

Comments

Enable or disable pagination feature
Limitation: This feature does not work for SQL 2000 Server

Default Value

20

Possible Values?

Selection? Criteria

Default Value

20

Possible Values?

Selection Criteria?

Default Value

10

Possible Values

Positive Integer

Selection Criteria

NA

Comments

This option is used to set the number of records to be displayed in one page

Default Value

Development

Possible Values

Any string to identify the Adeptia Suite. For Example : Development, Production etc.

Selection Criteria

Used to identify the Adeptia Suite environment, when more than on Adeptia Suite environment is running in your organization. The value given here is displayed, when you click the About link.

Default Value

false

Possible Values

true/false

Selection Criteria

In case you want to version control your Adeptia Suite objects, then set this property as true.

Comments

Sets Version Control Option as enabled or disabled

Default Value

SVN

Possible Values

SVN/HTTP/HTTPS

Selection Criteria

The protocol that you want to use to access the SVN server

Comments

Version Control repository access protocol. Possible values are SVN, HTTP and HTTPS

Default character set encoding to be used by all activities while parsing the data. However, you can also define the character set encoding at each activity level. Character set encoding defined at the activity level always takes precedence.

Specifies the default logging level of System and Process flow log. For example, INFO, console, jdbc.

INFO indicates the logging level and console and jdbc indicates appender. The data can go to console, jdbc, or file.
You can also define the logging level at each process flow level. Logging level, defined at process flow level always takes precedence.

Enables or disables separate log files for System and Application level. By default, both system and application logs are written together in one file. All Kernel logs are written into Kernelapplication.log and Webrunner logs are written into WebRunnerapplication.log file.

 If the value of this property is set to true, only application logs (runtime logs) are written into these files. All System logs are written into Kernelsystem.log and Webrunnersystem.log files.

Specifies the path where system logs files are stored. You can define an absolute path or any relative path where you want to store the file, for example, C:\Adeptia_systemLogFiles.
 

The relative path shall be relative to ServerKernel/web folder.

 For example, to store the recovery files within /ServerKernel/web/logs/Adeptia_systemLogFiles, you can define the path as:
./logs/ Adeptia_systemLogFiles.

logs/systemlogs

The value of this property is populated automatically as per the username specified in the Log Database Configuration step at the time of installation.

 As specified during installation

 As specified during installation.

Adeptia Suite Secret keystore name.

SecretKeys.Keystore is a protected database that holds keys that are generated when a user creates the Secret Key entity. These keys are used for Encryption, Decryption, and Schema services.

 Access to a keystore is guarded by a password defined in the abpm.security.secretkeypassword.encrypt property. You cannot change this password. In addition, each private key in a keystore can be guarded by its own password.

Specifies the protocol used by an outgoing mail server.

Specifies whether you want to receive notification whenever a users password is changed.

abpm.ldap.enableLdap

Enable or disable LDAP authentication.

abpm.ldap.provider.url

Provider URL to connect to LDAP Server.

abpm.ldap.enableLdapOverSSL

Enable or disable LDAP connection over SSL.

abpm.ldap.searchScopeLevel

Search scope level - One, Object, and Subtree.

abpm.ldap.bindDN

The DN used to bind against the LDAP server for the user and roles queries. This is DN with read/search permissions on the baseContextDN and rolesContextDN values. It specifies DN of the admin user in LDAP server.

abpm.ldap.bindCredential

Password for the bindDN.

abpm.ldap.baseContextDN

Fixed DN of the context to start the user search from.

abpm.ldap.baseFilter

Search filter to locate the context of the user to authenticate. The input username as obtained from the login module callback will be substituted into the filter where a "{0}" expression is seen.

abpm.ldap.rolesContextDN

Fixed DN of the context to search for user roles. For Active Directory, this is the DN where the user account is.

abpm.ldap.roleFilter

Search filter to locate the roles associated with an authenticated user. The login module callback will be substituted into the filter anywhere a "{0}"expression is seen. The authenticated userDN will be substitute into the filter where a "{1}" expression is seen.

abpm.ldap.roleAttributeID

Name of the role attribute of the context that corresponds to the name of the role.

If the value of the roleAttributeIsDN property is set to true, this property is the DN of the context to query for the roleNameAttributeID attribute.

If the roleAttributeIsDN property is set to false, this property is the attribute name of the role name.

abpm.ldap.roleAttributeIsDN

Flag indicating whether the user's role attribute contains the fully distinguished name of a role object, or the user's role attribute contains the role name.

If the value of this property is false, the role name is taken from the value of the user's role attribute.

If the value of this property is true, the role attribute represents the distinguished name of a role object.

The role name is taken from the value of the roleNameAttributeId attribute of the corresponding object. The default value of this property is false.

abpm.ldap.roleNameAttributeID

Name of the role attribute of the context that corresponds to the name of the role.

If the value of the roleAttributeIsDN property is set to true, this property is used to find the role object's name attribute.

If the value of the roleAttributeIsDN property is set to false, this property is ignored.

abpm.ldap.roleDN.searchRoleNameAttributeID

Enable or disable searching role name attribute in user's distinguished name.

abpm.ldap.administratorUsers

Name(s) of LDAP user(s) (separated by comma) that will be treated as System Admin users in Adeptia Suite and Adeptia Connect.

abpm.ldap.administratorGroups

Name(s) of LDAP group(s) (separated by comma) that will be treated as System Admin users in Adeptia Suite and Adeptia Connect.

abpm.ldap.groupAdminUsers

Name(s) of LDAP user(s) (separated by comma) that will be treated as Group Admin users in Adeptia Suite and IT Users in Adeptia Connect.

abpm.ldap.groupAdminGroups

Name(s) of LDAP group(s) (separated by comma) that will be treated as Group Admin users in Adeptia Suite and IT Users in Adeptia Connect.

abpm.ldap.developerUsers

Name(s) of LDAP user(s) (separated by comma) that will be treated as Developer Users in Adeptia Suite and Business Users in Adeptia Connect.

abpm.ldap.developerGroups

Name(s) of LDAP group(s) (separated by comma) that will be treated as Developer Users in Adeptia Suite and business Users in Adeptia Connect.

abpm.ldap.businessUsers

Name(s) of LDAP users (separated by comma) that will be treated as Business Users in Adeptia Suite.

abpm.ldap.businessGroup

Name(s) of LDAP groups (in comma separated format) that will be treated as Business Users in Adeptia Suite.

abpm.ldap.group.itUsers

Name of the LDAP group that shall be treated as IT users in Adeptia Connect.

abpm.ldap.alwaysDefaultGroupLogin

Enable or disable login only with default LDAP group in Adeptia.

abpm.ldap.defaultLdapGroup

Entity id of the group (created in Adeptia) that shall be treated as default LDAP group.

abpm.ldap.enableDefaultGroupLogin

Enable or disable login with default LDAP group in Adeptia.

abpm.ldap.enableSSO

Enable or disable Single Sign-On in Adeptia Suite.

abpm.ldap.sso.filterClass

Class name that needs to be initiated for SSO authentication process.

abpm.ldap.enable.anonymous.login

Enable or disable anonymous login through blank password in LDAP.

abpm.ldap.referrals

Set the environment property referrals in LDAP. Possible values are ignore and follow.

IP address/Name of the host machine where SVN is installed in the following syntax:

svn://<hostname >:<SVN port>

 where,

 <hostname> is hostname or IP address of the host, where SVN is installed.
<port> is the port at which SVN is running. By default, SVN uses 3690.
 
For example, if SVN Server is installed on a host with IP address 192.168.1.1 and using port 3690 , and the path of the SVN Repository is /Adeptia/Version_Control_Repository, then you need to define the URL as followswill be:
svn://192.168.1.1:3690/Adeptia/Version-Control_Repository

Default Value

blank

Possible Values

As per configuration of SVN Server

Selection Criteria

The username, which is used to access SVN repository

Comments

Version Control Repository User Name

Default Value

blank

Possible Values
 
In case SVN is installed on Linux OS, you need to provide the absolute path of the Version Control Repository in the following syntax:

 svn://<hostname >:<SVN port><Absolute Path of the Repository including the Repository Name>

svn://<hostname >:<SVN port>
or
svn://<hostname >:<SVN port><Absolute Path of the Repository including the Repository Name>

This is the

Default Value

blank

Possible Values

Any absolute path or relative path with respect to ServerKernel folder.

Selection Criteria

path of a local working copy of version control project. When you Check-In the activity of Adeptia Suite for the first time,

a local copy of SVN project is created in the path

specified in the property abpm.versionControl.projectPath.  

At the same time, a project with the name specified in the above property

is also created in the SVN.  

If

Adeptia Suite is installed

on Windows OS

then you can define either the absolute path or relative path with respect to ServerKernel folder. For example, you can define the absolute path as

C:/Adpetia/AdeptiaVersionControl. It means that the local SVN project is created within

C:

/Adeptia

/AdeptiaVersionControl folder.
 
You can also define the relative path

as .

/AdeptiaVersionControl. In this case

, a local SVN project is created within ServerKernel > AdeptiaVersionControl folder.

The default value of the property abpm.versionControl.projectPath is .

/AdeptiaVersionControl.

You can provide the path other than the default path in the abpm.versionControl.projectPath property as per your requirement.

If Adeptia Suite is installed on Linux OS then you must specify the absolute path for the Local Version Control Project

, for example, /root/home/ADEPTIA/AdeptiaVersionControl/.

Default Value

NA

Possible Values

Any accessible location on local system

Selection Criteria

Comments

Version Control Client Keystore Path

Default Value

Blank

Possible Values

NA

Selection Criteria

Comments

Version Control Client Keystore Password

750

Possible Values

Combination of read, write, and execute permission that you want to give to each type of user (Owner, Other groups to which the owner belongs, and Users outside the owner's group)

Default permission mask while creating a new activity.

The permission property contains a 3three-digit number, where:

• 1^st digit represents the level of permission for Owner.
• 2^nd digit represents the level of permission for other groups to which the owner belongs. 
• 3^rd digit represents the level of permission for users outside the owner's group.

There are

three levels of

permissions for every level of user:

• Read
• Write Write 
• Execute

Each level has a specific number assigned to it.

• Read - 4
• Write - 2 2 
• Execute - 1

So based on these numbers, you can assign each type of user

in any of the following digits:

7 = 4+2+1 (Read + Write + Execute)

• 6 = 4+2 (Read + Write)
• 5 = 4+1 (Read + Execute)
• 4 = 4 (Read)
• 3 = 2+1 (Write + Execute)
• 2 = 2 (Write) 
• 1 = 1 (Execute)

For Example - 750 (default value) means each user has the default permissions:
Administrator - 7 - Read + Write + Execute
Group - 5 - Read + Execute
Other - 0 - None