Deployment settings that can be edited

The top two fields contain general deployment values that can be edited:

• Deployment Name – The name of the deployment that you are creating

• Deployment Type Name – This is descriptive of the deployment and is for information purposes only.

Each deployment contains one VPE schema, and one or more component schemas.

• The VPE schema specifies the database schema from which VPE data will be available to a user.

• The component schemas specify what database schemas the user will be able to read component data from. Users are granted access to an entire deployment, so they therefore may be granted access to a number of component schemas.

Each schema contains the following settings:

• Schema name – This is the name of the schema and is used for display purposes when managing what deployments users can access.

• Inherits from master – If this option is set for a schema, then the database connection data is copied from the local file hibernate.properties and cannot be edited further. This is set on a schema-by-schema basis.

• If the option Inherits from master is not set, then the following settings can be edited for a schema. These are the same settings that are used to specify the database when installing aPriori, and they specify the database schema that will be used.

• Database type – MySQL or Oracle (If the database is Oracle, then there will also be an option to select whether the connection is specified by SID or Service Name.)

• Host name

• Port number

• Database identifier

• Username

• Password

If the Inherits from Master option is not checked, then a Test Connection button becomes enabled. This allows you to test if the connection details that have been entered result in a successful connection.

To add or remove component schemas

1 To add a new Component Schema, click the green “+” symbol at the bottom left of the screen.

2 To remove a Component Schema from the deployment, click the red “X” symbol at the right of the Component Schema name. (This button is only enabled if multiple Component Schemas exist in the deployment.