Approvals engine data source
Used to access the FTM database.
| Property | Value | Description |
|---|---|---|
| Scope | Stand-alone Server Install: Node Cluster Install: Cluster |
Scope specifies the level at which the resource definition is visible. Any valid scope
can be selected. For a stand-alone server install, the JDBC data source is to be configured at the node level, for example: Node=izhNode. For a cluster install, the JDBC data source is to be installed at the cluster level, for example: Cluster=FTMCluster. |
| Data Source Name | APV Engine Data Source | Name of the JDBC Data Source |
| JNDI Name | jdbc/apv/engine/BaseDB | The Java™ Naming and Directory Interface (JNDI)
name. Note: The value for this entry must be exactly as shown.
|
| Component-managed authentication alias | APV Engine JAAS Alias | Name of the Approvals engine JAAS alias |
| JDBC Provider | APV Engine DB2® Provider | Name of the DB2 JDBC provider that supports this data source |
| Database name | Customer specified | Name of the FTM database |
| Driver Type | 4 | DB2 driver type. Must use the type 4 driver. |
| Server name | Customer specified | Name of the server that contains the database |
| Port number | Customer specified | Port number to use for accessing the database |
| Container managed persistence (CMP) | true | Specifies if this data source is used for container managed persistence of enterprise beans |