There are many activities owned and performed by PC Admin.
- PowerCenter Repository & Domain Backups on day to day or weekly/monthly basis.
- Configuration and Management Of Users/Groups/Roles in PC, this wouldn't be daily activity.
- Configuration of security domains and Scheduling Synchronization of the users/group with LDAP directory service, if you use LDAP security Domain, not a daily activity.
- Managing the deployments (Labels, folder, deployment groups) and conflict resolutions, not a daily activity.
- Configuration and management of different types of nodes while installing PC.
- Configuration and management of application services, license service etc.
- Grid Responsibilities if your PC is running on Grid.
Do PC Admin will have performance tuning?
It depends. If the admins are experienced with PowerCenter, the underlying operating system, and/or the applications implemented in PowerCenter, then it does make sense that they cooperate with the developers for performance tuning.
If they are by no means involved in PowerCenter development, then they should at least be able to support analysing workflows in order to identify bottlenecks, but of course in such a case this cannot be too thorough...
what are the informatica tables are frequently admin/production support team will use it?
I need to collect all workflow details, session details & Mapping details. How & where can i take those details?
What are the informatica tables are frequently admin/production support team will use it?
I need to collect all WF,session & mapping details. How & where can i take those details?
It's very difficult to open each & every WFs.
It's neither useful nor necessary to open single workflows to obtain this information.
You can retrieve all these items and numbers from the repository itself. Part of each PowerCenter repository is a set of database views which grant safe access to metadata, be it structure metadata (e.g. mappings, workflows, and the like) or execution metadata (runtime info plus numbers of successfully and unsuccessfully processed records and the like).
Please consult the Repository Guide for more information about the MX views.
BTW you can build mappings which use the MX views as a source, but you'll have to "trick around" in order to make PowerCenter import them. There are some posts around this topic, just search for the keywords "import metadata exchange views PowerCenter".
thank you for your concise answer on the admin task.
Can you please develop what you had done to automate administrative tasks using infacmd/infasetup for
daily repository and domain backup?
I am looking for a KB article or more detail in the documentation.
thank you in advance
The activities to be performed here are not provided by Informatica and hence the hunt for a KB article is not an option.
You might need to check if someone else has attempted to achieve the same and have successfully implemented (should be done/achieved by most of them). If yes then someone may help you with the steps.
As far as the infacmd/infasetup commands to take repository backup and domain backup daily is concerned, it should be a simple script that needs to be executed daily.
You can have the script executed daily by a cron job or crontab.
Just be careful that repository backup and restore processes are executed with different tools for different Informatica products.
For PowerCenter, repository backup and restore processes are executed via the command-line utility pmrep.
For all model repositories, backup and restore processes are executed via the command-line utility infacmd.sh (resp. infacmd.bat on Windows).
It is also imperative to cleanly distinguish between the actual application services in the Informatica domain (such as repository services of all kinds, integration services, data integration services, and so on) and the repository contents underlying each repository service. Services are always managed via infacmd.sh (resp. infacmd.bat on Windows), but repository contents are handled differently (see the start of my reply).