Need a clarification in regards to default xml manager.
In our environment(SVP)we have created a custom application domain and a custom XML manager for the same domain.
All the services are configured in that custom application domain and it uses the custom XML manager(not default XML Manager).
During some test run i noticed that in the "HTTP Connection Statistic" even the default XML manager getting requests. I can confirm no objects(WSP or MPGW)are hooked to the default XML manager in that application domain.
So wondering what work is the default XML manager doing in that application domain?
Would really appreciate if anybody clarify my doubt..
Thanks in advance.
NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
This topic has been locked.
5 replies Latest Post - 2013-01-17T00:30:53Z by DP_KumarP
Pinned topic Default XML Manager
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Updated on 2013-01-17T00:30:53Z at 2013-01-17T00:30:53Z by DP_KumarP
swlinn 100000E7QE1346 Posts
swlinn 100000E7QE1346 PostsACCEPTED ANSWER
Re: Default XML Manager2013-01-15T03:45:51Z in response to DP_KumarPHi Kumar,
I assume you'd done an export and you don't see any references to the default xml manager? If so, all I can think of is there are some implicit usages of the default XML manager, but I don't have insight as to what that would be. This just goes to show though that you should NEVER change the default XML manager as those changes could be applicable in places where you don't expect them. Perhaps Hermann can look at the DP code to give some clues here???
HermannSW 2700006U544481 PostsACCEPTED ANSWER
Re: Default XML Manager2013-01-15T13:26:52Z in response to swlinnI looked up the box configuration, and internal stuff (Webgui, Probe, ...) uses internal (invisible) XML managers.
I logged on two of my boxes and see only 0 entries for default XML manager.
You should just look how long you have to wait for a change in HTTP Connection Status for default XML manager.
Let's say it changes every three minutes, then just take a packet capture for 3:30min, or have extensive logging in order to identify all transactions in that time.
Re: Default XML Manager2013-01-17T00:30:53Z in response to HermannSWHi Hermann,
Thanks for your reply. Will try the Packet Capture.
I checked the complete Application Domain but nowhere i can see any objects making any reference to the Default XML Manager.
We have the WSM Agent enabled on that Application Domain..Will that be accessing the Default XML Manager along with other XML Managers?