aol dd - tcs understanding - v3

7/31/2019 AOL DD - TCS Understanding - V3

http://slidepdf.com/reader/full/aol-dd-tcs-understanding-v3 1/22



© Tata Consultancy Services ltd. 1 June 2012 2

RELEASES

Software OS CI / DI OS – DB Instance RDBMS

ECC 6.0

(IS-Media 6.0)

Windows 2003 HP-UX 11 Oracle 10.2.0.2

SRM 5.0 Windows 2003 HP-UX 11 Oracle 10.2.0.2

BI 7.0 + SEM6.0

Windows 2003 HP-UX 11 Oracle 10.2.0.2

EP 7.0 Windows 2003 Windows 2003 SQL 2000

SOLMAN 4.0 Windows 2003 Windows 2003 SQL 2000

• ALL Database instances are clustered by HP Service Guard• SAP Application instances are load balanced vi SAP Load-balancer• ALL DB production storage is under SAN• EP 7.0 load balancing is done via Web Dispatcher• EP authentication is done via AOL LDAP server

• SSO is implemented to all SAP systems




ARCHITECTURE – Production Support

DEV

RDBMS

RDBMS

QAS RDBMS

RDBMS

SAP Users

APAC

Users

APAC

Users

Europe

Users

Europe

UsersNA UsersNA Users

ECC 6.0 (IS-MEDIA 6.0)EP 7.0

BI 7.0 /SEM 6.0 (Only ABAP)SRM 5.0

SOLMAN 4.0

RDBMS

RDBMS

5 Production systems

PRD

RDBMS:Oracle 10.2.0.2MySQL 2000

INTERFACES:

• Impress Engine• BEA WebLogic• Native SAP (ALE, BAPI, IDoc, etc.)• TopCall (faxination software)• File transfers

SANDBOX

RDBMS

RDBMS




ARCHITECTURE – Production Systems

PRD RDBMS

RDBMS ECC 6.0( IS-MEDIA 6.0 )

PRD RDBMS

RDBMS

PRD RDBMS

RDBMS

PRD RDBMS

RDBMS HPServiceGuard

DB-Primary

DB-Secondary

Database SAN StorageHI Performance Bulk Storage

PRD RDBMS

RDBMS

PRD RDBMS

RDBMS




ARCHITECTURE – Project Support

DEV

RDBMS

RDBMS

QAS

RDBMS

RDBMS

ECC 6.0

( IS-MEDIA 6.0 )

DEV RDBMS

RDBMS

QAS RDBMS

RDBMS

DEV RDBMS

RDBMS

QAS RDBMS

RDBMS

SRM 5.0

BI 7.0 / SEM 6.0(ABAP+JAVA)




ARCHITECTURE – Consolidated

BI 7.0 / SEM6.0

( ABAP + JAVA)

DEV RDBMS

RDBMS QAS

RDBMS

RDBMS DEV

RDBMS

RDBMS QAS

RDBMS

RDBMS PRD

RDBMS

RDBMS

COPY/MIGRATECOPY/MIGRATE

COPY/MIGRATE

Install BI JAVA (Add-in)

DEV RDBMS

RDBMS QAS

RDBMS

RDBMS ECC 6.0

( IS-MEDIA 6.0)DEV RDBMS

RDBMS QAS

RDBMS

RDBMS PRD

RDBMS

RDBMS

COPY/MIGRATE

COPY/MIGRATEApply SAP_ABA 06Apply SAP_BASIS 11

Install IS-MEDIA 6.0 (Add-on)

COPY/MIGRATE

SRM 5.0DEV

RDBMS

RDBMS QAS

RDBMS

RDBMS DEV

RDBMS

RDBMS QAS

RDBMS

RDBMS PRD

RDBMS

RDBMS

COPY/MIGRATECOPY/MIGRATE

COPY/MIGRATE


http://slidepdf.com/reader/full/aol-dd-tcs-understanding-v3 7/22 © Tata Consultancy Services ltd. 1 June 2012 7

Today’s Support

• Execution of Basis tasks in DEV& QAS systems are done by AOL

Basis team

• Execution of Basis tasks in Production systems are done by IBMBasis team

• IBM is using proprietary tools for monitoring SAP systems

• Security is taken care by different team

• DBA tasks for SAP systems are done by DBA group



Current AOL Basis Services

A

B

– User Management – Transport Management

– Batch Scheduling – Backup/Restore – Support / Kernel Patches – Client Administration – System Monitoring – Interface Management

– Output Management – Incident Management – Capacity Management – Storage Management – Projects – Performance Management

– OSS Administration – Database Management – HA/DR Testing – Security – Documentation



A

B

Basis Services – In detail

User Mgmt:• All end users login via Portal

• Majorly SAP Support team & few business users login via GUI• Few BW users use BeX• Vol. of changes : 14 changes / week / system & majority are R/3 & SEM

Transport Management:• Requests from DEVQAS are executed regularly

• Requests to prod are MANUAL on every Thursdays• Vol. of DEV QAS requests : 14 changes/week/system• Vol. of QAS PRD requests : >14 changes/week/system

Batch Scheduling:• All Prod/QA Jobs are scheduled manually

• Vol. of new jobs: 2 / month

Backup/Restore:• IBM Basis team schedules the Backup via RMAN tool• RMAN restore is used for QA & Sandbox system refresh• QA refresh 3 / yr / system



A

B

Support / Kernel Patches:• Current AOL System patch level is 2 levels below the SAP released patch

levels• Kernel patches applied twice in a year• SP patches driven by AOL business owners

Client Administration:• Client copies are not regular

Application Monitoring:• IBM Team monitors via proprietary tools• Monitor Portal – ESS/MSS• Monitor SSO• Monitor Ongoing projects in Portal – Minor issues like JCo locked, SSO

authentication• Very less “High Severity” tickets

Archiving:NO Archiving as data in the system is 2 yrs old and DB size is NOT big




A

B

Interface Monitoring:• Monitor RFC connection

• Monitor IDOCs

Output Management:• Printer : Berkley for Windows printers, Local for UNIX printers• Mail : SMTP• Fax : TopCall software

Incident Management:• End user report problems via Remedy• Project Team report problems via Remedy• L1 tickets are mostly solved by Helpdesk

Capacity Management:• Current hardware and storage is sufficient for current production support• Need to resize for incorporating OTC project in the single instance of SAP

production systems (ECC 6.0, BI 7.0 and SRM 5.0)




A

B

Projects:• OTC project in progress

• Installation of NEA 2005.1 (Dev/QA setup in progress)• Portal – Integrate systems• BI-Java Add-in installation, etc

OSS Administration:• OSS Connection : open/close

• OSS Administration : create user id, register developer/object keys,create systems• OSS notes : yes• SAProuter Support : software support

Security:

- Security controls are SoX based- 3rd party tool Virsa used- Not using AIS for auditing- Security controls & audits are done once a year




A

B

Performance Management:• Proactive Monitoring methodology/tools ????

• Dashboards : ????• Concerns : ????• Tasks :

– Troubleshoot Errors – Performance Tuning – Manage load-Balancing – Troubleshoot slow performance if reported any,

– Monitor and analyse workload – Monitor data transfer through RFC's between OLAP and OLTP's.

Database Administration:• ECC, BI/SEM, SRM – Oracle• EP, SolMan – SQL 2000

• Tools: Customized AOL scripts for Ping check, errors, proactive monitoring• Backup

– Daily Backup to disk via RMAN

• No DB Links• System stable No big issues which lead to outage (as of date)




A

B

HA/DR:

Servers are located in Manassas. Few of servers are in Dulles

Only DB server is under cluster (HP Service Guard)

Frequency of testing – Once a year

Storage Management:

• Production – EMC storage

• Most of the dev & QA systems are also on EMC due to criticality

• Using Clariion (low-end storage) for DB dumps & backup files

• No EMC tools used for SAP or DB administration

• EMC disks are configured as RAID-5

• No consistent backup/image copy across SAP landscape

P.S - Check for slides about HA, DR, Backup recommendations




Offshorability Matrix



A

B

AOL areas of concern

Quality of Resources




A

B

AOL Support Strength

• Current Team strength (BASIS)

– BASIS :

– Security :

• Issue Tickets / month for Basis team to attend : 50

• Request Tickets / month for Basis team to attend : 50

3




A

B

Preventive Maintenance

• Latest Support/kernel patches of SAP, database and OS

• Proactive Monitoring

• Performance Tuning

• Pre-production simulation tests Mercury Loadrunner is used during majorrollout or implementation




A

B

Points to Discuss

• IBM Monitoring tasks

• Transition Methodology

• Resource Model

• Usage of Solution Manager for CEN

• Possibility of using Redwood Scheduler for central job scheduling &monitoring

• Recommendation of Storage & HA/DR Architecture

• SLA definition: E.g. – System Availability, – Avg. response time – Initial Response Time, Processing Time, closure time, etc




TCS TOOLS

Tools TCS can deploy

• Alive:

– Proactive Monitoring & Alerting via dynamic thresholds

– Automated correlation of complex interdependencies

– Predictive Problem identification using Fingerprint technology

• SQL scripts for DB monitoring

aol dd - tcs understanding - v3

Documents