© Copyright 6/4/2013 BMC Software, Inc 2
Purpose of webinar
What this webinar is about:
Identify recommended practices for common questions/problems
Technical presentation with detailed information and suggestions
What this webinar is NOT about:
NOT a TM ART introduction or sales/marketing with a pre-requisite of prior education and/or hands on experience with TM ART
No futures/roadmaps for TM ART will be discussed
Note: These recommendations are guidelines, not hard and fast rules. Different environments and business conditions may require alternate approaches.
Please search our online knowledge base for more details or answers to other TM ART questions at
http://www.bmc.com/support.html then click 'Knowledge Base‘ & enter search criteria
© Copyright 6/4/2013 BMC Software, Inc 3
Agenda
High Availability Setup Options
Sizing and Deployment Considerations
TM ART’s Database Considerations
© Copyright 6/4/2013 BMC Software, Inc 4
Monitor specific transactions that reflect the overall health of an application
Measure performance, availability and accuracy in virtual and physical environments
Monitor from different geographic locations to reflect site-specific performance variances
Measure actual (real) transactions to understand loads reflective of actual usage
Measure each “step” of a transaction for rapid problem isolation
End User Experience:Real and Synthetic Transaction Management Capabilities
Mainframe
Web
ERP/CRM
© Copyright 6/4/2013 BMC Software, Inc 5
The BMC TM ART Synthetic Landscape
Central Administration
Scripting Workbench Execution Servers
Customer Applications
Integrations
© Copyright 6/4/2013 BMC Software, Inc 7
TM ART High Availability
TM ART HA environments must address redundancy and failover for all 3 tiers
© Copyright 6/4/2013 BMC Software, Inc 8
TM ART High Level Component Architecture
User Interface Management:• Front-end server(s)
• Chart servers(s)
Transaction Execution:
• Execution servers replay monitors
• Run asynchronous with central
• Alert server (special ES) provides
impact manager integration
ART Central –
Monitor Management:• Deploy, schedule, collect monitors
• Save, verify, aggregate metrics
• Integrate to BSM interfaces: BPPM,
SLM, CMDB, BEM, dashboards…
© Copyright 6/4/2013 BMC Software, Inc 9
Execution
Server #3
BMC TM ART Synthetic Locations:Automatic Load Balancing
Scripting
Tools
Central
Administration
Houston
NYC
Zimbabwe
Monitor Schedule
Execution
Server #1
Execution
Server #2
LOCATIONS
Zimbabwe
Each Synthetic Location
auto-load balances
transaction executions
across one or more
Execution Servers.
© Copyright 6/4/2013 BMC Software, Inc 10
Transaction Execution High Availability
Location, Location, Location ….
� Location is NOT the same as an execution server� TM ART auto-load balances monitors across all Execution Servers within a location� Location is a conceptual grouping
Examples:• Broad Geography: location “West Coast” could be ES in
LA, Seattle, Chile and Hawaii• Functional Grouping: Financial Data Centers
© Copyright 6/4/2013 BMC Software, Inc 11
Application Tier High Availability:Location Recommendations
ES Failure Redundancy: Have at least one more ES per location than is necessary to process all monitors under same schedule.
- Example: Need 2 ES to execute monitors at location A. Add (at least) a 3rd ES to handle a failure (or maintenance activities) for one of the ES.
- Must perform cost/risk analysis of how many redundant ES should exist per location to handle different number of ES failures.
Network Placement: Place ES for same location on different network subnets.
- If one network infrastructure fails, the remaining ES(s) can continue to monitor the application.
Disaster Recovery Sites: (e.g., Data center in Miami with Phoenix DR site)
- Given significant distance/network differences, doesn’t typically make sense to failover an ES or try to compare before/after measurements.
- Instead maintain two locations at Miami and Phoenix testing same applications.� Even if lose Miami, Phoenix ES monitors will tell if performance has degraded
after application DR failover.
© Copyright 6/4/2013 BMC Software, Inc 12
Execution Server Recommendation:Persistence Option Guarantees Metric Delivery
Central
Administration
Houston
NYC
Zimbabwe
Local Metric Data and TrueLog
files cached until they can
transmit to TM ART Central
Recommendation: Enable ES Persistence
• Edit /conf/execserver/SccExecServerBootConf.xml
• Add ResultBuffer XML tag in the SccPath section
• Example: <SccPath>
...
<ResultBuffer>c:\tmart_persist\resultBuffer</ResultBuffer>
...
<SccPath>
© Copyright 6/4/2013 BMC Software, Inc 13
TM ART Database HA
Both Oracle and Microsoft SQL Server have numerous HA and Disaster Recovery configurations available. Customers may choose from most of these options based on their cost/risk tolerance for the monitor data availability.
Examples:
- Standard Backup / Recovery: � Should DB fail on host A, recover a copy to host B.� Comments: Time to restore DB availability is high. Always need this option
anyway to recover from data corruption to a prior point in time. Needs network or TMART redirect.
- Hot Standby: (MSSS Log Shipping or Oracle DataGuard)� Host B continuously applies A’s transaction log files to a clone copy. On failover,
only need to apply the last bit of log and restore.� Comments: Similar to Standard B/R but much faster recovery time and more
complex to maintain.
- DB Clustering: (MSSS on a MS Cluster, Oracle RAC)� Cluster solutions provide process failover.� Oracle RAC requires configuring different RAC nodes in TMART UI.� Comments: More automated, TM ART independent, failure handling of nodes.
© Copyright 6/4/2013 BMC Software, Inc 14
TM ART Database HA
TM ART has special configuration options to leverage Oracle RAC.- Identify one or more RAC nodes available for accessing TM ART data.- TM ART will try secondary nodes if the connection fails to others.
© Copyright 6/4/2013 BMC Software, Inc 15
TM ART User Interface HA
Chart Servers HA:
- The chart server is used to generate charts that are viewed in reports. - TM ART auto-load balances across a pool of chart servers.- HA Recommendation: Configure at least 1 additional chart server for failure
and maintenance downtime tolerance than required to support the charting load.
Front-End Server HA:
- The front-end server is web browser HTML-based and responsible for the graphical user interface that must be hosted on a web server (IIS or Tomcat).
- Multiple front-end servers can be connected to one TM ART Central Application Server.
- Customers can bring up the UI by contacting a specific FE Server or have a load balancer in front of the FE Servers.
- HA Recommendation: Configure at least 2 FE Servers with load balancing. May also want to locate the FE Servers on a different network infrastructure to continue access to TM ART during partial network outages.
© Copyright 6/4/2013 BMC Software, Inc 16
TM ART Central HA
TM ART Central High Availability Options:
- Persistent cache for queued metric data- Failover/disaster recovery server – separate host or VM- Microsoft clusters for app server – active/passive- Application server survivability via VMotion- Multi-host standby (not in MS Cluster) – manual procedure to copy/get second
system up and running on failover, what files/data to copy, etc.
© Copyright 6/4/2013 BMC Software, Inc 17
Application Server Recommendation:Persistence Result Data Option
Recommendation: Enable Central Data Persistence in files
instead of memory buffer:
• Edit /conf/appserver/SccAppServerBootConf.xml
• Add ResultBuffer XML tag in the SccPath section
(relative or absolute path)
• Relative Path Example: <SccPath>
...
<ResultBuffer>resultBufferFile</ResultBuffer>
...
<SccPath>
• The above creates a resultBufferFile in the “Application
Data” directory, typically at C:\Documents and Settings\All Users\Application Data\BMC\PM3x
Monitor Result Data Transport ArchitectureMeasure Data created by executing a monitor is held in memory
buffers both on the Execution Server and Central Application
Server temporarily as a staging area until transferred.
Causes of lost result data when using Buffer in Central:
(1) Buffer overflows when results can’t be stored in DBMS
(2) Server shutdown/restart
Result
Buffer File
Result
Buffer File
© Copyright 6/4/2013 BMC Software, Inc 18
TM ART Central High Availability
TM ART can be set up on MS Clusters or manually on independent hosts(see BMCDN Document for more details).
Alternatively, can also use Virtual Machine technology to house servers and motion to other hosts.
Note: due to intensive, sustained I/O for large TM ART environments, we have occasionally seen problems with managing the DBMS on VMs.
Virtual (Cluster) Name
Node Host Name
MS Cluster Example:
© Copyright 6/4/2013 BMC Software, Inc 19
Application Server MS Clusters Configuration
TM ART App Server can be setup ONLY in active/passive on a MS.- Why Active/Passive and not Active/Active?
� Because only one TM ART Application Server can be active at a time when connected to the database repository
- Install TM ART on both nodes (either shared or local drives; shared is suggested)- Configure cluster service for any application as:
� Resource Type � generic service � Possible Owners � all nodes where resource can be brought online� Dependencies � add cluster name, cluster IP address, and shared drives� Generic Service Parameters � find service name & path to executable in registry
– HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
© Copyright 6/4/2013 BMC Software, Inc 20
Chart & Front-End Server: MS Clusters Configuration
Use same basic steps as for the Application Server
Important: Configure Central with Chart Server virtual (cluster), not node name
Example MS Cluster configuration:
© Copyright 6/4/2013 BMC Software, Inc 21
Configuring TM ART for HA Manually
If possible, install TM ART onto a shared drive for configuration files.
Vast majority of configuration information is stored in the database, including monitors, scripts, etc.
Remaining configuration information is found in configuration directory.- …\BMC TM ART Central <version>\conf\- On non-shared file installations, updates to configuration files must be synchronized
on both primary and fail-over target
Important: After failover, the host name of TM ART Central must be the same.- Adjust DNS name to map to failover IP address after the failover
© Copyright 6/4/2013 BMC Software, Inc 23
TM ART Sizing Considerations
Host, DBMS resource availability (CPU, shared memory…)
Number of locations
Number of execution servers per location
Number of transactions
Frequency of monitor execution
Types of transactions/protocols
Transaction complexity
© Copyright 6/4/2013 BMC Software, Inc 24
BMC TM ART Synthetic Supported Protocols
Web Browser
•HTTP(S)/HTML
•Macromedia Flex/AMF
•Streaming (MS, Real)
•Outlook Web Access
•Remedy ARS
Internet
•HTTP(S)
•SMTP/POP/IMAP
•MAPI
•FTP
•LDAP
•WAP
•TCP/IP & UDP
Middleware
•CORBA (IIOP)
•J2EE/EJB
•.NET Remoting (Framework)
•(D)COM (COM+, MTS)
•BEA Tuxedo (ATMI, JOLT)
•Oracle Forms
•SAP NetWeaver
Terminal Services
•Citrix MetaFrame (ICA)
Client/Server (Databases)
•ODBC
•ADO
•Oracle OCI
•IBM CLI
ERP/CRM
•SAP
•PeopleSoft
•Siebel
•Oracle Applications
•Chordiant
•Epiphany
•Lawson
Other Applications
•SilkTest GUI Support
Web Services (SOA)
•SOAP (HTTP/XML)
•MS .NET SOAP Stack
•Apache Java SOAP Stack
Legacy/Mainframe
•IBM Mainframe (TN3270e)
•Telnet-based terminal protocol
•5250
© Copyright 6/4/2013 BMC Software, Inc 25
TM ART Central Load Estimation – Key Questions
How heavy are my transactions?- Heavy protocol types – especially that launch a related client (e.g., SAP, Citrix)- Complex monitors (multiple pages, timers, counters) generate numerous measures*
� Even simplest monitors generate approximately 15 measures each execution� Typical average execution measure number is around 35 measures
Number of locations at which a transaction must be scheduled? - Medium size TM ART – 25 locations- Large size TM ART – 50+ locations
At what frequency must transactions be scheduled for execution?
Number of TrueLogs generated?- When transaction problems occur and generate TrueLogs, number the measures spike- Recommendation: Engineer enough capacity in system beyond “normal” to handle
increased workload of TrueLogs when application problems occur.
* Measure is a value generated by a single monitor execution.
Example: PageTime of monitor “myhomepage” at location “downtown” = 1 measure.Determine # of measures per transaction from Execution Log (1 measure per row).
© Copyright 6/4/2013 BMC Software, Inc 27
TM ART Sizing Example
Example:- Number of transactions = 50- Number of locations = 5- Average number of measures per transaction = 36
The following arrival rates are projected:- 36 Measures per Tran * 50 Trans = 1,800 measures per scheduled cycle
- 5 min Scheduled frequency = 12 schedule cycles per hour
- 1,800 measures per cycle * 12 cycles = 21,600 measure per hour� Note: This represents a large environment as related to existing ART installs.
- 5 locations * 21,600 = 108,000 measures per hour
- Required minimum DB project MeasureWriteTime = 33 milliseconds per measure
� 108,000/3600 sec/hr = 30 measures/sec (or 1 measure every 33 ms)– Note: 33 ms measure write time is at the slower end of observed times. – Good MeasureWriteTime is dependent on CPU, DBMS resources, network speed between
Central Server and DBMS and db tuning. – Multiple centrals will be required if sufficient db write times cannot be achieved.
© Copyright 6/4/2013 BMC Software, Inc 28
Monitor Recommendations
Minimize frequency of monitor scheduling, especially if Central or ES is busy
Monitor scheduling at same time at location can cause spikes in # measures- Recommendation: Stagger transaction schedules to reduce impact on ES and DBMS.
Specialty scheduling to reduce impact on application and TM ART overhead- Cascaded Delay: avoids scheduling transaction at same time at all locations
� Example: 5 second delay runs at location A at 5:00, B at 5:00:05, C at 5:00:10…- Concurrent Runs: set maximum # locations that run monitor per execution cycle
� Example: 3 CR for 5 locations – exec #1 {1, 2, 3}, exec #2 {4, 5, 1}, …
Transaction Complexity:- Creating complex monitors touching multiple pages - generates lots of measures- Recommendations:
� Reduce complexity of monitor transactions� Eliminate extra, unwanted timers from scripts
– Example: Replace multiple page timers with a single Customer Timer� Use URL checker for basic web testing to create minimal measure overhead
Disable unnecessary TrueLogs
Reduce the duration of data retention in Central (Recommendations: 30 days for raw and 15 minute aggregates)
© Copyright 6/4/2013 BMC Software, Inc 29
When to Use Multiple TM ART Centrals
TM ART Central retrieves, correlates, aggregates, and stores monitor measures
Rules of Thumb: - MeasureWriteTime(avg)
� > 30 ms �DBMS in need of tuning &/or resources � < 10 ms � indication of good DBMS performance and tuning
- MeasureCount Totals > 350,000 constitute a large BMC TM ART deployment
Recommendation: Total measures per hour > 500,000 require additional Central
© Copyright 6/4/2013 BMC Software, Inc 30
TM ART Execution Server Load Guidelines
ES sizing is based on several factors including ….
- Protocol or application being monitored- Monitoring frequency- Depth of each transaction (how many steps/pages are scripted)- Presence of Silktest monitors
© Copyright 6/4/2013 BMC Software, Inc 31
Guidelines: Deploying Monitors Per Execution Server?
Distribute monitor load across multiple Execution Servers in a location.- Recommendation: consider minimum of 2 ES per location for load balancing and HA
concerns
Use an upper limit of 200 monitors per ES for capacity planning (if all are simple web monitors).
With middleweight web monitors (5-10 pages that run < 1 minute), use 100 for ES capacity planning.- Note: assumes frequency of 15 minutes (10 at the least) and may require staggering
schedules across the 15 minute period to achieve the highest number. - For frequencies below 10 minutes, reduce the total planning number by 1/3 to 1/2.
For heavy apps like Citrix & SAP, estimate 20-40 monitors per ES.
For Silktest monitoring of thick apps, estimate 10 monitors per ES.- Note: assumes ample MS Terminal Server session resources are licensed and
available.
© Copyright 6/4/2013 BMC Software, Inc 32
Chart and Front-end Server Sizing
Optimally, the database and Chart, Front-end, Application Servers should be on 4 separate hosts.- For smaller TM ART environments co-resident servers can be used initially
Recommendation for initial deployment- Minimal configuration - 2 Chart Servers + 2 Front-end Servers- With a larger number of concurrent clients access TM ART, additional FE and Chart
Servers may be required- Customers may want to provide a load balancer in front of numerous Front-end
servers so that customers don’t have to know different connection alternatives.
NOTE: Frequent automatic refreshes of a large number of clients can burden the Front-end Servers. Consider increasing or eliminating (setting to 0) the automatic page refresh time on the User Administration dialog.
© Copyright 6/4/2013 BMC Software, Inc 34
Choosing the Type of Database (Oracle or MSSS)
Key considerations when choosing the DBMS Vendor- Which DBMS are the company DBAs most familiar with and willing to support- Database licensing costs- Share existing DB server with other applications
� Pros:– Avoids separate DB license fees– Piggy-back existing backup/recovery maintenance
� Cons:– BMC TM ART deployments are often very high OLTP – May conflict and impact other applications sharing the DBMS server– DB tuning, recovery, etc., may be hampered if impacts other applications– Version incompatibility (e.g. app 1 can’t run on same DB version required by TM ART)
- No databases are maintenance-free- Maintenance/tuning
� TM ART on Oracle typically requires much more overhead/tuning maintenance
Recommendation:� All other considerations being equal, running TM ART on Microsoft SQL Server is
recommended primarily because of the lower maintenance overhead.
© Copyright 6/4/2013 BMC Software, Inc 35
BMC TM ART Data Retention / History
By default, collected data is retained indefinitely and can grow large resulting in:- Slower user interface response time- Slower indexing and data deletion maintenance- Slower upgrade times – especially when new releases adjust the schema- Overall higher efforts to tune and maintain the DBMS
Recommendation: - Retain raw and 15-minute interval data for 30 days or min. time required by business- Integrate BMC TM ART with BMC ProactiveNet Performance Manager
� Let BPPM maintain the longer metric history, analytics, and dynamic baselines� Focus TM ART on testing and collecting information
Example:
Edit the <KeepOldData> tag in \conf\appserver\SVAppServerHomeConf.xml<RawValues>31</RawValues> Removes raw values for data older than 31 days.<115min>61</115min> Removes 15 minute interval values after 2 months.<160min>182</160min> Removes 1 hour interval values after 6 months.<11440min>365</11440min> Removes 1 day interval values after 1 year.<110080min>730</110080min> Removes 1 week interval values after 2 years
© Copyright 6/4/2013 BMC Software, Inc 36
Oracle Database Schema Maintenance: Index & Statistics
Optimal Oracle query execution require index and statistic updates- Following numerous data delete jobs, indices and tables can become fragmented.- Oracle Cost Based Optimizer (CBO) requires up-to-date statistics and may default to full
table scans if index/statistics are out-of-date, resulting in poor performance for large SV_TIMESERIESdata tables.
Rebuild Indexes for SV_TIMESERIESdata on a regular basis- Why? TM ART’s constant high rate of insert & delete operations fragment both indices
and tables.- Especially recommended after scheduled data delete jobs. - Consult your DBA for their recommended mechanism to regenerate indices- Example: Rebuilding indices
� begin EXECUTE IMMEDIATE 'alter index "SERVICE_TMART"."PK_SV_TIMESERIESDATA" shrink space'; EXECUTE IMMEDIATE 'alter index "SERVICE_TMART"."IDX_SVTIMESERIESDATATIME" shrink space';
end;
© Copyright 6/4/2013 BMC Software, Inc 37
Oracle Database Schema Maintenance: Example for Drop and Recreate of Indices
Drop indices - drop index PK_SV_TIMESERIESDATA- or drop the constraint- ALTER TABLE SV_TIMESERIESDATA DROP CONSTRAINT PK_SV_TIMESERIESDATA;
Create indices- CREATE INDEX TMART.IDX_SVTIMESERIESDATATIME ON TMART.SV_TIMESERIESDATA (TIME_PK)
LOGGINGTABLESPACE TMARTPCTFREE 10INITRANS 2MAXTRANS 255STORAGE (
INITIAL 104KNEXT 104KMINEXTENTS 1MAXEXTENTS UNLIMITEDPCTINCREASE 0BUFFER_POOL DEFAULT
)NOPARALLEL;
- CREATE UNIQUE INDEX TMART.PK_SV_TIMESERIESDATA ON TMART.SV_TIMESERIESDATA (TIMESERIESID_PK_FK, TIME_PK)LOGGINGTABLESPACE TMARTPCTFREE 10INITRANS 2MAXTRANS 255STORAGE (
INITIAL 104KNEXT 104KMINEXTENTS 1MAXEXTENTS UNLIMITEDPCTINCREASE 0BUFFER_POOL DEFAULT
)NOPARALLEL;
Recreate the constraints- ALTER TABLE TMART.SV_TIMESERIESDATA ADD ( CONSTRAINT PK_SV_TIMESERIESDATA PRIMARY KEY (TIMESERIESID_PK_FK, TIME_PK)
USING INDEX TABLESPACE TMARTPCTFREE 10INITRANS 2MAXTRANS 255STORAGE (
INITIAL 104KNEXT 104KMINEXTENTS 1MAXEXTENTS UNLIMITEDPCTINCREASE 0
));- ALTER TABLE TMART.SV_TIMESERIESDATA ADD ( CONSTRAINT FK_SV_TSD_SV_TIMESERIES FOREIGN KEY (TIMESERIESID_PK_FK)
REFERENCES TMART.SV_TIMESERIES (TIMESERIESID_PK) ON DELETE CASCADE);
© Copyright 6/4/2013 BMC Software, Inc 38
Oracle Database Schema Maintenance: Index & Statistics
Oracle Cost Based Optimizer (CBO) requires up-to-date statistics - Out-of-date statistics may default to full table scans and very poor performance for large
SV_TIMESERIESdata tables.
Update statistics frequently- Example query to verify stats job scheduling:
Select state from dba_scheduler_jobs where job_name = 'GATHER_STATS_JOB';(state should return ‘SCHEDULED’ )
- Consult your DBA for recommended statistics update commands
- Example: dbms_stats utility
� Typically better at estimating statistics, resulting in faster SQL execution plans� Often better than the old-fashioned analyze table and dbms utility options� A sample execution of dbms_stats with the OPTIONS clause:
exec dbms_stats.gather_schema_stats( - ownname => ‘tmart_owner', - options => 'GATHER AUTO', - estimate_percent => dbms_stats.auto_sample_size, - method_opt => 'for all columns size repeat', - degree => 34 - )
© Copyright 6/4/2013 BMC Software, Inc 39
BMC TM ART – CENTRAL / WORKBENCH / DATABASE
Supported Platforms, Requisites and Architecture
© Copyright 6/4/2013 BMC Software, Inc 40
CENTRAL & EXECUTION SERVERPlatfoms Supported
• Microsoft Windows XP 32bit with Service Pack 3
• Microsoft Windows XP 64bit with Service Pack 2
• Microsoft Windows Server 2003 32bit with Service Pack 2
• Microsoft Windows Server 2003 64bit with Service Pack 2
• Microsoft Windows Server 2003 R2 32bit with Service Pack 2
• Microsoft Windows Server 2003 R2 64bit with Service Pack 2
• Microsoft Windows Vista 32bit
• Microsoft Windows Vista 64bit
• Microsoft Windows Server 2008 32bit
• Microsoft Windows Server 2008 64bit
• Microsoft Windows Server 2008 R2
• Microsoft Windows 7 32bit
• Microsoft Windows 7 64bit
Operating Systems:
Cluster Support:• Microsoft Windows Server 2003 32bit with Service Pack 2
• Microsoft Windows Server 2003 64bit with Service Pack 2
• Microsoft Windows Server 2003 R2 64bit with Service Pack 2
• Microsoft Windows Server 2008 32bit
• Microsoft Windows Server 2008 64bit
• Microsoft Windows Server 2008 R2
© Copyright 6/4/2013 BMC Software, Inc 41
DATABASE & WEB BROWSER Platfoms Supported
Database Support:
Web Browser Support:
• Microsoft SQL Server 2005, 2008, 2008 R2
• Oracle Database 10g Release 1 and 2, including Oracle RAC
• Oracle Database 11g Release 1 and 2, including Oracle RAC
• Windows Internet Explorer 6.0, 7.0, 8.0, 9.0
• Opera 8.5.1, 9.2
• Mozilla Firefox 3.0 or later
• Google Chrome
© Copyright 6/4/2013 BMC Software, Inc 42
MONITOR WORKBENCHOS and Browsers Supported
Operating Systems :• Microsoft Windows XP 32bit with Service Pack 3
• Microsoft Windows XP 64bit with Service Pack 2
• Microsoft Windows Server 2003 32bit with Service Pack 2
• Microsoft Windows Server 2003 64bit with Service Pack 2
• Microsoft Windows Server 2003 R2 32bit with Service Pack 2
• Microsoft Windows Server 2003 R2 64bit with Service Pack 2
• Microsoft Windows Vista 32bit
• Microsoft Windows Vista 64bit
• Microsoft Windows Server 2008 32bit
• Microsoft Windows Server 2008 64bit
• Microsoft Windows Server 2008 R2
• Microsoft Windows 7 32bit
• Microsoft Windows 7 64bit
Web Browser Support:
• Windows Internet Explorer 6.0, 7.0, 8.0
• Mozilla Firefox 3.0 or later
• Google Chrome
© Copyright 6/4/2013 BMC Software, Inc 43
MONITOR WORKBENCHTransactions – Protocols and Clients Supported
Terminal Emulation Support:
• AttachMate Extra 8
• AttachMateWRQ 13.0
• Distinct IntelliTerm 8.1
• Ericom Powerterm Pro v8.8.1
• HummingBird_Exceed 11.0 (hooking via socks proxy)
• JProtector 4.5.2.0
• MochaSoft 5.3 (hooking via socks proxy)
• NetTerm 5.1.1
• Nexus Terminal 5.3
• PassportPC2Host 3
• Quick3270 3.73
• Rumba 7.4
• Rumba 8
• SDI TN3270 Plus v2.4
• SecureCRT 1.0
• TeraTermPro 2.3
• TN5250_sourceforge 0.17.3
• TNBridge
ERP/CRM Support:
SAPGUI Clients:
• SAPGUI client 620, Patches 44, 50, 66
(recommended), and 20
• SAPGUI client 710
• SAPGUI client 720
PeopleSoft Systems:
PeopleSoft 8.0, 8.3, 8.4, and 8.8
Siebel Systems:
• Siebel 6.3 using MS SQL Server
• Siebel 6.3 using IBM DB2
• Siebel 6.3 using Oracle
• Siebel 7
• Siebel 8.0, 8.1
Clarify Systems:
Clarify eFrontOffice 8, 10
Remedy Web ARS:
Remedy Web ARS 6.3, 7.0, 7.0.1, 7.1, 7.5, 7.6, 7.6.04
© Copyright 6/4/2013 BMC Software, Inc 44
MONITOR WORKBENCHTransactions – Protocols and Clients Supported
Citrix Support:Citrix Clients:
• Citrix XenApp Client 11, 11.2, 12.0
• Citrix Web Interface 5.1, 5.2, 5.3
Citrix Servers:
• Citrix Presentation Server 4.0, 4.5
• Citrix XenApp 5.0, 6.0
Operating Systems:
• Microsoft Windows XP
• Microsoft Windows Server 2003
• Microsoft Windows Server 2008
Oracle Froms Support:
• Oracle Forms 6i, 9i, 10g
• Oracle Applications 11i, 12i
SOAP Support:
• Microsoft SOAP Toolkit 2.0 Service Pack 2 (SP2),
Internet Information Server 5
• Apache-SOAP Version 2.1, TOMCAT Version 3.1
Web Service Support:
• IBM Universal Database Systems 5.2, 6.1, 7.1
• Microsoft SQL Server 7.0, 2000, 2005, 2008, 2008 R2
• Oracle7 Server Release 7.3.2.2.1
• Oracle8 Enterprise Edition Release 8.0.3.0.0, 8.0.5.0.0
• Oracle8i Release 8.1.5, 8.1.6, 8.1.67
• Oracle Database 10g Release 2
• Oracle Database 11g Release 2
• Sybase SQL Anywhere Network Server 5.5.04
Database Support:
• Axis 1.x
• Axis2 1.4, 1.5
• GlassFish Metro 1.5
© Copyright 6/4/2013 BMC Software, Inc 45
MONITOR WORKBENCHTransactions – Protocols and Clients Supported
CORBA Support:
TUXEDO Support:
JOLT Support:
.NET Support:
Rich Internet Applications Support:
• BEA WebLogic Enterprise 5.0.1, 6.0, 6.1
• VisiBroker Java/C++ 3.x, 4.x, 5.x, 6.x
• Inprise Application Server 4.0
• Iona Orbix
• IBM WebSphere 3.5, 4.x, 5.0
• Iona iPortal Application Server 1.1
• BEA TUXEDO Server 6.3, 6.4, 7.0, 7.1, 8.0, 9.0
• BEA WebLogic Enterprise 4.2
BEA Jolt 1.1 (including BEA TUXEDO Server 6.4), 1.2
JAVA Support:• Java Runtime Environment 1.2.2: classic and hotspot 1.0
• Java Development Kit 1.4, 1.5, 1.6, 1.7
• IBM Java Development Kit 1.3
• Eclipse 3.2, 3.3, 3.4, 3.5, 3.6
• Microsoft .NET Framework 1.0, 1.1, 2.0, 3.5
• Microsoft .NET Framework runtime 2.0
• Microsoft Visual Studio 2008 and 2010
• Adobe Flex 2, 3, 4
• Google Web Toolkit
• ExtJS 3
• Eclipse RAP
• script.aculo.us
© Copyright 6/4/2013 BMC Software, Inc 46
REQUIEREMENTS
PROCESSOR MEMORY DISK OTHER
CENTRAL+
Execution Server
INTEL Core i5 (3.80
GHz) or equivalent CPU8 GB (Mín.) 30 GB
Java Runtime Environment (JRE)
Network Adapter: 100 Mbit
Network Connection: ISDN of faster
Execution ServerINTEL Core i5 (3.80
GHz) or equivalent CPU4 GB (Min.) 20 GB
Network Adapter: 100 Mbit
Network Connection: ISDN of faster
Database Server - - 100 GB
* TM-ART Central and Execution Servers can be installed on Virtual Machines