WL-OPC ReadMe

The license agreement (EULA) can be found on wlopc-license.txt page which is located in the "lic" folder

wl-opc.v1.9.2.zip/wl-opc file contains the following directories and files

Prerequisites for The Production Environment Installation

1. Setup at least one server/machine with the below configurations:
   
   1. Supported Operating Systems (OS): Up to date Linux 7.X or 8.X, Oracle Solaris 10.X, MS Windows 10+, MS Windows Server 2019+ and Apple OS X 10.X platforms. Linux OS 7.x or 8.X distributions (Oracle Enterprise Linux, Red Hat Enterprise Linux, CentOS... etc.) are recommended for the production environment
   2. Minimum 1 or 2 CPU Core. 2+ CPU Core is recommended to monitor 50+ WebLogic domains
   3. Minimum 2 GB Memory/RAM. 6+ GB memory is recommended to monitor 50+ WebLogic domains
   4. Minimum 40 GB disk size. 80 GB /u01 disk is recommended. /u01 is the reference OS disk mount point for the documentation
   5. Create an OS user/group. opc:opc with /u01/opc home path is recommended
      Consider assigning WL-OPC's server IP address according to your common WebLogic AdminServer(s) IP subnet. WL-OPC must access all your WebLogic domain park
      For trial or POC installation; just extract the zip package then go to the ./wl-opc/bin folder and edit setenv.properties file then run .wl-opc/bin/opc start command
2. Download and install the latest JDK 1.8.x compatible with your OS platform
   http://www.oracle.com/technetwork/java/javase/downloads/jdk8-downloads-2133151.html
3. Give network access or OS firewall access to the server's WL-OPC port. Default WL-OPC application server port 8080 must be accessible from the client browser to access WL-OPC web console
4. Define below network access in between WL-OPC server and WebLogic AdminServer(s)
   
   

   Source	WL-OPC Server $IP
   Destination	WebLogic AdminServer $IP:$PORT    *Multiple $IP:$PORT | Apply to all WebLogic domains

   Source	WebLogic AdminServer $IP                  *Multiple $IP | Apply to all WebLogic domains
   Destination	WL-OPC Server $IP:$PORT

5. SMTP/Mail server information and SMTP relay for the WL-OPC server to deliver email notifications
6. Install a proxy webserver (i.e. NGINX, Apache HTTP Server) then configure it in front of WL-OPC application server or setup a local LoadBalancer (i.e. F5, Citrix Netscaler) then configure it in front of the WL-OPC application server. NGINX proxy webserver is recommended (OPTIONAL)
7. Register local intranet DNS record then access the WL-OPC console via http(s)://opc.company.com/opc URL. Announce it to your operation team(s) for a standard and operational excellent Oracle WebLogic/FMW management

   opc.company.com

   WL-OPC access $IP

Easy and quick installation! (Trial Purpose, Summary)

    Step by step and more detailed installation guide for production environment is available: Go to Step by Step Installation Guide

• Install latest JDK 1.8.x
• Extract wl-opc.v1.9.2.zip package to /u01/opc (i.e. OS user home folder)
• Go to $WLOPC_HOME/bin folder and edit setenv.properties file
• Execute the ./opc start command to start the WL-OPC application server
• That's all! Access WL-OPC web console http(s)://$wlopc-server-ip:$port/opc
• Login to the WL-OPC Console then complete the configuration wizard for once (Default Credentials: admin/wl-opc)

WL-OPC Architecture and Runtime

Installation and Introduction Video Tutorials

    Installation tutorial contains basic information about WL-OPC console usage

  WL-OPC Installation and Registering Oracle WebLogic Domain(s):
      How to Install WL-OPC? - Central WebLogic & FMW Domain Monitoring, Management, Automation, DevOps      

  Introduction Tutorial:
      Oracle WebLogic and FMW Domain Monitoring & Management Center      

       Reference Paths for the Installation Steps

                          

                              
OS User / Group
 opc:opc  
                              
OS User Home Folder
 /u01/opc  
                              
JDK Installation Path
 /u01/opc/jdk/jdk1.8.0_271  
                              
WL-OPC Extract Path
 /u01/opc/wl-opc (= $WLOPC_HOME)  
                          
                        

1. Upload wl-opc.v1.9.2.zip and latest JDK 1.8.x installation files to the server (i.e. /tmp folder)
2. Create opc:opc OS user and group

                          $ groupadd opc
   $ useradd -g opc -d /u01/opc opc
   $ passwd opc
   $ sudo su - opc        
                                   

3. Install JDK to folder and test the JDK installation

                            $ mkdir -p /u01/opc/jdk
   
   $ tar xzvf /tmp/jdk-8u271-linux-x64.tar.gz -C /u01/opc/jdk/
   $ /u01/opc/jdk/jdk1.8.0_271/bin/java -d64 -version
   
   java version "1.8.0_271"
   Java(TM) SE Runtime Environment (build 1.8.0_271-b09)
   Java HotSpot(TM) 64-Bit Server VM (build 25.271-b09, mixed mode)
                                   

4. Extract WL-OPC zip package to path

                $ unzip -d /u01/opc /tmp/wl-opc.v1.9.2.zip
                                   

5. Edit .bash_profile of "opc" OS user and set JAVA_HOME, WLOPC_HOME environment variables

                # Reference Linux PATH Configuration
   
   # vi ~/.bash_profile
   
   JAVA_HOME=/u01/opc/jdk/jdk1.8.0_271
   export JAVA_HOME
   
   WLOPC_HOME=/u01/opc/wl-opc
   export WLOPC_HOME
   
   PATH=$JAVA_HOME/bin:$WLOPC_HOME/bin:$PATH:$HOME/bin
   export PATH
   
                                   

6. Load new bash profile and test JAVA_HOME, WLOPC_HOME environment variables

                            $ cd
   $ . .bash_profile
   
   $ echo $JAVA_HOME $WLOPC_HOME
   /u01/opc/jdk/jdk1.8.0_271 /u01/opc/wl-opc
   
   $ which java
   ~/jdk/jdk1.8.0_271/bin/java
   
   $ which opc
   ~/wl-opc/bin/opc        
                                   

7. Edit $WLOPC_HOME/bin/setenv.properties file. Update JAVA_HOME, WLOPC_HOME and SERVER_ADDRESS variables according to your server settings

              # vi $WLOPC_HOME/bin/setenv.properties
   
   # File Name: setenv.properties
   # Set WL-OPC Environment Variables
   
   JAVA_HOME=""                            # Set path to $JAVA_HOME
   WLOPC_HOME=""                           # Set path to $WLOPC_HOME
   SERVER_ADDRESS=""                       # Set WL-OPC server IP or hostname
   SERVER_PORT="8080"                      # Change port value if 8080 port is already in use
   SERVER_CONTEXTPATH="/opc"               #
   USER_MEM_ARGS="-Xms1024m -Xmx2048m"     # Increase or decrease memory values according to number of WebLogic domain(s)
   JAVA_OPTIONS="-XX:+UseG1GC -Dfile.encoding=UTF-8"
   DERBY_OPTIONS="-Dderby.locks.escalationThreshold=2147483647 -Dderby.locks.deadlockTimeout=60 -Dderby.locks.waitTimeout=120 -Dderby.storage.initialPages=500 -Dderby.storage.pageCacheSize=16000 -Dderby.storage.pageSize=32768"
                                   

   Take the below screen capture for your reference:

   
   Initial JVM -Xms and -Xmx memory arguments have been already configured as 1024m initial and 2048m max heap size. According to your traffic and number of WebLogic domain assets, you can increase the heap size of WL-OPC
   
   
   $WLOPC_HOME/bin/opc executable file uses below environment variables. Update environment variable inside setenv.properties file with your custom values and keep opc executable file as original
   • JAVA_HOME
   • WLOPC_HOME
   • SERVER_ADDRESS
   • SERVER_CONTEXTPATH
   • SERVER_PORT
   • USER_MEM_ARGS
   • JAVA_OPTIONS
   • DERBY_OPTIONS
   • WLOPC_JAR_NAME
8. Start WL-OPC application server

                             $ opc start
   # For BASH mode (i.e. Ubuntu OS) run opc command as "bash opc start"
   
                                   

   nohup command is already used in the ./bin/opc executable file. Do not start opc with additional nohup command. "opc start" tails $WLOPC_HOME/bin/WLOPC/logs/wl-opc.out log file by default; you can use "CTRL + C" to exit tail console. The OPC background daemon process will continue to work
   
   Below log must be seen in the WL-OPC log

                                   INFO 14181 --- [main] com.wlsdm.opc.WLOPC: OPC server is RUNNING and ready to accept requests. v1.9.2
                                   

   Check OPC process

                              $ opc status
   
   # OR
   
   $ ps -ef | grep wl-opc    
                                   

   OPC command usage and available operations

                opc command usage: /u01/opc/wl-opc/bin/opc {start|stop|status|tlogs|dbshrink|dbpurge $days|backup|preupgrade}
   
   START________: $ opc start          # starts opc application server
   STOP_________: $ opc stop           # stops opc application server
   STATUS_______: $ opc status         # checks opc process and prints opc PID
   TLOGS________: $ opc tlogs          # tails opc logs
   DBSHRINK_____: $ opc dbshrink       # shrinks opc database
   DBPURGE______: $ opc dbpurge $days  # purges opc database
   BACKUP_______: $ opc backup         # backups opc runtime files and database
   PREUPGRADE___: $ opc preupgrade     # prepares opc for the upgrade
                                   

9. After starting WL-OPC application server. Open web browser and go to http:// $SERVER_ADDRESS : $SERVER_PORT / $SERVER_CONTEXTPATH (i.e. http://10.112.12.12:8080/opc)

   Take the below screen capture for your reference:

   
10. Login to the WL-OPC web console with the default super-user credentials. Change the default password or create your super-user after the WL-OPC configuration wizard completed

                 Username: admin
    Password: wl-opc

11. WL-OPC configuration wizard is available for the first login. Complete the WL-OPC configuration wizard to setup your WL-OPC infrastructure
12. Check below network access before adding WebLogic domains to WL-OPC

                 # On WL-OPC Server:
    
    telnet "$WebLogic_AdminServer_IP" "$AdminServer_PORT"
    
    
    
    # On WebLogic Admin Server(s):
    
    telnet "$WL-OPC_Server_IP" "$WL-OPC_PORT"
                                    

13. Finally, follow instructions on the WL-OPC console to register WebLogic domains. Enjoy your operational excellent central product to automate Oracle WebLogic/FMW environments!

Edit .bash_profile of "opc" OS user and set JAVA_HOME, WLOPC_HOME environment variables

                    # Reference Linux PATH Configuration

# vi ~/.bash_profile

#######################################################

JAVA_HOME=/u01/opc/jdk/jdk1.8.0_271
export JAVA_HOME

WLOPC_HOME=/u01/opc/wl-opc
export WLOPC_HOME

PATH=$JAVA_HOME/bin:$WLOPC_HOME/bin:$PATH:$HOME/bin
export PATH

#######################################################
                        

OPC command arguments and available operations

 opc command usage: /u01/opc/wl-opc/bin/opc {start|stop|status|tlogs|dbshrink|dbpurge $days|backup|preupgrade}

START________: $ opc start           # starts opc application server
STOP_________: $ opc stop            # stops opc application server
STATUS_______: $ opc status          # checks opc process and prints opc PID
TLOGS________: $ opc tlogs           # tails opc logs
DBSHRINK_____: $ opc dbshrink        # shrinks opc database
DBPURGE______: $ opc dbpurge $days   # purges opc database by the specified number of days. where $days is the number of days to retain. for example, if you specify 30 days, then any records older than 30 days are purged. reports data and metadata are still available after purge operations
BACKUP_______: $ opc backup          # backups opc runtime files and database
PREUPGRADE___: $ opc preupgrade      # prepares opc for the upgrade
                        

OPTIONAL: Install a proxy webserver (i.e. NGINX, Apache HTTP Server) then configure it in front of the WL-OPC application server or setup a local LoadBalancer (i.e. F5, Citrix Netscaler) then configure it in front of the WL-OPC application server. NGINX proxy webserver is recommended

1. Install NGINX to WL-OPC server
   https://docs.nginx.com/nginx/admin-guide/installing-nginx/installing-nginx-open-source/
2. Configure WL-OPC virtual host as below and update according to your WL-OPC environment settings

   							server {
           listen 80;
   
           root /var/www/wlopc;
           index index.html index.htm;
   
           # Make site accessible from http://localhost/
           server_name opc.company.com;
   
           location / {
                   # First attempt to serve request as file, then
                   # as directory, then fall back to displaying a 404.
                   # try_files $uri $uri/ =404;
                   # Uncomment to enable naxsi on this location
                   # include /etc/nginx/naxsi.rules
   
   		proxy_set_header X-Real-IP $remote_addr;
   		proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
   		proxy_set_header Host $http_host;
   		proxy_set_header X-NginX-Proxy true;
   
   		proxy_pass http://$WL-OPC_Server_IP:8080/;
   		proxy_redirect off;
   
   		# Socket.IO Support
   		proxy_http_version 1.1;
   		proxy_set_header Upgrade $http_upgrade;
   		proxy_set_header Connection "upgrade";
   
                   rewrite ^/$ http://opc.company.com/opc permanent;
   
           }
   }
                                   

Overwriting the wl-opc folder is the only step for the upgrade. Replace the new wl-opc folder with the existing wl-opc folder and then restart WL-OPC. Follow the below steps for a clean upgrade

1. Stop WL-OPC application server

                               $ opc stop
                                   

2. Optional: Take a full backup of WL-OPC. If you already backed up your WL-OPC manually, skip this step

                           # !!! IMPORTANT !!!
   
   # 1) Existing bin folder, opc.sh, setenv.properties and wl-opc.v1.9.2.jar files will be available in backups/backup.$dateTime folder
   
   # 2) ./bin/opc.sh and ./bin/setenv.properties files are backed up as opc.sh_ORIG and setenv.properties_ORIG under bin folder
   
   
   $ opc backup
   
   ....
   ...
   ..
   .
   Full WL-OPC Backup is completed successfully and available in backups folder as;
   --------------
   Folder Content: /u01/opc/wl-opc/backups/backup.202012202138/
   --------------
   total 338768
   -rw-r--r--  1 opc  opc  74092685 Dec 20 21:38 bin.202012202138.tar.gz
   -rwxr-xr-x@ 1 opc  opc     11477 Dec 20 21:38 opc.sh.202012202138
   -rwxr-xr-x@ 1 opc  opc      7496 Dec 20 21:38 setenv.properties.202012202138
   -rw-r--r--@ 1 opc  opc  89371436 Dec 20 21:38 wl-opc.v1.9.2.jar.202012202138    
                                   

3. Run the preupgrade or mv command to take the backup of original opc and setenv.properties files and prepare WL-OPC for the upgrade

                                     # opc versions after v1.9.1
   $ opc preupgrade
                                     # opc versions before v1.9.1
   $ mv setenv.properties setenv.properties_PRE-ORIG
                                   

4. Upgrade Step: Extract or copy the new WL-OPC package folder to the existing $WLOPC_HOME folder. Take the below "Usage of Copy Command for Upgrade" section as a reference and apply commands according to your environment
   
   Copy Command for Upgrade

   # /path/to/wl-opc = $WLOPC_HOME
   
   # Accepts all file overwrite warnings
   
   cp   -fR   /path/to/new-package/wl-opc   /path/to/wl-opc/../.   
   
   # OR
   
   cp   -fR   /path/to/new-package/wl-opc   $WLOPC_HOME/../.   

   
   
   Usage of Copy Command for Upgrade
   

   					    	# !!! IMPORTANT !!!
   
   # 1) Consider new version binary is uploaded to /tmp folder and available as /tmp/wl-opc."$NEW-VERSION".zip
   
   # 2) Current $WLOPC_HOME equals to /u01/opc/wl-opc
   
   
   $ cd /tmp
   $ unzip -d /tmp/opc-new /tmp/wl-opc."$NEW-VERSION".zip
   $ cp -fR /tmp/opc-new/wl-opc /u01/opc/.
   
   # Upgrade is completed
                                   

      ./bin/opc and ./bin/setenv.properties files are overwritten by executing cp -fR command. Current original versions are backed up as _PRE-ORIG extension in bin folder at Step-3. opc start command handles and loads previous setenv.properties file
5. Start the new upgraded WL-OPC version and make sure new version release numbers printed in the wl-opc.log as below

                       $ opc start
                                   

   INFO 14181 --- [main] com.wlsdm.opc.WLOPC: OPC server is RUNNING and ready to accept requests. "$NEW-VERSION"
                                   

      If the start command is not working and giving [ERROR] !!! One or more variables are undefined !!! warning then go to "VII. Step by Step Installation Guide" section and find missing properties. Add or update variables in setenv.properties file by taking Step-7 as a reference

Help is available

• on the HTML page in the wl-opc/docs directory. Open   ./docs/help
• online at   http://www.wlsdm.com/wl-opc/docs/help

Please follow us and get updates. Never miss a post about WLSDM, WL-OPC, Oracle WebLogic/FMW monitoring and management learnings

  Community / Support

  Medium Blog

  Twitter Follow

  YouTube Subscribe

  LinkedIn Connect

  Facebook Like

  Instagram follow4follow

  Email Support Team