Hi Pramod, that screen shot is your JDBC adapter connection. That is used for connecting your integrations running on the Integration Server to your database that contain application data.
For the CDS, you need to configure the appropriate JDBC pool. In the IS Admin UI, navigate to Settings → JDBC pools. This is where you connect the various components that run on the IS to the database(s).
You will noticed a Functional Alias Definition for CentralUsers. This needs to be associated with a database pool. I have attached screen shots.
So on this page first make sure your JDBC pool(s) are setup properly, then associate the pool with the CentralUsers functional alias. See screen shots below.
As mentioned previously, the database you “point” to from the JDBC pool alias must contain a database component called CommonDirectoryServices (which are basically a set of tables).
You can verify if this is setup by running the wM Database Component Configurator tool, and connecting to the database (on the Input tab, select Action Type of “catalog” then fill in the db connection info), then at the bottom, click the Execute button. When it’s done, you should see the installed (db) components in that database. For example, for CDS you should see CommonDirectoryServices in the Results.
If you don’t see it, you have to create it. You can do this in the DB configurator tool. Click the Input tab, and select action type of Create and Version of latest. Then select radio button “Component” and select CommonDirectoryServices.
Click the Execute button. If your DB URL, user and password are good, then this component tables will be created. You can use the type = catalog to double check.
The JDBC pool mentioned above has to point to the DB URL you created the CommonDirectoryServices in.
Do you have your IS JDBC pools setup?
#webMethods#Integration-Server-and-ESB