Creating accounts

Using Database facilitates you to create and run services that run transactions to retrieve data from, and insert and update data in, relational databases.

1. Click Connectors.
2. Search for Database in Available Connectors and select Database.
3. Click New account.
4. Provide the action name and description for the account in the Add account page.
5. Enter the details in the Add account wizard.

   Name

   Name for the account you want to add.

   Description

   Short description for the account you want to add.

   Database

   Database you want to connect to.

   Driver Group

   Driver group used to connect to the database. Lists the prebundled drivers available and the drivers that are uploaded in the database connector. For more information, see Pre-bundled drivers. You can upload a new JDBC driver by selecting the Add icon next to the Driver Group list. You can upload just the certified jars. For more information, see Adding drivers.

   Data source Class

   The data source class to be used. This field specifies the name of the JDBC driver’s data source class.

   Server Name

   Name of the server that hosts the database.

   Note: If the tenant cannot connect to the cloud database, then check the security settings of the cloud database.

   User Name

   Username associated with the account on the database server.

   Password

   Password for the specified user name.

   Database Name

   Name of the database to which you are connecting.

   Port Number

   Port number that is used for connecting to the database.

   Truststore Alias

   Alias of the truststore configuration. The truststore contains trusted certificates that are used to determine the trust for the remote server peer certificates. You can also add a truststore certificate by selecting the Add icon next to the Truststore Alias list. For more information, see Projects chapter.

   Keystore Alias

   • Alias for the keystore configuration.-

     You can add a keystore certificate by selecting the Add icon next to the Keystore Alias list.

     For more information, see Projects chapter.

   • Network Protocol- Network protocol that the connection must use when connecting to the database. Type TCP or TCPS to indicate the network protocol.
   • Other properties- Configure the Property Name and Property Value by selecting from the list or typing the name if not listed, and enter the corresponding value. Click + to add a property.
     • Property Name - Name of the property. You can select the property from the list or type the property name when it is not listed.
     • Property Value - Value for the property.
     Note: Properties listed for you to select from the list are driver-dependent.

     Example 1. You can use this field to choose a property such as TableFilter. You can either select or type the TableFilter property in the list and enter the <current catalog>.Accounting in the input text field. Use {} to configure a combination of multiple key-value pairs.

     Example 2.

     *connectionProperties={oracle.jdbc.V8Compatible=true,includeSynonymns=true }

     By default, the loginTimeout is set to 60, which is the time (seconds) that a connection waits to connect to a database. The <current catalog> represents the default catalog that is associated with an account. The <current schema> represents the default schema that is associated with an account.

6. Click Next. The Advance Setting page is displayed.
7. Provide the details in the Advance Setting page to configure connection pooling manually.
   Note: Connection pooling is not enabled by default.

   • Enable connection pooling- Toggle the slider to the right to enable manual configuration of the connection pooling details. Disable the connection pooling to use system-defined values.
   • Minimum and maximum Pool Size- Minimum and maximum connection pool size for this account Minimum Pool Size- Number of connections to create when the connection is enabled. The system maintains the specified Minimum Pool Size of connections, irrespective of whether these connections remain idle. Maximum Pool Size- Maximum number of connections that can exist at a time in the connection pool.
   • Block timeout- Number of milliseconds that IBM® webMethods Integration waits to obtain a connection before it times out and returns an error. For example, if you have a connection pool with a maximum size of 20 and receive 30 simultaneous connection requests, 10 requests are queued, waiting for an available connection. When you set the Block timeout to 5000, each of the 10 requests waits up to 5 seconds for a connection before timing out and returning an error. When the services take 10 seconds to complete and return connections to the pool, queued requests fail due to unavailable connections. Setting a high Block timeout can cause similar failures. Also, if a request has errors that delay its response can block other requests from being sent.

     This Block timeout must be tuned along with the Maximum Pool Size setting to accommodate such bursts in processing.

   • Expire timeout- Number of milliseconds that an idle connection can remain in the pool before it is closed and removed from the pool. The connection pool removes idle connections until the number of connections in the pool is equal to the Minimum Pool Size. The timer for an idle connection is reset when the connection is used. If you set the Expire timeout value too high, the connection pool might accumulate numerous unused and idle connections. It uses the local memory and also ties up a connection on your backend resource. It might have an adverse effect when your resource has a limited number of connections. If you set the Expire timeout value too low, the performance might degrade because of the increased activity of creating and closing connections.

     The Expire timeout must be tuned along with the Minimum Pool Size setting to avoid excessive opening and closing of connections during processing.