Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Property NameDescriptionDefault ValuePossible Values
abpm.pagination.taskmanager.page.sizeMaximum number of records that will be displayed on a page.20Any positive integer
abpm.pagination.managepage.page.sizeMaximum number of records that will be displayed on a manage screen.20Any positive integer
abpm.pagination.page.sizeMaximum number of records that will be displayed on one page10Any positive integer

 

 

Anchor
Environment_Name
Environment_Name
PERSONALIZATION

...

Property NameDescriptionDefault ValuePoosible Value
abpm.versionControl.enableEnables versioning in Adeptia Suite.falsetrue or false
abpm.versionControl.repository.access.protocolProtocol to access the SVN server.SVNSVN/HTTP/HTTPS
abpm.versionControl.repository.url

IP address/Name of the host machine where SVN is installed .Define the hostname or IP address of SVN host according to 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 the 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 according to syntax given belowin the following syntax:

 svn://<hostname >:<SVN port><Absolute Path of the Repository including the Repository Name>
Provide the path to the Repository that you created when installing SVN.
For example if the SVN Server is installed on a host with IP address 192.168.1.1 using port 3690, and the path of the SVN Repository is /Adeptia/Version_Control_Repository, then you need to define the URL as follows:
 
svn://192.168.1.1:3690/Adeptia/Version-Control_Repository

 

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

abpm.versionControl.username

 

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

abpm.versionControl.usernameUser Name of the Version Control RepositoryThe username, which is used to access SVN repository. As per configuration of SVN Server
abpm.versionControl.passwordPassword of the user specified in the abpm.versionControl.username.  
abpm.versionControl.projectPath

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

the

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

the

Adeptia Suite is installed

of

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

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

c

C:

\

/Adeptia

\

/AdeptiaVersionControl folder.
 
You can also define the relative path

like

as .

\

/AdeptiaVersionControl. In this case

the

, 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

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

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


Client Authentication

Property NameDescriptionDefault ValuePossible Values
abpm.versionControl.keystore.path

Description

Path of your keystore to use for client authentication

Default Value

NA

Possible Values

Any accessible location on local system

Selection Criteria

. Applicable only when you use a an HTTPS protocol on an SVN server which is client authenticated

Comments

Version Control Client Keystore Path

 

...

. Any accessible location on a local system.
abpm.versionControl.keystore.password

Description

Set a password for your keystore

Default Value

Blank

Possible Values

NA

Selection Criteria

. Applicable only when you use a an HTTPS protocol on an SVN server which is client authenticated

Comments

Version Control Client Keystore Password

 

...

.  


Anchor
_

...

Permission
_

...

Description

...

Permission
Permission

Property NameDescriptionDefault Value

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)

Selection Criteriaabpm.activity.defaultPermission

Default permission mask while creating a new activity.

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

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


There are 3 level three levels of permission 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

...

750Combination 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)