Service Map pattern is not consistently discovering properly

[Michael Lineba2]

I have a pattern created from a generic pattern.    This specific pattern detects and identifies the application properly, then by the next morning on one server it does not find the running app, but identifies as a Generic application.   

The pattern is identifying a z3950 Gateway application running on 2 servers.     Server1 is consistent and is working as expected with identifying the app running on the server, however Server2 does not.     Every morning when I open the map Server2 is identified as a generic application of z3950. 

I do a quick discovery of the IP for Server2, then rediscover the map.     Then Server2 is identified correctly and is using the pattern created for z3950 Gateway.     By the next morning Server2 is again a Generic Application of z3950.

I do not see any specific reason for this behavior.     

Ideas?

[emily1]

Have you created a process classifier that will launch the pattern when the process is detected? Make sure the conditions in the classifier match the separate processes running on both of the servers so it will launch for both of them.