If you have Business Transactions defined in Applicare, go to Configuration -> Export / Import Configuration and export all definitions to a file by clicking the Export button.
Create a new schema in Oracle for Applicare.
Run the SQL scripts in <Applicare Dir>/sql/ddl/oracle to the createApplicare tables in the schema.
Run the createDomainProps.bat(sh) script in <Applicare Dir>/directory to get the encrypted password for the database user. The script requires four parameters. The first three can be any character, but the last parameter must be the database user's password.
For example, if the password is applicare:
>createDomainProps.bat x x x applicareThe output will be similar to the below:
applicare.serverIP=x applicare.serverPort=x applicare.systemUser=AZ5EPnifefE= applicare.systemPassword=ixUYQx6AgYSmaVGz5l2Iwg==
The last line of the output contains the encrypted password. In this case it's ixUYQx6AgYSmaVGz5l2Iwg==. Please note it down for the next step.
- Open the Applicare.props file in the Applicare install directory with a text editor and change the following property values as described in the table below.
| Property | Value | Description |
|---|---|---|
| applicare.dburl | jdbc:oracle:thin:@<db host>:1521:<SID> | Replace <db host> with the database IP and <SID> with your Oracle SID. e.g.: jdbc:oracle:thin:@localhost:1521:ORCL |
| applicare.dbVendor | Oracle | |
| applicare.dbTestSQL | SELECT 1 FROM DUAL | |
| applicare.dbDriverClass | oracle.jdbc.OracleDriver | |
| applicare.dbUsername | <Database Username> | Set your Oracle database user name as the value here |
| applicare.dbPassword | <Encrypted Database Password> | Copy and paste the encrypted password you generated in the above step |
Restart the Applicare server. Ignore the warning messages about failing to create tables and triggers as they have been already created by running the SQL scripts manually.
Login to Applicare and, if you have any, add the WebLogic / WebSphere domains in Configuration -> Domain Configuration.
Import any Business Transactions definitions exported to the file on the first step by going to Configuration -> Export / Import Configuration, clicking the Import button and selecting the definition file.
Copy the modified Applicare.props file to the Applicare agent folders on other physical machines running Applicare agents, if any.
Copy the Oracle JDBC driver jar file to your application server's class path if it's not already there.
Restart Application servers running Applicare agents for the changes to take effect. Add the servers to the Applicare console again from the Applicare console's home page.
Verify data is saved in the new database by going to the Analyzers -> Heap Analyzer -> History tab and viewing historical heap performance data for any of the monitored servers. Historical performance data should start to show up after about 5 minutes of starting the monitored server.