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 ?

[dkhanna01]

I knew this will come from you I checked this yesterday in my setup and I had this checked (for TCP) in the identification section for MYDBServer as shown in screenshot (please note XVIODB = MYDBServer):

OH BTW I was talking to John Klassen yesterday and he told me that you helped him a lot on the mapping stuff

[dkhanna01]

I don't know if this is helsinki or something wrong in the setup, but my CI type is treating this as a "Generic Application"

[jake_mckenna]

Did you activate the pattern and the connectivity pattern? I know John warned you on that, but always good to ask.

[dkhanna01]

Yep absolutely, I activated the patterns.

[glennpinto]

If your app is discovered as a generic app it is either not being tried or one of the steps in your pattern are failing which is defaulting it to use the generic pattern. You should be able to view the discovery log by right clicking on the generic app on your map and seeing if your pattern is tried, if it displays, note which step is failing and fix it. If it does not display as being tried in the discovery log, your pattern is being filtered either by the OS defined at the pattern level or as Jake mentioned within the entry points used for the identification section.