Upload
ravi5dipu
View
141
Download
1
Tags:
Embed Size (px)
DESCRIPTION
KT Document for PeopleSoft
Citation preview
Oracle APPS DBA Support Knowledge Transition Document / Template
For
LOGITECH Worldwide
Version No. 1
Prepared By Reviewed by Approved By
Name Anil Kumar RanaRole Project Lead
Signature
Date 20-May-2008
1
Oracle Applications Knowledge Oracle Applications DBA Support knowledge Transition Document
CCHANGEHANGE L LOGOG
Date Version Author Change Reference
ReviewersVersion Name Review Date Role
2
Oracle Applications Knowledge Oracle Applications DBA Support knowledge Transition Document
Table of Contents
1.0 Introduction 4
1.1 Purpose of the document 4
1.2 Objective 4
2.0 Scope of Engagement: 5
2.1 Scope 5
2.2 Out of Scope (Exclusions) 6
3.0 Instance Management 6
3.1 Available Instances 6
3.2 PeopleSoft Applications 7
4.0 KT Approach 8
4.0.1 Architecture overview 8 4.0.2 Code Migration (SLAs) 9 4.0.3 Approvals 10 4.0.4 Cloning 11 4.0.5 Patching 12 4.0.6 High Availability 12 4.0.7 Backup Policies 13 4.0.8 Key DBA tasks 14 4.0.9 Useful Scripts details 16
5.0 Service Request Handling 17
5.1 Types of service requests 175.2 Contact Numbers for Support 17
6.0 Source Code Management 18 6.1 Code Migration methods / tools 18
7.0 Escalation Mechanism 15
3
Oracle Applications Knowledge Oracle Applications DBA Support knowledge Transition Document
1.0 Introduction
1.1 Purpose of the document
This document is an output of the Logitech KT phase. It details the Applications
system under maintenance and the maintenance approach for the same as DBA
perspective. This document is a deliverable to Logitech Inc. as part of the
applications KT phase for applications DBA Support and has to be validated by the
appropriate personnel from Logitech Inc to ensure that Cognizant Technology
Solutions has understood the business process mapping in the Applications DBA
support, correctly. It is of extreme importance, therefore, that the Logitech
personnel responsible for validating this document do so with due consideration.
Cognizant Technology Solutions would like to thank Logitech for their co-operation
to help Cognizant in understanding the System Process addressed through
Applications, Database and application support.
1.2 Objective
To be able to acquire sufficient knowledge about the Applications System at
Logitech for DBA Support.
To be able to acquire the sufficient knowledge about the business process
mapped into the applications system for database administrator support.
To understand the process followed in the area of applications system
maintenance and support.
To be able to set up plans and procedures to perform maintenance activities
and guidelines.
4
Oracle Applications Knowledge Oracle Applications DBA Support knowledge Transition Document
2.0 Scope of Engagement:
2.1 Scope
24*7 Database administration for all in-scope applications in respective environments
Start / shutdown of concurrent manager, database instances, administrative jobs
Database space management
Database performance management
Database security management
Database change management
Database patch management
Database backup, restore, and refresh
Expected volume for Oracle Apps – 3-5 times per month for 2 instances
(OLTP, Planning) Expected volume for PeopleSoft – 2-3 times per month
Report refreshes – automated end-to-end
Proactive monitoring of database status in the above respects
24*7 support expected to users except during weekly maintenance window of 14
hrs from Sun 12 midnight PST to 2 pm PST Initiating and resolution of trouble tickets as per documented process and
notification to concerned parties Expected volume of user-initiated Database Service Requests: 15 to 20
per day (75% Critical, 25% Normal) currently, expected to go to 30-35 per
day with the new applications being implemented Monthly reporting of database status on the above aspects
24*7 Application monitoring of all the in-scope applications in respective
environments
Start / shutdown of applications and application components
Proactive monitoring of applications and application component status
24*7 support expected to users except during weekly maintenance window of 14
hrs from Sun 12 midnight PST to 2 pm PST
Initiating and resolution of trouble tickets as per documented process and
notification to concerned parties
Monthly reporting of application uptime / downtime status
5
Oracle Applications Knowledge Oracle Applications DBA Support knowledge Transition Document
Code Migration for the in-scope applications from Dev to QA and QA to
Production environment
Performance tuning during Development to QA migrations
Dev to QA migrations
Expected volumes for Oracle ERP – 5 to 10 per day
QA to Prod migrations
Performed during weekends
Expected volumes for Oracle ERP – 5 to 10 per week
Expected volumes for all other applications (apart from Oracle ERP) total for Dev
to QA and QA to Prod migrations – 15 to 20 per week.
2.2 Out of Scope (Exclusions)
The following services are out of scope for the purpose of this proposal:
Major Application Upgrade
Any Functional Analysis & Functional Support
Infrastructure, Hardware, Software Licensing & Support
Impact Analysis in the Release and Change Management Process
Vendor / license management and interaction with product vendors for activities
not related to support Database Portfolio Management and database design
3.0 Instance Management
3.1 Available Instances
Server Instance Instance TypeAIX 5.3 1 ProductionAIX 5.3 1 QAAIX 5.3 1 Development AIX 5.3 1 TestAIX 5.3 1 Demo
6
Oracle Applications Knowledge Oracle Applications DBA Support knowledge Transition Document
3.2 PeopleSoft Applications
Various PeopleSoft instances used in Logitech are mentioned in the table below:
Instance Database Apps &
Web TierBatch Server Purpose Location PeopleSoft File
systemowner
HR89PROD us04pd02 us04pa03 us04pa03(Unix), us04pr03 & us04pr04(Windows)
PeopleSoft Production
Boulder oracle
HR89QA us01u79 us01u79 us01u79 (Unix), us04dp02(windows)
PeopleSoft QA
Fremont oracle
HR89TEST us01u79 us01u79 us01u79 (Unix), us04dp02(windows)
PeopleSoft TEST
Fremont oracle
HR89DEVL us01u78 us01u78 us01u78 (Unix), us04dp02(windows)
PeopleSoft Development
Boulder oracle
HR89DEMO us01u78 us01u78 us01u78 (Unix), us04dp02(windows)
PeopleSoft Demo
Boulder oracle
7
Oracle Applications Knowledge Oracle Applications DBA Support knowledge Transition Document
4.0 KT Approach
4.0.1 Architecture overview
The main purpose of PeopleSoft in Logitech is: Global HR management Personal goals management Manager Self Service Employee Self Service
The Oracle sql account is sysadm. The file system owner on windows portal is psadmin. In PeopleSoft, to manage the application, each person will need their individual
accounts. All the authentications & alerts of PeopleSoft come on Lotus Notes. The version of PeopleSoft utilities used has been mentioned below:
People Tools 8.47. HRMS 8.9. Web logic 8.1 SP5. Micro Focus Server Express 4.0 SP1. Tuxedo and Jolt 8.1
The architecture of PeopleSoft can be understood from the figure below:
8
Oracle Applications Knowledge Oracle Applications DBA Support knowledge Transition Document
The Oracle Database version for all the environments is 10.2.0.2. Psadmin is an important tool which helps in managing Application Server &
Process Scheduler. Production is a Multi Node Installation. Rest all the other Environments are
Single Node. Web Server & COBOL are running under root user account. The URL for HR89PROD is http://atlas.logitech.com The URL for HR89QA is http://us01u79.logitech.com/hr89qa/signon.html The URL for HR89TEST is http://us01u78.logitech.com/hr89test/signon.html The URL for HR89DEVL is http://us01u78.logitech.com/hr89devl/signon.html The URL for H89DEMO is http://us01u78.logitech.com/ps/signon.html Storage for Production is done on NetApp.
4.0.2 Code Migration (SLAs)
Requests come via ITG. The Code Migration workflow is QA PROD. Most production migrations done on Sunday except business critical. While migrating code to Production, following process must be followed:
Log in to us01dp02. Click on Application Designer & login as psoft. Click on tools. Click on Copy Project. Select From File. Select the project which needs to be migrated on the Select Project
window. Click on Select. On the Copy from File window, select Use project definition as File. Click Ok. On the next window, click on Options. On the Copy Languages window, click on Select all. Click ok. On the Copy from file window, click Copy. The Copy in Progress Window opens. After successful copy, the window closes. Click on Build tab. Click on Settings. Make sure that the Skip table if it already exists, Recreate view if it
already exists & Recreate index only if modified options are always clicked unless specified otherwise by the user.
Close the Settings window. Click on Build tab. Click on Projects. Check the Create table option. Click on Build. Go to the temp folder on the windows machine & check the Log file for
any errors.
9
Oracle Applications Knowledge Oracle Applications DBA Support knowledge Transition Document
While doing a SQR migration, following process needs to be followed: Open the ITG Request for code migration. The request might have the sqr file attached or the user may provide an
accessible path to pick the file up. While copying the file to UNIX servers, please use ASCII mode and file
name should remain in lowercase. Depending on the request, the file needs to be copied to any of the
following folders: us01u78 : /apps/psoft/user/sqr us01u79 : /apps/psoft/user/sqr us01dp02 : /apps/psoft/user/sqr us04pr03 and us04pr04 : /apps/psoft/user/sqr us04pa03 : /apps/psoft/user/sqr
4.0.3 Approvals
All code migrations requests are approved by Ajay Dutt or Larry Leong.
10
Oracle Applications Knowledge Oracle Applications DBA Support knowledge Transition Document
4.0.4 Cloning
Usually source is the HR89PROD for cloning. HR9DEMO is never cloned; it is maintained as the Gold copy and should not
be touched. During cloning/refresh the following process needs to be followed:
Copy the dbf files from source filer to target & check that all the files are properly copied.
Create the database for the target. Once the database has been created successfully, change sysadm
password to appropriate password. Log in to us01dp02. Navigate to D:\psoft\DBA folder. Run resetpswd.dms as sysadm by reflecting the right sysadm
password. Run following sqls from us01u78 or us01u79:
/u01/app/oracle/admin/scripts/DBREF89 ref_ajay.sql refresh_89.sql For hr89devl, run
update_report_node_definition_u78.sql For hr89qa/hr89test, run
update_report_node_definition_u79.sql Log into sqlplus of the target database. Truncate psren and psoptions table. Import from us01u78 or us01u79:
/u01/app/oracle/admin/scripts/DBREF89 exp_dbname.dmp file.
For hr89devl, start apps and batch servers on us01u78. Web server is usually up and not bounced as it is not
dependent on the Database. For hr89qa/hr89test, start Apps and Batch servers on
us01u79. Web server is usually up and not bounced as it is not
dependent on the Database. Do the integration broker setup. Login to the refreshed instance e.g. hr89test, hr89qa or
hr89dev using your personal PeopleSoft administrator’s ID. Click on PeopleTools Click on Integration Broker. Click on Monitor Integrations. Click on Monitor Message. Click on Domain Status. On the Domain Status page, select All Domains to be Inactive. Click Update to change the status of all domains to Inactive & all
dispatchers to Cleanup. Click “Force Reset” button to change the status of all dispatchers to
Inactive. Login into Data mover in us01dp02 and remove the data from the live
message tables by running the below 2 DMS scripts:
11
Oracle Applications Knowledge Oracle Applications DBA Support knowledge Transition Document
D:\psoft\DBA\Database_Refresh\ AppMsgPurgeLive.dms. D:\psoft\DBA\Database_Refresh\ AppMsgPurgeAll.dms.
Login to PeopleSoft again & rename the desired node definition. Navigate to Configuration Gateway Search. Click on Local Gateway & Change the gateway server to match the
refreshed instance. Click “Save”. It asks to update, say yes. Click Ok. Navigate to Integration Broker Integration Setup Node
Definitions HR89PROD. Change description to match refreshed instance and save. Then click
on “Rename Node”. Give the refreshed instance name and click on save. Reboot the web server. Reactivate the messaging domains. For this, login to PeopleSoft & navigate to PeopleToolsIntegration
BrokerMonitor IntegrationsMonitor MessageDomain Status. On the Domain Status page, select All Domains Status to be Active. Inactivate the production domains. Exit the applications. This completes the Cloning process.
4.0.5 Patching
No patching has been done in the past. Usually bundles are received that the HR team tests and then we get a
consolidated procedure as to how to apply the patches.
4.0.6 High Availability
Virtual IP is used for failover. us04pa03 and us04pd02 fail to one another during HA. The HA implementation on PROD can be understood from the figure below:
12
Oracle Applications Knowledge Oracle Applications DBA Support knowledge Transition Document
4.0.7 Backup Policies
Hot backups of PROD are taken daily and weekly using NetApp snapvault. Monthly cold backups are taken by IBM and goes to tap which is sent offsite. Monitor backup Backup processes are monitored by email to the respective
user when threshold value is reached.
13
Oracle Applications Knowledge Oracle Applications DBA Support knowledge Transition Document
4.0.8 Key DBA tasks
Make sure that PeopleSoft on us01dp02 is up & running. (This is the main
service of PeopleSoft on Windows that is shared by QA, TEST, DEMO & DEVL). Start/shutdown the services/instances.
The Startup/Shut Down of PROD is as follows: Shutdown:
Login as psoft on the Apps/WebServer. Go to /apps/psoft/hrms89/appserv. Start the psadmin tool. For this, run the environment file & on
command prompt type pasadmin. Choose the menu options to stop apps and batch server for
the node. Login into Windows as psoftadmin domain user. Stop the psoft service. Login to the Webserver as psoft & shut it down. For this,
follow the following steps:o Sudo . /apps/psoft/hrms89/psconfig.sho Sudo
/apps/psoft/hrms89/webserv/peoplesoft/stopWebLogic.sho Sudo /usr/local/bin/kill_web_process.ksh web and kill any
processes not stopped Login as psoft user on apps server & stop COBOL. Sudo /opt/microfocus/mflmf/lmfgetpv k. Login as oracle on database server. Shutdown the database and listener.
Startup: Login as oracle on database server. Start the database and listener. Login as psoft on the Apps/WebServer.
14
Oracle Applications Knowledge Oracle Applications DBA Support knowledge Transition Document
Go to /apps/psoft/hrms89/appserv Start the psadmin tool. For this, run the environment file & on
command prompt type pasadmin. Choose the menu options to start apps and batch server for
the node. Login into Windows as psoftadmin domain user Start the psoft service. Login as psoft user on apps server & start COBOL. Sudo /opt/microfocus/mflmf/mflmadm. Login to the Webserver as psoft & start it. For this, follow the
following steps:o Sudo . /apps/psoft/hrms89/psconfig.sho Sudo
/apps/psoft/hrms89/webserv/peoplesoft/startWebLogic.sho Sudo
/apps/psoft/hrms89/webserv/peoplesoft/startManagedWebLogic.sh PIA
o Sudo /apps/psoft/hrms89/webserv/peoplesoft/psolAdmin.sh START (start the PeopleBooks)
The Startup/Shut Down of other Instances is as follows: Shutdown:
Login as psoft on the Apps/WebServer. Go to /apps/psoft/hrms89/appserv. Start the psadmin tool. For this, run the environment file & on
command prompt type pasadmin. Choose the menu options to stop apps and batch server for
the node. Login into Windows as psoftadmin domain user. Stop the psoft service. Login to the Webserver as psoft & shut it down. For this,
follow the following steps:o Sudo . /apps/psoft/hrms89/psconfig.sho Go to /apps/psoft/hrms89/PSEMAgent & run
nohup ./StopAgent.sho Go to /apps/psoft/hrms89/webserv/peoplesoft & run
/psolAdmin.sh STOP & /stopWebLogic.sh Login as oracle on database server. Shutdown the database and listener.
Startup: Login as oracle on database server. Start the database and listener. Login as psoft on the Apps/WebServer. Go to /apps/psoft/hrms89/appserv Start the psadmin tool. For this, run the environment file & on
command prompt type pasadmin. Choose the menu options to start apps and batch server for
the node. Login into Windows as psoftadmin domain user Start the psoft service..
15
Oracle Applications Knowledge Oracle Applications DBA Support knowledge Transition Document
Login to the Webserver as psoft & start it. For this, follow the following steps:o Sudo . /apps/psoft/hrms89/psconfig.sho Sudo
/apps/psoft/hrms89/webserv/peoplesoft/startWebLogic.sho Sudo
/apps/psoft/hrms89/webserv/peoplesoft/startManagedWebLogic.sh PIA
o Sudo /apps/psoft/hrms89/webserv/peoplesoft/psolAdmin.sh START (start the PeopleBooks)
o Sudo /apps/psoft/hrms89/webserv/peoplesoft/startManagedWebLogic.sh PSEMHUB
o Navigate to apps/psoft/hrms89/PSEMAgent & run nohup /StartAgent.sh
4.0.9 Useful Scripts & processes details
ps –ef|grep mfl Information about the COBOL Licensing manager.
StartManagedWebLogic.sh Script to start the Managed Web Logic Service. Located in /app/psoft/hrms89/webserv/peoplesoft
StartWebLogicAdmin.sh Script to start the Web Logic Admin service. Located in /app/psoft/hrms89/webserv/peoplesoft
StartWebLogicBuilder.sh Script to start the Web Logic Builder Service. Located in /app/psoft/hrms89/webserv/peoplesoft
StopWebLogic.sh Script to stop the Web Logic Service. Located in /app/psoft/hrms89/webserv/peoplesoft
16
Oracle Applications Knowledge Oracle Applications DBA Support knowledge Transition Document
5.0 Service Request Handling
5.1 Types of service requests
All service requests which includes the entire gamut of minor, major or super-
major maintenance or enhancement requests will be routed through the …
(Tracking System)
5.2 Contact Numbers for Support
The contact numbers of the Cognizant team are provided in the form of a table.
Associate Name Work Number Cell Number Residence Number
The USER IDs of the Cognizant support team shall be provided here in a
tabular form. If the Cognizant team accesses Customer database on Lotus
Notes, then the Lotus Notes Ids used shall also be mentioned here.
6.0 Source Code Management
6.1 Code Migration methods / tools
Application designer.
17