 |
 |
 |
 |
A WebLogic domain with separate Admin and Managed Server/s is recommended.
AutoPilot WL installer can be downloaded with VM or without VM. If you download AutoPilot WL installer without VM then you would need to run it with the path set to bin directory of the Java 2 SDK. Java 2 SDK bin directly should be added to the beginning of the PATH system variable.
To start the installation in console mode on a Unix system:
Log in to the target UNIX system.
Download the software as from Arcturus website.
Go to the directory where you downloaded the installation program file:
autopilotWL.bin
Launch the installation by entering the following commands:
chmod a+x autopilotWL.bin
./autopilotWL.bin -i console
The installation program begins to install AutoPilot WL.
To start the installation in graphical mode on a Windows system:
Log in to the Windows system.
Download the software as from Arcturus website.
Go to the directory where you downloaded the installation program and double-click the installation file:
autopilotWL.exe
The installation program begins to install AutoPilot WL. Proceed to Running the Installation Program.
To run graphical-mode installation, your console must support a Java-based GUI.
Log in to the target UNIX system.
Download the software as from Arcturus website.
Go to the directory where you downloaded the installation program file:
autopilotWL.bin
Launch the installation by entering the following commands:
chmod a+x autopilotWL.bin
./autopilotWL.bin
The installation program begins to install AutoPilot WL.
Proceed to Running the Installation Program.
The installation program prompts you to enter specific information about your system and configuration. Here are the details of the panels where user input is requested.
BEA WebLogic Domain Details
This information is used to connect to WebLogic domain for deployment of AutoPilot WL. It is very important to have this information right. If there is any error in this information AutoPilot installer will not be able to deploy AutoPilot WL and will display a message installation error/failed.
System user and password are WebLogic Admin User and WebLogic Admin Password.
Managed Server entered in this panel would get the AutoPilot agent installed. Also when AutoPilot Tuning Wizard is used the managed server specified in this panel will be tuned.
In case of installation on a combined tier WebLogic environment, you will enter admin server name as the managed server too.
AutoPilot Database Creation Panel
Currenly auto creation of table schema for Oracle is not supported. Oracle users can run the script oracleTableSchema.sql installed under {autopilot_install_dir}/Server/ddl/Oracle for AutoPilot schema creation.
Similarly mysqlTableSchema.sql script is available for MySql under {autopilot_install_dir}/Server/ddl/MySQL.
AutoPilot Database/Driver information Panel for Connection Pool Creation
This info is used for connecting to the database for creation of AutoPilot schema and AutoPilot connection pool on WebLogic domain where AutoPilot is installed.
Note: You should provide this information even if you choose to not create the tables through installer.
AutoPilot Installation Location
AutoPilot installation directory name should not contain blank spaces.
BEA WebLogic Admin Server Startup Script Modifications Information Panel
Last panel in before installation would be
After you hit Install, all the required AutoPilot WL sp2 files will be installed in the directory choosen. AutoPilot installer will also build an ant script for deployment of various AutoPilot J2EE components. Follow the instructions below from outside the installer for deployment of AutoPilot WL.
You need to run {AutoPilot_Install_Dir}/config/autopilot_deploy.sh or {AutoPilot_Install_Dir}/config/autopilot_deploy.cmd to deploy AutoPilot WL on WebLogic. Before you fire autopilot_deploy.sh/autopilot_deploy.cmd, follow the instructions below that are also available in {AutoPilot_Install_Dir}/config/ReadMeFirst.html
1. Make a backup of you config.xml for WebLogic domain where AutoPilot will be installed. Backed up config.xml comes handy if the autopilot_deploy script fails for some reason. You can fix the issue, start the domain with clean config.xml (without partial deployment of AutoPilot) and again execute the autopilot_deploy script for AutoPilot WL deployment.
2. create a test connection pool to the database you have choosen in AutoPilot installer. Use the same connection pool properties as entered in AutoPilot Installer, to create this test pool. Once the pool is created and deployed you can delete the pool. This is done to ensure their are no issues with creating a connection pool to the database.
autopilot_deploy script automatically creates and deploys the pool but fails if the pool creation is not successful for some reason.
3. If you have not installed WebLogic server with defaults in {BEA_HOME} directory ie you have changed the name of weblogic81 directory under {BEA_HOME}, you will need to do the following
* In autopilot_deploy.sh/autopilot_deploy.cmd file specify the correct location of weblogic.jar in the classpath
* Correct the location of weblogic.jar for lax.class.path property in {AutoPilot_Install_Dir}/Client/AutoPilot TuneWizard.lax
Once you have followed the steps above, fire the {AutoPilot_Install_Dir}/config/autopilot_deploy.sh or {AutoPilot_Install_Dir}/config/autopilot_deploy.cmd to deploy AutoPilot WL on WebLogic.
AutoPilot License Installation
AutoPilot Install comes with a 15 day evaluation license. Once you install AutoPilot, an evaluation license file is installed under {AutoPilot_Install_DIR}/Server/AP_adminservername.key. AP_adminservername.key must be copied to another file with adminservername replaced by the name of WebLogic Admin or managed server for which key is to be used e.g. to run AutoPilot Engine on WebLogic admin server named MedRecAdminServer, AP_adminservername.key file should be copied to AP_MedRecAdminServer.key and placed in the directory specified by arcturus_home property in admin server startup script. Similary to run AutoPilot agent on WebLogic managed servers this file should be copied to AP_managedservername.key e.g. if WebLogic managed servers names are ms1 and ms2 then AP_adminservername.key should be copied to AP_ms1.key and AP_ms2.key and these files should be placed in arcturus_home directory for these respective managed servers.
Restart WebLogic after AutoPilot WL deployment and license installation. AutoPilot WL menu appears in WebLogic console.
On Windows Platform: In case you are installing AutoPilot on a combined tier WebLogic environment ie combined WebLogic Admin Server and Managed Server environment, you will need to add {autopilot_install_dir}/Server/bin to your java library path
-Djava.library.path=C:/ArcturusAutopilotWL/Server/bin
Once you pass java library path parameter, you will also need to add {BEA_HOME}/weblogic81/server/bin to the java library path for BEA Performance Pack to work. eg.
-Djava.library.path=C:/ArcturusAutopilotWL/Server/bin;C:/bea/weblogic81/server/bin
And voila. You have successfully installed AutoPilot.
NOTE: A typo in the values entered can cause installtion to fail. If you get installation error/failed message you may not need to re do the installation. You should first check if the installer did install AutoPilot WL on to the targeted domain. If it didn't install then there may be some error in the information entered. You should ensure the values entered are correct by opening build.properties from {autopilot_install_dir}/config directory. Once you have checked all the values are correct you can run the script autopilot_deploy.bat or autopilot_deply.sh (depending upon the platform). Please ensure there is no component of AutoPilot installed in the domain before running autopilot_deploy.bat/sh file. If any of the components that AutoPilot installs is already installed script would fail and wouldn't be able deploy all the components AutoPilot WL needs. You can have AutoPilot components installed due to a previous successful/failed installation.
