Hello All,In my Prod environment,Jobs folder is not appearing under TIBCO folder while monitoring Tibco BW 5.12 while it is appearing in UAT for the same agent and i have cross checked and found same configuration.I have gone through with case '00046195' in CA Support but that case is different as shows details about 'Jobs Created Per Hour should be equal to the NumberCreatedPerHour of GetProcessStarters method'. I am attaching one screen shot which shows 'jobs' under 'TIBCO' for reference.Please help.ThanksVaibhav
I see you also logged new case 00251828 for this problem.
You have updated to say that after a patch file transfer to Production (Solaris) you have found extra ^M characters at the end of the lines of some of the TIBCO pbd files including the tibcobw-toggles-full.pbd which has the tracers for Job/JObPool tracing i.e
Yes those extra ^M characters would definitely cause a problem so please re-transfer the files in ASCII mode from Windows to Unix (Solaris) which should prevent the extra ^Ms from being present.
Yes, '^M' character is added in following lines under file 'tibcobw-toggles-full.pbd'
So you want me to re-transfer this file into ASCII mode from Windows to Unix(Solaris) so I will be using command 'dos2unix tibcobw-toggles-full.pbd tibcobw-toggles-full.pbd' or you want me to use anyother command so plz suggest.
Let me know any other scenario which can restrict 'Job' folder not be generate.
You can EITHER repeat the file transfer (ftp/winscp etc) using ASCII/text mode OR run the dos2unix command on all files which have ^Ms (only 1 of those options is needed)
If that file correction followed by BW Process/agent restart does not fix the problem then we will investigate further via the case.
To promote the file into production is required very big process to follow
hence I will try to use dos2unix.
Does it require agent restart after this change.
Thanks & Regards
Senior Consultant for APM
On Nov 24, 2015 11:44, "Lynn_Williams" <
Yes agent will need a restart to force a re-read of the modified pbd file.
With current ^Ms in the file:
If AutoProbe was not running you would not see any useful monitoring so it looks like it must have started. So it may be ^Ms did not cause a load failure but expected Job related Tracing still is not running due to the ^Ms.
Once the file(s) are healthy we can go from there if problem still persists.
Logs could not generate as improper permission on log folder hence can update on the same so I will restart the agent after this change.
We removed '^M' character and restarted the service and that service is having internal job that is 'writing to a log file' but job folder was not created in Production and then we started the same service in UAT(where everything is working fine) and job folder was not created also here. It seems that agent did not consider it as a job.
Please suggest, agent will consider which/what as a job so that we can try to create the service for testing purpose.
We have mass agent deployment by this weekend so I need to know if 'Job' folder would not present in production then what we have to do.
Please let me know as we have deployment over this weekend and what I can suggest to client to take as precaution or caution.
Many thanks in advance.
It sounds like this is a good point to open a case to resolve issues since analysis is likely needed rather than simple answers
These symptoms could also be related to the overloaded Collector that we have diagnosed for the case logged for the missing 5.9 agent problem. Once we sort out that problem we can then see what other ones remain.
Let me correct you, Our Agent version is 9.1.4+Patch(certified by CA) to
support BW 5.12
If this also looks like collector overloading then how come only 'job'
metrics is not present for all the application.
On Dec 4, 2015 05:31, "Lynn_Williams" <