Infrastructure. Oren Barshishat IT Support Manager. Adi Finkels Customer Support Manager. Sparta Systems

Transcription

1 Leverage and Scale Your TrackWise Infrastructure Oren Barshishat IT Support Manager Sparta Systems Adi Finkels Customer Support Manager Sparta Systems

2 Agenda Introduction How to Deploy The TrackWise System Scalability, High Availability, Redundancy, Performance Disaster Recovery Plan for TrackWise NewTrackWise ITOfferings Questions

3 Introduction

4 Introduction No doubt that business pressures to maintain optimal operations in IT is high. Deploying and maintaining TrackWise in today s fast changing environments require a regimented plan to ensure continued smooth operations. Planning for five 9 s of uptime Planning for a growing user base Planning for global quality deployments Planning for worst case scenarios And planning with tight budgets System Consolidation Planningfor globalqualitydeployments IT Cost Cutting Mergers & Acquisitions 7x24 Operations Globalization

5 Deployment

6 Deploying the TrackWise System Basic Setup The most simple production setup: One web/application server & one database server. Web/Application/Crystal Server Database Server

7 Deploying the TrackWise System Basic Setup Typical Setup The Load Balancer will be in front of the Web/Application servers. One common URL/Link will be used for all. Load Balancer Multiple Web/Application/ Crystal Servers Database Server

8 Scalability

9 Scalability The need for scalability can come from various situations Deploying TrackWise to additional sites Consolidating TrackWise instances as a result of a merger or acquisition Utilizing your TrackWise instance for a higher data volume solution Change in user behavior Scalability lbl should ldbe examined on two fronts. Growing user base Growing data (PR) volume

10 Scalability Growing user base Deploy additional web/app servers Consider virtualization through VMWare Consider segregating components on standalone servers (Coordinator, PR Import jobs, Web Services, etc) Consider 64 bit now available with version 8.3 Load Balancer Multiple/Segregated Web/Application Servers Database server Crystal server

11 Scalability Growing data volume Involve your DBA!! Database clustering Database partitioning Consider web/app server segregation egat as with the ecase for growing the user volume (if needed) Load Balancer Multiple Web/Application/ Crystal Servers Database Cluster

12 High Availability & Redundancy

13 High Availability and Redundancy Mission Critical operations necessitate zero tolerance for down time. Worldwide operations ITStaffing constraints Eliminating single points of failure High availability lbl and redundancy d for your TrackWise environment Network Application Server Database Server

14 High Availability and Redundancy Network Load Balancer Clustering Diverse network connections providing fully redundant paths Load Balancer 1 Load Balancer 2 Application Server

15 High Availability and Redundancy Application Server Solutions supporting Failover Clustering Load Balancing technique to detect and disable troubled servers Active Server Failover Clustering Failover Switch X Passive Server Shared Storage

16 High Availability and Redundancy Database Server Oracle Real Application Clusters SQL Server Clustering Active Server Switch X Active Server Active Server

17 Performance

18 Performance Achieving an optimal operational environment requires optimal performance for end users on TrackWise. Minimize i i the time to complete key transactions Avoiding white screens Slow reports Quickly identifying if i issues bf before the users do Addressing performance is done from different angles Understanding the common causes of poor performance Application usage Environment considerations

19 Performance Understanding the common causes of poor performance Memory/CPU exhaustion at the database level Memory exhaustion at the web/application server level Poor wide area network speeds Sizing is critical Database statistics should be reviewed by a DBA on a regular basis to ensure environment and configuration is optimal Web/Application server Java Heap should be monitored and logged to look for trends

20 Performance Application Usage: Understanding operations that can be a performance drain on TrackWise Primaryoperations to understand Area LargePR exports Large Batch Edit Things to Consider Minimize number of columns Avoid FlexFields in the export Consider working in smaller batches If possible, perform Batch Edits during non peak hours Large non table driven Consider converting to table driven selection lists Not setting a reasonable limit Allowing too many results can lead to large results sets to desktop results consuming large parts of application server memory.

21 Performance Environment Considerations: Web/Application Servers TrackWise Web is the primary application used by end users Consider segregating TrackWise components to their own servers Ensure sufficient CPU and memory exists on each server (heap settings too) Consider full CPU Crystal licenses. Perhaps multiple l Report Servers. Load Balancer Multiple Web/Application/ Crystal Servers Database Server Crystal Server

22 Performance Environment Considerations: Database Servers Examine/monitor statistical information Database clustering Ensure memory settings (i.e. SGA in Oracle) are sized properly Over engineering CPU and memory on database servers is acceptable Load Balancer Multiple Web/Application/ Crystal Servers Database Server

23 Performance Knowing where your users are! Two useful enhancements recently released and available in TrackWise 7 SR9.6 and 8.2 User login/logout logging configurable via a web XML flag New About box so users can tell IT staff which Application server they are homed to.

24 Disaster Recovery Planfor TrackWise

25 Disaster Recovery Plan for TrackWise Disaster Recovery High availability and redundancy techniques handle most faults Datacenter disasters require a disaster recovery plan Prime areasto address for Disaster Recovery Secondary datacenter site Software sync procedures Most critical: Data sync procedures

26 Disaster Recovery Plan for TrackWise Secondary Datacenter site Industry best practices exist for selecting an optimal secondary site Hardware and network shall be mimicked as in the primary site Plan needs to be developed to switch sites Software Sync Procedures TrackWise software needs to be fully installed, configured and ready for production use at secondary site Any TrackWise software release patches applied to primary site need to be followed by upgrade to secondary site

27 Disaster Recovery Plan for TrackWise CRITICAL: Data Sync Primary and secondary site databases must be kept in sync Tolerance for acceptable recovery time needs to be considered Cost effective technique: applying backups on a regular basis Time sensitivity technique: a data sync tool such as Oracle Data Guard Primary Site Secondary Site

28 New TrackWise IT Offerings

29 IT Assessment IT Assessment. Why? Clients using TrackWise for at least 2 3 years typically results in certain patterns of complacency. Some are good and some are not optimal. Aging hardware Performance issues Planned growth and new future needs

30 IT Assessment IT Assessment. How? Process of 4 6 professional days Sparta evaluates all servers in the existing TrackWise infrastructure Understand current bottle necks and performance issues Identify patterns of use Understand future planned growth and needs

31 IT Assessment IT Assessment. Outcome. Information analysis Sparta in house expertise engaged based on analysis to help drive improvements Final analysis formally documented Immediate ROI

32 64 BitSupport TrackWise 8.3 will support Windows Server bit 64 bit Web/Application server will enable the use of more memory and more heap Leverage infrastructure to handle additional concurrent users Performance boost of operating in a 64 bit Performance boost of operating in a 64 bit environment

33 Questions Thank You