Discovery Pattern to create new entry point

[dkhanna01]

I'm trying modify discovery pattern for JBoss. I have   this HPUX host (which is essentially my DB server) that connects to my JBoss application via TCP. Here are the steps that I'm taking:

Pre-requisite: Created a table by the name "MYDBServer Entry Point" and extend that table with "Endpoint"

                                              This created a table by the name "u_mydbserver_entry_point"

Inside Discovery Pattern

1. Created a connectivity section as "MYApp to MYDBServer"

2. Step1: fetch the host name from config file

3. Step2: fetch the port name from config file

4: Step3: Connect to MYDBServer

        Connection Type: Application Flow

        Entry Point: MYDBServer Entry Point

                Connection attribute

                host: $host_name

                port: $port_name

These hostname and port names are all correct and I've already verified that. Now when I try to use "TCP as my entry point I can see that service mapping does connects to the host_name at port $port_name. But when I'm using "MYDBServer Entry Point" the Discovery log says "no entry point for u_mydbserver_entry_point".

What am I missing here ?

[jake_mckenna]

From how it sounds you should not need a new entry point type and can use the OOB TCP connection. However you many need to setup a new table or identification pattern to use to capture the information needed to indicate this is you MyDBServer. I think you might be running into a problem binding to the process, which can be resolved by changing your entry point type to just the standard TCP connection.

[dkhanna01]

Thanks Jake. All I need to find out on the MYDBServer (after TCP connection is establish) is the number / count of the processes running on.$port_name. I might have 30-40 number of processes running on the same port that I need to show in my service mapping.

[dkhanna01]

I've defined table for MYDBServer and also the Discovery Pattern as MYDBServer corresponds to the table. Then in discovery pattern, I change my "Target CI Type" as MYDBServer. But in the discovery the application is treating it as "generic Ci Type" instead of MYDBServer

[jake_mckenna]

So based on this are you seeing it use your pattern in the Discovery log? One step that it doesn't sound like you did, I forget this sometimes too, is adding the entry point type to you identification pattern. In this case the TCP one to make sure that triggers your pattern. See my screenshot. Define the identification section