Error parsing file envmetadatadatamatchers.xml

Hello,

Yesterday I was caught up with a strange issue with CA while tried to view the environment info through CA. As soon as I was clicking the VIEW button, the CA was getting closed. After search with the log files of agents, viewer and CA, I noticed one error message in the CA log file...

EMF_CATEGORY - Error parsing file envmetadatadatamatchers.xml.
EMF_CATEGORY - Error parsing file envmetadatadatamatchers.xml.

I got nothing after extensive search what got missed and why this error message is coming up. There is actually no such file which was getting logged in the log file i.e. "envmetadatadatamatchers.xml" if we talk about CA specifically. But what if you can break this file name something like: "envmetadata data matchers.xml"?

Yes, this is where the CA viewer first looks to create the report and this file was missing from PS_HOME\PSEMViewwer\envmetadata\data\matchers.xml. Before start of my CA activity, I did a cleanup of the EMF HUB, Agent and Viewer and accidentally deleted matchers.xml...which should not get delete from any of the directory, neither from Agent's directory, nor from Viewer directory.

Hope this will be of some help to you sometime...

Change Control Security

Change Control Security

If you have been gone through issue like Change Control has been enabled, however, any user can unlock the definition of any other user's definition, then this is because of Change Control Security level setup which your administrator has been set according to instance. There are three types of access can be assigned if it comes to Change Control.


Restricted access
Developer access
Supervisor access


Using the Security component, you can assign users one of three Change Control access levels, depending on how much authority you want them to have. Below is a brief description about these different access levels.

Restricted access

This is top security level which can be setup to keep in mind that apart from admin, no one can chage/lock/unlock any other user's definitions. This restricts users from locking or unlocking definitions. When Change Control locking is enabled, users with this kind of access can open PeopleSoft Application Designer development definitions in read-only mode only untill and unless admin help.


Developer access

This is for DEV instances which allows users to lock any unlocked definitions and to unlock any definitions that they have locked. This allows users only to deal with their OWN definitions, not other's. They can then manipulate their owned definitions, as per their security profile.

Supervisor access

This is a generic level, can say for just INFO only to users among themselves. This access allows users to unlock any locked definitions, regardless of who locked them and lock the same by their profile. They can also access the Change Control Administrator dialog box, in which one can lock and unlock all definitions at one time and enable and disable Change Control locking and history. As per first comment, this kind of access is INFO only type, where one user can know who has locked this definition and accordingly take action / manipulate definition.







Note: Some contents have been taken from PeopleBooks...