Installation Guide for Applicare v6.6.

Applicare Version 6.6.4 Document Revised: February 13, 2012

Copyright
Copyright 2004-2012 Arcturus Technologies, Inc. All Rights Reserved.

Restricted Rights Legend

This software is protected by copyright, and may be protected by patent laws. No copying or other use of this software is permitted unless you have entered into a license agreement with ARCTURUS authorizing such use. This document is protected by copyright and may not be copied photocopied, reproduced, translated, or reduced to any electronic medium or machine readable form, in whole or in part, without prior consent, in writing, from Arcturus Technologies, Inc. Information in this document is subject to change without notice and does not represent a commitment on the part of ARCTURUS Technologies, Inc. THE DOCUMENTATION IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. FURTHER, ARCTURUS TECHNOLOGIES DOES NOT WARRANT, GUARANTEE, OR MAKE ANY REPRESENTATIONS REGARDING THE USE, OR THE RESULTS OF THE USE, OF THE DOCUMENT IN TERMS OF CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE.

Trademarks
Copyright 2004-2012 Arcturus Technologies, Inc. All Rights Reserved. ARCTURUS Applicare, ARCTURUS Applicare WL, ARCTURUS Applicare WL2, ARCTURUS Applicare WL3, IntelliTune, IntelliSense, IntelliCheck, ARCTURUS Applicare Advisor, ARCTURUS Applicare Detector, ARCTURUS Applicare AutoTune Wizard, Knoms, ARCTURUS Applicare Blackbox and ARCTURUS Applicare JVM Optimizer are non-registered trademarks of Arcturus Technologies, Inc. All other names and marks are property of their respective owners.

1-2

| Arcturus Applicare Installation Guide

Table of Contents
1 Installation Guide ...................................................................................................................................................1-4 1.1 1.2 1.3 1.4 1.5 2 3 4 5 6 7 Installation Requirements: ............................................................................................................................. 1-4 Runtime Requirements .................................................................................................................................. 1-4 Installation Types........................................................................................................................................... 1-4 Installing Applicare ........................................................................................................................................ 1-5 Testing the Installation .................................................................................................................................. 1-6

Installing Applicare Agent on a WebLogic Server ....................................................................................................2-7 Installing Applicare Agent on a WebSphere Server ...............................................................................................3-11 Installing Applicare Agent on a Tomcat Server ......................................................................................................4-14 Installing Applicare Agent on a JBoss Server .........................................................................................................5-16 Installing Applicare Agent on a Java Server ...........................................................................................................6-18 Appendix..............................................................................................................................................................7-21 7.1 7.2 7.3 7.4 7.5 Setting up multiple WebLogic domains with the same name........................................................................ 7-21 Adding multiple WebLogic servers with the same name to Applicare Console.............................................. 7-21 Licensing...................................................................................................................................................... 7-22 Enabling IntelliTrace on Production Servers ................................................................................................. 7-22 Running Multiple Business Transaction Data Collectors ............................................................................... 7-23

Arcturus Applicare User Guide |

1-3

Installation Guide

1.1 Installation Requirements:

You need the following to run Applicare: HP-UX 11, Sun Solaris 8,9,10, Linux*, AIX, Windows JDK 5.0 or above

Optional: Oracle 9i database or higher (A fully functional Derby/Java DB is included)

1.2 Runtime Requirements

Each Java application server running Applicare agent will use around 50 - 100 MB more PermGen space (more for very large applications). Make sure to adjust -XX:MaxPermSize JVM parameter value of your application servers accordingly. Firewalls should be configured to allow communication from all agents to Applicare server port (8880) and Applicare server to agent server's HTTP(S) port. Also all agent servers and Applicare server should be able to access the Applicare database (default, Derby database running on port 1527). Its recommended to have at least 1 GB of database space available per agent. Therefore if you have five application servers in your environment, you must have at least 5 GB of table space available for your Applicare database.

1.3 Installation Types

The recommended way to install Applicare is to simply use the Installer and follow the Automated Installation instructions shown below. This is what we recommend for all environments, especially if this is your first time installing Applicare. The installer has a GUI mode that works with Windows and UNIX, as well as a UNIX console mode if X/Windows is not available.

1-4

Installation Guide| Arcturus Applicare Installation Guide

1.4 Installing Applicare

The installation process is fairly straight forward. Simply execute the installer and follow the prompts. You will need to pay close attention to the instructions given in the installer, as they are tailored specifically to your environment. Note: If you need a copy of the latest installer please contact Arcturus Support or submit a request on http://www.arcturustech.com . If your environment will not allow running an installer, you can find the manual installation steps in the Appendix. Please contact Arcturus Support for the application archive.

Starting the Installation Program in Graphical Mode on Windows Platforms

Go to the directory where you downloaded the installation program and double-click the installation file: AP_6xx.exe

Starting the Installation Program in Graphical Mode on UNIX Platforms

To run graphical-mode installation, your console must support a Java-based GUI. Launch the installation by entering the following commands: # chmod u+x AP_6xx.bin # ./AP_6xx.bin

Starting the Installation Program in Console Mode on UNIX Platforms

To start the installation in console mode on a UNIX system, enter the command below. It is only necessary to run in the console mode if you do not have access to X/Windows, or the X packages are not installed. # chmod u+x AP_6xx.bin # ./AP_6xx.bin -i console

Silent Mode Installation

Applicare can be installed without requiring any user interaction by running the installer in silent mode and providing all setting in a properties file. In order to create the properties file you have to run the installer with r argument and perform an installation which will create the installer.properties file in the same folder as the installer. (Note: You shouldnt create the installer.properties file in console mode i.e. running with i console argument) # ./AP_6xx.bin -r You can use the created installer.properties file to run silent installations on other machines by passing it as an argument to the installer. Open the installer.properties file in a text editor and modify the property values as required before using on another machine.

Arcturus Applicare User Guide | Installation Guide

1-5

# ./AP_6xx.bin i silent f installer.properties

1.5 Testing the Installation

Now that you have installed Applicare successfully, its time to test your setup to make sure Applicare is functioning properly and ready to be used. 1. Start Applicare server using the installed shortcut or by running startup.bat/sh script in <Applicare Dir>/server/bin directory 2. Login to the Applicare Console at http://<server ip>:8880/applicare (default user id and password is admin). 3. Ensure that you can login and the default dashboard is displayed

1-6

Installation Guide| Arcturus Applicare Installation Guide

Installing Applicare Agent on a WebLogic Server

1. If the WebLogic server is in a different machine from the one running Applicare server, please execute the following steps. a. Run build_agent.bat/sh script in Applicare directory and it will build a file named agent.jar b. Copy the agent.jar file to the machine running Weblogic server and place it in the same directory location. E.g. if you installed Applicare to c:\Applicare, create a directory as c:\Applicare in the machine running Weblogic server and place the agent.jar there c. Run jar xvf agent.jar in a console from the newly created directory to extract all necessary files d. If your extracted folder path is different from the original Applicare installation directory, edit scripts/setAgentEnv.bat(sh) file and modify the ARCTURUS_HOME environment variable to point to the extracted directory path.

2. Setup your Weblogic domain in Applicare console by going to Configuration -> Domain Configuration page and clicking the new button. Specify the Admin servers IP, admin port, username and password along with the domain name and click save. If you have multiple domains with the same name please follow the steps described in the Appendix section. 3. Modify Weblogic servers startup args: a. If you are using the startup scripts to start your Weblogic servers Edit startWeblogic.cmd/sh script in the in your domains bin directory and add the following line right after the @REM START WEBLOGIC or # START WEBLOGIC line and replace the values in bold with actual values as per your environment i. On Windows Systems call <Applicare Dir>\scripts\setAgentEnv.bat ii. On Unix Systems . <Applicare Dir>/scripts/setAgentEnv.sh

Arcturus Applicare User Guide | Installing Applicare Agent on a WebLogic Server

2-7

b. If you are using node manager to start the server add the following arguments to the server start configuration and replace the values in bold with actual values as per your environment i. On Windows Systems Class Path:
<Applicare Dir>\applicare-aspects.jar;<WL Dir>\server\lib\weblogic_sp.jar; <WL Dir>\server\lib\weblogic.jar

Arguments:
-javaagent:<Applicare Dir>\applicare-aspects.jar=verbosity=0,logfile=false -Darcturus_home=<Applicare Dir> -Djava.library.path=<Applicare Dir>\bin;<WL DIR>\server\native\win\32

ii. On Unix Systems Class Path:

<Applicare Dir>/applicare-aspects.jar:<WL Dir>/server/lib/weblogic_sp.jar: <WL Dir>/server/lib/weblogic.jar

Arguments:
-javaagent:<Applicare Dir>/applicare-aspects.jar=verbosity=0,logfile=false -Darcturus_home=<Applicare Dir>

4. Make sure the JVM can increase Perm gen to at least 256MB by adding -XX:MaxPermSize=256m to startup arguments. Server might fail to start with Applicare agent if the perm gen size is too low. 5. Restart the Weblogic server for the changes to take effect 6. Login to Weblogic console and install the applicare_agent.war in <Applicare Dir>/agent/WebLogic directory and target it to your Weblogic server(s) and start the application

2-8

Installing Applicare Agent on a WebLogic Server| Arcturus Applicare Installation Guide

7. Configure the Weblogic server in Applicare console as shown below a. Click Add Server button in the default dashboard

Arcturus Applicare User Guide | Installing Applicare Agent on a WebLogic Server

2-9

b. Provide the IP and port the Weblogic server is listening to, select the appropriate protocol (HTTP/HTTPS) and click save. If the server appears in the auto detected server list, you can click the Add button next to server instead of entering the above details manually.

Thats it, youre all set to start exploring the features, finding root causes, and making your life easier! If youre test didnt go well, contact Arcturus Support for assistance.

2-10

Installing Applicare Agent on a WebLogic Server| Arcturus Applicare Installation Guide

Installing Applicare Agent on a WebSphere Server

1. If the WebSphere server is in a different machine from the one running Applicare server, please execute the following steps. a. Run build_agent.bat/sh script in Applicare directory and it will build a file named agent.jar b. Copy the agent.jar file to the machine running WebSphere server and place it in the same directory location. E.g. if you installed Applicare to c:\Applicare, create a directory as c:\Applicare in the machine running Weblogic server and place the agent.jar there c. Run jar xvf agent.jar in a console from the newly created directory to extract all necessary files

2. Setup your WebSphere profile in Applicare console by going to Configuration -> Domain Configuration page and clicking the new button. Specify the Deployment Managers IP, SOAP port, username and password along with a profile name and click save. Trust Store and Keystore values are required only if Admin security is enabled on WebSphere server. 3. Modify WebSphere servers startup args: You will have to modify the Java Virtual Machine properties of the server before deploying applicare_agent and this can be done through WebSphere Administrative Console -> Servers -> Application Servers -> {Server Name} > Java and Process Management -> Process Definition -> Java Virtual Machine a. On the Java Virtual Machine Configuration page, add the following arguments and replace the values in bold with actual values as per your environment i. On Windows Systems Boot Classpath:
<Applicare Dir>\applicare-aspects.jar

Generic JVM Arguments:

-javaagent:<Applicare Dir>\applicare-aspects.jar=verbosity=0,logfile=false

ii. On Unix Systems Boot Classpath:

<Applicare Dir>/applicare-aspects.jar

Generic JVM Arguments:

-javaagent:<Applicare Dir>/applicare-aspects.jar=verbosity=0,logfile=false

Arcturus Applicare User Guide | Installing Applicare Agent on a WebSphere Server

3-11

b. Now you need to add the following custom properties by clicking the Custom Properties link under Additional Properties heading on the same page. Name arcturus_home java.awt.headless java.library.path profile.name server.name Value <Applicare Dir> true <Applicare Dir>/bin <Profile Name> <Server Name> Description Absolute path to your Applicare directory Replace <Applicare Dir> with absolute path to Applicare directory The profile name you used when configuring the profile in Applicare console Name of your WebSphere server

4. Make sure the JVM can increase Perm gen to at least 256MB by adding -XX:MaxPermSize=256m to Generic JVM arguments. Server might fail to start with Applicare agent if the perm gen size is too low. 5. Restart the WebSphere server for the changes to take effect 6. Login to Administrative console and install the applicare_agent.war in <Applicare Dir>/agent/WebSphere directory and target it to your WebSphere server(s) and start the application. Note: Make sure you install the application to web application context /applicare_agent at the time of deployment.

3-12

Installing Applicare Agent on a WebSphere Server| Arcturus Applicare Installation Guide

7. Configure the WebSphere server in Applicare console as shown below a. Click Add Server button in the default dashboard

b. Provide the IP and HTTP/HTTPS port the WebSphere server is listening to, select the appropriate protocol (HTTP/HTTPS) , provide the SOAP connector port of the server and click save.

Thats it, youre all set to start exploring the features, finding root causes, and making your life easier! If youre test didnt go well, contact Arcturus Support for assistance.

Arcturus Applicare User Guide | Installing Applicare Agent on a WebSphere Server

3-13

Installing Applicare Agent on a Tomcat Server

1. If the Tomcat server is in a different machine from the one running Applicare server, please execute the following steps. a. Run build_agent.bat/sh script in Applicare directory and it will build a file named agent.jar b. Copy the agent.jar file to the machine running the Tomcat server and place it in the same directory location. E.g. if you installed Applicare to c:\Applicare, create a directory as c:\Applicare in the machine running Tomcat server and place the agent.jar there c. Run jar xvf agent.jar in a console from the newly created directory to extract all necessary files d. If your extracted folder path is different from the original Applicare installation directory, edit scripts/setTomcatAgentEnv.bat(sh) file and modify the ARCTURUS_HOME environment variable to point to the extracted directory path. 2. Manual Deployment a. Shutdown the Tomcat server and deploy applicare_agent.war thats located in <Applicare Dir>\agent\Tomcat directory b. Edit catalina.bat/sh file and add the following lines at the beginning and replace the values in bold with actual values as per your environment if you are using startup scripts to start Tomcat i. On Windows Systems set SERVER_NAME=<a unique name to identify the server> call <Applicare Dir>\scripts\setTomcatAgentEnv.bat ii. On Unix Systems export SERVER_NAME=<a unique name to identify the server> . <Applicare Dir>/scripts/setTomcatAgentEnv.sh

3. Automated Deployment. You can use the deployment scripts shipped with Applicare to perform the above manual deployment steps by executing <Applicare Dir>/scripts/deployment/run.bat(sh) scripts. run.bat(sh) tomcat <path to Tomcat dir> < a unique name to identify the server > e.g. ./run.sh tomcat /apache-tomcat-6.0.18 TCServer1

4-14

Installing Applicare Agent on a Tomcat Server| Arcturus Applicare Installation Guide

4. If you are staring Tomcat as a Windows service add the following to your services Java Options section and replace the values in bold with applicable values
-Dserver.name=<a unique name to identify the server> -javaagent:<Applicare Dir>\applicare-tomcat-aspects.jar=verbosity=0,logfile=false -Darcturus_home=<Applicare Dir> -Djava.library.path=<Applicare Dir>\bin

5. Make sure the JVM can increase Perm gen to at least 256MB by adding -XX:MaxPermSize=256m to startup arguments. Server might fail to start with Applicare agent if the perm gen size is too low. 6. Start the Tomcat server 7. Configure the server in Applicare console as shown below a. Click Add Server button in the default dashboard

b. Provide the IP and port the server is listening on and click save

Thats it, youre all set to start exploring the features, finding root causes, and making your life easier! If youre test didnt go well, contact Arcturus Support for assistance.

Arcturus Applicare User Guide | Installing Applicare Agent on a Tomcat Server

4-15

Installing Applicare Agent on a JBoss Server

1. If the JBoss server is in a different machine from the one running Applicare server, please execute the following steps. a. Run build_agent.bat/sh script in Applicare directory and it will build a file named agent.jar b. Copy the agent.jar file to the machine running the JBoss server and place it in the same directory location. E.g. if you installed Applicare to c:\Applicare, create a directory as c:\Applicare in the machine running JBoss server and place the agent.jar there c. Run jar xvf agent.jar in a console from the newly created directory to extract all necessary files d. If your extracted folder path is different from the original Applicare installation directory, edit scripts/setJBossAgentEnv.bat(sh) file and modify the ARCTURUS_HOME environment variable to point to the extracted directory path. 2. Manual Deployment a. Shutdown the JBoss server and deploy applicare_agent.war thats located in <Applicare Dir>\agent\JBoss directory b. Edit run.bat/sh and add the following lines after the lines where run.conf.bat is executed (Windows) or the run.conf file is read (Unix) and replace the values in bold with actual values as per your environment, if you are using startup scripts to start JBoss i. On Windows Systems set SERVER_NAME=<a unique name to identify the server> call <Applicare Dir>\scripts\setJBossAgentEnv.bat ii. On Unix Systems export SERVER_NAME=<a unique name to identify the server> . <Applicare Dir>/scripts/setJBossAgentEnv.sh

3. Automated Deployment. You can use the deployment scripts shipped with Applicare to perform the above manual deployment steps by executing <Applicare Dir>/scripts/deployment/run.bat(sh) scripts.

run.bat(sh) jboss <path to JBoss profile dir> < a unique name to identify the server > e.g. ./run.sh jboss /jboss-5.1.0.GA/server/default AppSvr1

5-16

Installing Applicare Agent on a JBoss Server| Arcturus Applicare Installation Guide

4. If you are staring JBoss as a service add the following to your services JvmOptions and replace the values in bold with applicable values
-Dserver.name==<a unique name to identify the server>;-javaagent: <Applicare Dir>\applicare-tomcataspects.jar=verbosity=0,logfile=false;-Darcturus_home=<Applicare Dir>;-Djava.library.path=<Applicare Dir>\bin

5. Make sure the JVM can increase Perm gen to at least 256MB by adding -XX:MaxPermSize=256m to startup arguments. Server might fail to start with Applicare agent if the perm gen size is too low. 6. Start JBoss server 7. Configure the server in Applicare console as shown below a. Click Add Server button in the default dashboard

b. Provide the IP and port the server is listening on and click save

Thats it, youre all set to start exploring the features, finding root causes, and making your life easier! If youre test didnt go well, contact Arcturus Support for assistance.

Arcturus Applicare User Guide | Installing Applicare Agent on a JBoss Server

5-17

Installing Applicare Agent on a Java Server

1. If the Java server is in a different machine from the one running Applicare server, please execute the following steps. a. Run build_agent.bat/sh script in Applicare directory and it will build a file named agent.jar b. Copy the agent.jar file to the machine running the Java server and place it in the same directory location. E.g. if you installed Applicare to c:\Applicare, create a directory as c:\Applicare in the machine running Java server and place the agent.jar there c. Run jar xvf agent.jar in a console from the newly created directory to extract all necessary files d. If your extracted folder path is different from the original Applicare installation directory, edit scripts/setGenericAgentEnv.bat(sh) file and modify the ARCTURUS_HOME environment variable to point to the extracted directory path. e. Edit your Java servers startup script and add the following lines at the beginning and replace the values in bold with actual values as per your environment f. On Windows Systems set SERVER_NAME=<a unique name to identify the server> set APPLICARE_PORT=<an available port # on which Applicare agent can start listening to> call <Applicare Dir>\scripts\setGenericAgentEnv.bat @REM append the %APP_JAVA_OPTS% to your java command to start your server with Applicare startup arguments. E.g for JBoss server
"%JAVA%" %APP_JAVA_OPTS% %JAVA_OPTS% -Djava.endorsed.dirs="%JBOSS_ENDORSED_DIRS%" -classpath "%JBOSS_CLASSPATH%" org.jboss.Main %*

g. On Unix Systems export SERVER_NAME=<a unique name to identify the server> export APPLICARE_PORT=<an available port # on which Applicare agent can start listening to> . <Applicare Dir>/scripts/setGenericAgentEnv.sh # append the $APP_JAVA_OPTS to your java command to start your server with Applicare startup arguments. E.g for JBoss server
"$JAVA" $APP_JAVA_OPTS $JAVA_OPTS -Djava.endorsed.dirs="$JBOSS_ENDORSED_DIRS" -classpath "$JBOSS_CLASSPATH" org.jboss.Main "$@"

6-18

Installing Applicare Agent on a Java Server| Arcturus Applicare Installation Guide

2. If you are staring your server as a service add the following to your services JVM options and replace the values in bold with applicable values
-Dserver.name==<a unique name to identify the server>;-javaagent: <Applicare Dir>\applicareaspects.jar=verbosity=0,logfile=false;-Darcturus_home=<Applicare Dir>;-Dapplicare_port=<Port to run Applicare agent>

3. Make sure the JVM can increase Perm gen to at least 256MB by adding -XX:MaxPermSize=256m to startup arguments. Server might fail to start with Applicare agent if the perm gen size is too low. 4. Start the server 5. Configure the server in Applicare console as shown below a. Click Add Server button in the default dashboard

b. Provide the IP and port Applicare agent is listening on and click save

Arcturus Applicare User Guide | Installing Applicare Agent on a Java Server

6-19

Thats it, youre all set to start exploring the features, finding root causes, and making your life easier! If youre test didnt go well, contact Arcturus Support for assistance.

6-20

Installing Applicare Agent on a Java Server| Arcturus Applicare Installation Guide

Appendix

7.1 Setting up multiple WebLogic domains with the same name

If you have multiple domains with the same domain name you will have to follow the below procedure to setup domain configuration for each server. 1. Create a domain.props file for each domain by executing the createDomainProps.sh/bat file in <Applicare Dir>/scripts folder.

Usage: createDomainProps.bat Admin_Server_IP Admin_Port Username Password > domain.props e.g. createDomainProps.bat 192.168.0.1 7001 weblogic weblogic > domain.props

2. Add -Dapplicare.domain.props argument to JAVA_OPTIONS in startup script or Java arguments in server startup configuration if you are using Node manager to start the server. Set the argument value to the absolute path of the domains.props file.

e.g. -Dapplicare.domain.props=/Applicare/scripts/domains.props

7.2 Adding multiple WebLogic servers with the same name to Applicare Console
If you want to add two or more servers with the same name from different domains to Applicare console you will have to assign an alias to one or all servers to make each server name unique and recognizable in Applicare. You can assign an alias to a server by adding the Dserver.name=<Any Name> parameter to the server startup arguments (Replace <Any Name> with the name you want to assign). After adding the argument, restart the server and add it to Applicare Console. Applicare will detect the alias and use it instead of the WebLogic server name.

Arcturus Applicare User Guide | Appendix

7-21

7.3 Licensing
Applicare installation will create an evaluation license that will allow you to use Applicare for 3 weeks and to monitor up to 3 servers. If you have a commercial license please copy it to your Applicare directory overwriting the existing AP_AdminServer.key file.

7.4 Enabling IntelliTrace on Production Servers

IntelliTrace was designed to run on production servers with very minimal overhead so that the end users don't experience a noticeable performance degradation. However on large applications where lot of third party libraries are used, it is recommended to enable IntelliTrace on a test server and perform the following optimization before enabling IntelliTrace on production servers. Basically you can inform IntelliTrace to ignore third party libraries altogether by adding the package names of the third party code to trace-exclusions.txt file in Applicare home directory. In most cases you are not interested in the internal working of these third party libraries and excluding them from tracing will reduce the overhead significantly. Enable IntelliTrace on the test server (requires restart) and run through few different transactions or run a load script. Now in IntelliTrace window if you expand the transactions to view call graphs you may see third party classes/methods in the call graph. Open trace-exclusions.txt file in a text editor and you can see that we have already added most of the common libraries such as Spring framework and Apache Commons in this file. So if you see some third party classes/methods in you IntelliTrace window that you are not concerned about, you should add the base package name of that library to traceexclusions.txt in a new line. e.g. To disable tracing all classes in org.apache and its sub packages, you should add the following line org.apache. Remember to copy the modified file to all agent Applicare directories on other machines too and you will have to restart application servers for the changes to take effect. Now you can use the modified file in production Applicare installation to get best performance while IntelliTrace is enabled. Also you can send the packages you want excluded to Arcturus Tech so they will be included in traceexclusions.txt file by default in future versions.

7-22

Appendix| Arcturus Applicare Installation Guide

7.5 Running Multiple Business Transaction Data Collectors

In some large environments a single Applicare server might not be able to keep up with all the business transaction traces generated by monitored servers. Therefore in order to allow scaling to large number of servers Applicare allows you to run multiple Business Transaction data collectors that can divide data collection from servers.

Configuration
You have to configure the servers the collector should gather data from by editing the btx.props file in btm_collector folder. e.g. If you want the collector to gather data from 3 monitored servers, specify their URL as below url_1=http://sc1.mydomain:8080 url_2=http://sc2.mydomain:8080 url_3=http://sc2.mydomain:7080

Running a collector
To start the collector, simply execute run.bat or run.sh script in the btm_collector folder after completing the configuration as described above.

Running multiple collectors on the same machine

To start another collector: 1. Make a new folder in btm_collector 2. Copy the btx.props file to the new folder and modify it to point to the servers you want your new collector to gather data from 3. Make a copy of the run.bat/sh file 4. Modified the new script file and set the AGENT_HOME variable in the script to point to the new sub folder you created in the above steps 5. Execute the new script file to start the collector

Running a collector in a different machine

To run a collector on a different machine simply copy your complete Applicare folder to the new machine and follow the steps as above. Please make sure the absolute path of your Applicare folder on the new machine is the same as the original Applicare folder.

Arcturus Applicare User Guide | Appendix

7-23