Trusted connections preserve the identity records of clients that are connecting to a DB2® database through MashupHub. Trusted connections can provide a more secure environment by granting access based on the identity of the users and can take advantage of the connection pooling in WebSphere® Application Server.
To set up trusted connections, you add one or more resource references to the MashupHub web.xml
file and enable trusted context for the DB2 databases in WebSphere Application Server. If you want to set up trusted context using the WITH AUTHENTICATION option, you write a custom DataStoreHelper class that implements a specific method. These steps are performed by the MashupHub administrator. You do not need to be connected to the DB2 database to configure trusted context for MashupHub.
Configuring trusted context on a single server: imc3
To configure DB2 trusted context on a single server, you configure the data source and the JDBC provider for the databases with trusted context, create a resource reference in MashupHub, and enable trusted context in WebSphere Application Server.
Configuring trusted context in a cluster configuration: imc3
To configure DB2 trusted context in a cluster configuration, you create the JNDI data source for the cluster, create a resource reference for the cluster, map the resource reference to the JNDI datasource, and enable trusted context with authentication in WebSphere Application Server.
Parent topic: Database feed configuration: imc3