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 Connect 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.

Select smtp if the mail server is using SMTP protocol.
Select mapi if outgoing mail is using MAPI protocol, for example, Exchange 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 Connect.

abpm.ldap.businessGroup

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

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 Connect.

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 then the URL will be: svn://192.168.1.1:3690/
 
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 path of a local working copy of version control project. When you Check-In the activity of Adeptia Connect 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 Connect 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 Connect 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 permission mask while creating a new activity.

The permission property contains a three-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 
• Execute

Each level has a specific number assigned to it.

• Read - 4
• Write - 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