ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.



Article ID: 53069


Updated On:


SOLVE:Operations Automation SOLVE:Access Session Management SOLVE:FTS OPS/MVS Event Management & Automation SOLVE



Procedures to ensure you are running with the updated OPSLOG WebView.


OPSLOG WebView R11.6

If earlier versions of the OPSLOG WebView client are stored in local cache, Java will connect using the cached OPSLOG WebView client. If the OPSLOG web server has since been upgraded, you may need to download an upgraded OPSLOG WebView client as well. Upgrade to OPS/MVS R11.6 (or higher) will upgrade both the OPSLOG WebView server and client on the server side.

To ensure you are running with the updated OPSLOG WebView client you must clear out the Java cache for the application.

Start, Settings, Control Panel, Java Control Panel

<Please see attached file for image>

Figure 1


<Please see attached file for image>

Figure 2

Select OPSLOG WebView java application.

Click on X to delete cache.

Browse OPSLOG web server. Java will download and install the OPSLOG WebView client as if it was the first-time visit to the web server.

If you browse the OPSLOG WebView server without first clearing out the local Java cache, exit WebView client. Close your browser window. Launch the browser again and this time Java downloads and installs a current version of the OPSLOG WebView client.

Note: Deleting temporary files from your browser will also cause Java to download and install the OPSLOG WebView client.


Component: SOPMVS


1558721217553000053069_sktwi1f5rjvs16vy4.gif get_app
1558721215425000053069_sktwi1f5rjvs16vy3.gif get_app