This software is currently BETA, use at your own risk
What is it:
WeblogicMonitor is a command line based java utility which can be used to collect performance and usage statistics from Weblogic installations used with PeopleSoft. It currently inserts this data into an embedded Sqlite database for later use with the Viewing component.
- Java 7+ If you run this utility from one of your PeopleSoft servers you should be able to utilize the java version provided.
- wlfullclient.jar – This file you must create yourself from your one of your Weblogic installations. Here are the instructions from Oracle, but I also provide them here.
- Change directories to the server/lib directory: cd WL_HOME/server/lib
- Use the following command to create wlfullclient.jar in the server/lib directory: java -jar wljarbuilder.jar
- After uncompressing the WeblogicMonitor zip file, you should find WeblogicMonitor/lib, place wlfullclient.jar into the lib directory
- T3S support requires additional files detailed below, but they are not needed if you use only T3
How to use WeblogicMonitor:
- Download the newest WeblogicMonitor version from the Downloads Page
- Uncompress to a directory ex: D:\WeblogicMonitor or /opt/apps/utils/WeblogicMonitor
- Ensure you have created wlfullclient.jar and copied it to the WeblogicMonitor/lib directory
- Change directory to the installed path: cd D:\WeblogicMonitor
- Run java -jar WeblogicMonitor.jar help
- The beta license will be displayed enter y to accept it.
- The help info will be displayed
- Run java -jar WeblogicMonitor.jar insert to add a Weblogic Admin Console, follow the prompts, they should be self explanatory but here is an example:
[code]java -jar WeblogicMonitor.jar insert
Please enter name of the PeopleSoft Instance:
Please enter name of the weblogic server to monitor:
This would normally be PIA on single or multi server Instances
However it could be PIA1/2 in clustered instances or something custom.
Please enter hostname of the Weblogic Admin Console:
Please enter port of the Weblogic Admin Console:
Please enter protocol of the Weblogic Admin Console (t3 or t3s):
Please enter username of the Weblogic Admin Console:
Please enter password of the Weblogic Admin Console:
Does the following data look correct:
HCM PIA psweb1 9000 monitor monitor
- I highly recommend not using the default user and password.
- I also recommend creating a new user in Weblogic and assign it the Monitors role.
- Run java -jar WeblogicMonitor.jar list to display current configuration and verify
[code]ROW: 1 HCM PIA psweb1 9000 monitor [ENCRYPTED PASSWORD DISPLAYED][/code]
- Run java -jar WeblogicMonitor.jar monitor or monitor <time> to begin monitoring where <time> is a polling interval in seconds
How to use WeblogicMonitor with T3S:
If the admin console port requires SSL to access (Administration Port option enabled) use the following steps to enable T3S for the WeblogicMonitor.
- Copy cryptoj.jar and wlcipher.jar from WL_HOME/server/lib to the WeblogicMonitor/lib directory
- Create a trust store and import the admin console certificate or your required root CA.
- Start the monitor with the following options: -Dweblogic.security.SSL.enableJSSE=true -Dweblogic.security.CustomTrustKeyStoreFileName=<your file> -Dweblogic.security.CustomTrustKeyStorePassPhrase=<your password> -Dweblogic.security.TrustKeyStore=CustomTrust -jar WeblogicMonitor.jar monitor
- I used -Dweblogic.security.SSL.enableJSSE=true due to Weblogic not liking the OID of the cert I generated with keytool. The error you may receive without enabling JSSE is PKIX: Unsupported OID in the AlgorithmIdentifier object. This depends on your version and what was used to create your certificate of course.
- If you are switching from T3 to T3S or vice versa with an existing database file, you can run java -jar WeblogicMonitor.jar updateProtocol to update the protocol for each environment.
- Now requires Java 7 or higher.
- Added support for the T3s (T3 with SSL) protocol in additional to the original T3 protocol.
- Added collection of the root servlet data (psp, psc, cs, SchedulerTransfer, etc). This adds about 18 additional rows of data each polling interval.
- New version should backup and then upgrade existing database file. The database file version number has now changed.
- You may wish to make a manual backup on your own as well.
- Changes made to support performance improvements for the Viewer utility.
- Created a routine which should create a new database file for every month the monitor runs. This will be my data management strategy for now. You can then delete the files you no longer need to keep.
- Changed the database file name to weblogicmon<dbversion>-yyyy-MM.db (weblogicmon0.2.14-2013-06.db) in support of the rolling data files.
- Modified when the config is loaded. It now loads every polling interval. This allows a running monitor to have it’s configuration changed without restarting the monitor.
- Added a routine to upgrade database files from older versions.