Connections allow Unwired Server to communicate with data sources. To facilitate the connection process, define a set of properties for each data source.
A connection is required to send queries to mobile business objects, and to receive answers. The format in which data is communicated depends on the type of data source; for example, database data sources use a result set, while Web services data sources provide XML files, and SAP data sources use tables.
Establish connections by supplying an underlying driver and a connection string. Together, the driver and string allow you to address the data source, and provide you a mechanism by which to set the appropriate user authentication credentials and connection properties that describe the connection instance. Once a connection is established, Unwired Server can open and closed it as required.
Unwired Server maintains database connections in a connection pool, which is a cache of database connections for the consolidated database (CDB) or any other database data source.
A connection can be reused when the database receives future requests for data, thereby improving Unwired Server performance. If all the connections are being used, and the maxPoolSize value you configured for a connection pool has not been reached, a new connection is added to the pool. For Unwired Server, connection pools are based on an existing template created for a specific data source type.