The BIS-GridEngine is configurable with the help of the Java Properties concept. A .properties file and the corresponding Properties object implementation that reads the file is used. A BISGridProperties object, which is created when the services start, retrieves the configuration information. This object is responsible for the configuration of all BIS-Grid services. The properties are loaded in two steps, firstly the default properties and secondly user customised properties. The location where the customised, site-specific BIS-Grid configurations are stored must be set in the UNICORE Atomic Services properties file uas.properties . This can be found in the UNICORE configuration folder unicorex/conf/ :
The BIS-Grid engine engine is ready for using a service certificate that can be used to establish secured SSL connections to other hosts providing Grid Services or even to enable a secured communication between the BIS-Grid engine and the WS-BPEL workflow engine or external services. The following configuration defines a key- and truststore that includes a BIS-Grid certificate.
| Property Name | Description | Default Value |
| bisgrid.keystore.file | Path to the Keystore file, where the BIS-Grid Engine credentials are in | none |
| bisgrid.keystore.password | Password for the Keystore file | none |
| bisgrid.keystore.type | Type of the Keystore file | jks |
| bisgrid.keystore.alias | Alias for the Certificate used for outgoing connections | none |
| bisgrid.truststore.file | Path to the Truststore file, where the BIS-Grid Engine credentials are in | none |
| bisgrid.truststore.password | Password for the Truststore file | none |
| bisgrid.truststore.type | Type of the Truststore file | jks |
| Property Name | Description | Default Value |
| bisgrid.deployment.directory | An absolute Path to the directory where the Management Service stores all BIS-Grid Deploymnet Packages | deployment |
| bisgrid.xacml.policy.directory | The directory (relativly to the unicorex directory) where the XACML Policies for the workflows should be stored. | conf |
| bisgrid.cleanup.working.directory.on.startup | When the UNICORE 6 container is restarted, all information of deployed workflows will be deleted. This affects only the directories for deployed workflows in the deployment directory. Such an directory contains e.g. the created ActiveBPEL deployment package or the unpacked BIS-Grid Deployment Archive | false |
| bisgrid.deploy.workflow.packages.on.startup | It is possible to put BIS-Grid deployment archives into the deployment directory. If this configuration is true, the engine deploys all of the archives on startup. check.for.duplicate.workflow.names | false |
| check.for.duplicate.workflow.names | If true, the Workflow Management Service checks if there is already a workflow deployend with the same name so that it is impossible to overwrite existing workflows. | false |
The following configurations are used for the Workflow Serivce instances:
| Property Name | Description | Default Value |
| bpel.soapaction.url | Soap Action Prefix for operations that must be forwarded to the BPEL engine | http://bisgrid.de/bpel |
| bisgrid.externalcall.handler.out | Comma seperated list of Classes (subclass of org.codehaus.xfire.handler.AbstractHandler ) that should be inserted into the HandlerPipeline for outgoing messages | de.fzj.unicore.wsrflite.utils.LogOutMessageHandler |
| bisgrid.externalcall.handler.out | Comma seperated list of Classes (subclass of org.codehaus.xfire.handler.AbstractHandler ) that should be inserted into the HandlerPipeline for incoming messages | de.fzj.unicore.wsrflite.utils.LogInMessageHandler |
This configurations are to determine the ports for the BIS-Grid Proxy service instance.
| Property Name | Description | Default Value |
| proxy.port | Port of the HTTP Proxy (BIS-Grid Proxy Service) | 8089 |
| proxy.port.ssl | Port of the SSL HTTP Proxy (BIS-Grid Proxy Service) | 8090 |
WS-BPEL workflow engines are described by the following four properties. For each engine, the <id>-part must be substituted with an ID for the engine, starting with 0 and incremented by 1 for each new engine.
Here is an example for configure the BIS-Grid engine to use two engine (one on localhost and one on 123.123.22.12)
bpel.worklow.engine.host_0 = localhost bpel.worklow.engine.port_0 = 8000 bpel.workflow.engine.ssl_0 = true bpel.workflow.engine.type_0 = ActiveBPEL bpel.worklow.engine.host_1 = 123.123.22.12 bpel.worklow.engine.port_1 = 9000 bpel.workflow.engine.ssl_1 = true bpel.workflow.engine.type_1 = ActiveBPEL bpel.adapter_ActiveBPEL = de.dgrid.bisgrid.common.bpel.adapter.activebpel2.ActiveBpelAdapter
| Property Name | Description | Default Value |
| bpel.worklow.engine.host_id | The host name or ip where the WS-BPEL Engine is running | localhost |
| bpel.worklow.engine.port_id | The port where the WS-BPEL Engine is running | 8000 |
| bpel.workflow.engine.ssl_id | Is the port a SSL Port? | false |
| bpel.workflow.engine.type_id | The type of the BPEL Engine. The type is needed to the right Adapter for the BPEL engine | ActiveBPEL |
| bpel.adapter_ TypeName | The class where the Adapter for the TypeName WS-BPEL Engine can be fourd. This Property has no id. Hence no _1 or something like that | de.dgrid.bisgrid.common.bpel.adapter.activebpel2.ActiveBpelAdapter |
This are additional properties introduced to enable deployment and undeployment on the ActiveBPEL Workflow Engine with the help of the ActiveBPEL Adapter. At the moment it is assumed that the engine runs on the same machine as UNICORE 6 so that a direct access to the bpel.workflow.engine.deployment.dir_id is possible.
| Property Name | Description | Default Value |
| bpel.workflow.engine.deployment.dir_id | bpr-Directory, where the deployment packages (bpr) are located | none |
| bpel.workflow.engine.persistence_id | Is persistance activated for this engine | false |
| bpel.workflow.engine.persistence.db_driver_id | Class of the driver to connect to the Database | org.gjt.mm.mysql.Driver |
| bpel.workflow.engine.persistence.db_host_id | Host where the database is running on | localhost |
| bpel.workflow.engine.persistence.db_port_id | Port to connect to the database | 3306 |
| bpel.workflow.engine.persistence.db_username_id | username for the database | ActiveBPEL |
| bpel.workflow.engine.persistence.db_password_id | password for the database | ActiveBPEL |
| bpel.workflow.engine.persistence.db_database_id | database name | ActiveBPEL |