Monitoring and Control Accelerator · The Guidewire Monitoring and Control Accelerator can be...

1

MONITORING AND CONTROL ACCELERATOR GUIDE - 17 MAY 2017

Monitoring and Control

Accelerator

Components for monitoring and controlling Guidewire products

A S O L U T I O N G U I D E C O V E R I N G

E N H A N C E D G U I D E W I R E P R O D U C T

M O N I T O R I N G U S I N G T H E

M O N I T O R I N G A N D C O N T R O L

A C C E L E R AT O R .

2


Table of Contents

Introduction ................................................................................................................... 5

Purpose of this Document .................................................................................................................................. 6

Enhanced Android Client .................................................................................................................................... 7

Applicable Product Versions ............................................................................................................................... 7

Terms of Use1 ..................................................................................................................................................... 9

Further Assistance .............................................................................................................................................. 9

Accelerator Component Overview ................................................................................ 10

Deployment ................................................................................................................. 11

Server Requirements ........................................................................................................................................ 11

Standard Basic Installation ............................................................................................................................... 12

Server Configuration using the Web Client ....................................................................................................... 14

1. Open the web client ......................................................................................................................... 14

2. Edit the container attributes ............................................................................................................ 14

3. Save the Current Configuration ........................................................................................................ 15

4. Restarting the Server ........................................................................................................................ 15

5. Disabling further changes. ................................................................................................................ 15

6. Re-enabling configuration editing .................................................................................................... 16

Monitoring Components............................................................................................... 17

Monitoring the Guidewire Server Availability .................................................................................................. 17

Server Availability Configuration ...................................................................................................................... 18

1. Select the checkGWServer flow ....................................................................................................... 18

2. Configure the GWCheckService node .............................................................................................. 18

3. Configure the AlertTarget node (optional) ....................................................................................... 18

4. Save and run the flow ....................................................................................................................... 19

5. Observe/Manage Alerts ................................................................................................................... 19

Monitoring the Message Backlog ..................................................................................................................... 20

Message Backlog Configuration ........................................................................................................................ 20

3


1. Select the monitorMessage flow ...................................................................................................... 20

2. Configure the GWMessageSource node .......................................................................................... 21

3. Configure the FileTarget (optional) .................................................................................................. 22


5. Download the metric data................................................................................................................ 22

Monitoring the Server JVM .............................................................................................................................. 23

Server JVM Monitoring Configuration .............................................................................................................. 23

1. Enable JMX ....................................................................................................................................... 23

2. Select the monitorJVM flow ............................................................................................................. 23

3. Configure the JMVMonitor Node ..................................................................................................... 24



Monitoring Event Activity................................................................................................................................. 25

Monitoring Event Activity Configurations ......................................................................................................... 25

1. Enable appropriate event rules ........................................................................................................ 25

2. Select the monitorGWEvents flow and start it ................................................................................. 25

3. Events can be monitored and archived. ........................................................................................... 26


Retrieving Monitoring Data Files ...................................................................................................................... 27

1. Pick the proper data file from your web client ................................................................................ 27

2. Open the file in excel ........................................................................................................................ 27

Guidewire Product Control ........................................................................................... 28

Control Capabilities .......................................................................................................................................... 28

Suspend Messaging using the GW Control Service ........................................................................................... 29

1. Select the stopGWMessaging flow ................................................................................................... 29

2. Configure the GWControlService node ............................................................................................ 30

3. Start the stopGWMessaging flow ..................................................................................................... 31

4. Suspend all messaging ...................................................................................................................... 31

Web Server Paths ......................................................................................................... 32

VDAB Reference Locations ............................................................................................ 33

4


Appendices .................................................................................................................. 34

Appendix A: Enabling JVM Monitoring ............................................................................................................. 34

Enabling JMX monitoring in an Application Server .................................................................................. 34

Appendix B: Event rule to capture business events .......................................................................................... 35

Configuration: Sending Events to a Local Monitoring Server .................................................................. 35

Configuration: Sending Events to a Remote Monitoring Server .............................................................. 36

Appendix C: Message Delegate Backlog Monitoring ......................................................................................... 37

Message Delegate Backlog Configuration ............................................................................................... 37

About Guidewire Software ........................................................................................... 38

5


Introduction The Guidewire monitoring and control accelerator provides components that can be assembled in different

ways to provide the following:

Accelerator Features Documentation Required Client

Performance and application health monitoring

Covered in the Accelerator Guide Web Client

Operational control of the Guidewire

application

VDAB Documentation and additional

sample flows

Android Client

Alerting and error intervention VDAB Documentation and additional

sample flows

Android Client

While this accelerator is anticipated to enhance the monitoring and control capabilities of any company

running Guidewire products, the capabilities should be integrated into an overall monitoring strategy.

This document provides the information to implement some standard monitoring flows but is not intended

to provide complete details regarding flow programming or all features of the underlying VDAB processing

engine.

6


Purpose of this Document This document provides an introduction of how to install and use the Guidewire monitoring and control

components.

It also provides detailed instruction for using the accelerator to do key types of monitoring.

Document

Focus This document serves as a guide to implementing some key guidewire

monitoring flows by adapting the provided sample flows. It is intended for

developers, architects and testing specialists that wish to supplement their

Guidewire monitoring with these key metrics. Samples are provided for the

following:

Monitoring Guidewire server accessibility

Monitoring Guidewire messaging backlogs

Monitoring Guidewire product JVM

Monitoring Guidewire event metrics

The sample monitoring flows included in the standard distribution of the accelerator simply need to be

configured and enabled.

Document

Limitations

While this document serves as a guide to implementing some key monitoring

flows covers only a subset of possible monitoring flows and is not intended to

support all possible uses of the accelerator components and the underlying

VDAB visual processing server. If you intend to do more than adapt the existing

monitoring flows, download the Android client and refer to the additional

tutorials on flow programming and alerting.

The following are not included in this document:

Descriptions of all configuration options for the sample monitoring

flows

Detailed information regarding using the full-featured Android client

Descriptions and samples for using other types of monitoring nodes

Visual scripting features of the processing engine

Detailed examples for using the Guidewire control features

Complete instructions for setting up automated performance

regression

Configuration details for different types of alerting

Details on persisting monitoring data on other databases (Oracle, SQL

Server and MySQL work with the processing engine but configuration

for these databases is not included in this document.)

For additional documentation and flow programming tutorials go to

http://www.vdabtec.com/vdab/tutorials

7


Enhanced Android Client While the GW Monitoring and Control Accelerator includes a web client which supports typical administrative

functions, full flow authoring features are only currently available using an Android Client. The standard

Android client can be downloaded at no cost from vdabtec.com. This Android client , which can be

downloaded from http://vdabtec.com/vdab/softare, can be run on an android device or on a windows device

using an Android emulator.

Web Client Android Client

Security Single security setting for all client users.

Server can be locked down by editing the configuration

Named users with specific roles on the server.

Typical Usage Administering and retrieving data from

existing monitoring flows

Full flow editing, programming and debugging.

Data Charting Displays only current live data Allows retrieving and displaying historical data

Obtaining the Client Included with the accelerator and is an integral part of the server

Download from

http://www.vdabtec.com/vdab/software

Applicable Product Versions While this accelerator is anticipated to work with all product versions since version 7, the accelerator been

tested with the indicated products and versions:

Product Component Tested Flows Tested Notes

ClaimCenter 8.04 GWCheckSource

GWMessageSource

MonitorJVMSource

GWActivityAgent

GWControlService

monitorGWService

monitorMessages

monitorJVM

monitorGWEvents

stopGWMessaging

ClaimCenter 8.05 GWCheckSource

GWMessageSource

MonitorJVMSource

GWActivityAgent

GWControlService

monitorGWService

monitorMessages

monitorJVM

monitorGWEvents

stopGWMessaging

Claim Center 9.03 GWCheckSource

GWMessageSource

MonitorJVMSource

GWActivityAgent

GWControlService

monitorGWService

monitorMessages

monitorJVM

monitorGWEvents

stopGWMessaging

The GWControlService is not yet working in V9.

8


PolicyCenter 8.04 GWCheckSource

GWMessageSource

MonitorJVMSource

GWActivityAgent

GWControlService

monitorGWService

monitorMessages

monitorJVM

monitorGWEvents

stopGWMessaging

9


Terms of Use1 We have made this document and accompanying accelerator files available to you as we thought that you

might find them useful. As such, they are provided to you "as is", which means that we do not offer you any

assurances with respect to them. You will be solely responsible for any changes made to your configuration

as a result of you downloading and implementing any of our materials.

You also understand that Guidewire owns the intellectual property rights to the specific components

documentation/file downloads we make available to you. You must not use them in any way that would

adversely affect our rights under applicable law. Please see the full terms of use1 for additional information.

Further Assistance This guide is intended to primarily support the enhanced Guidewire product monitoring using web

administration. For Guidewire product control and alerting you can consult additional documentation

regarding the VDAB processing server, download the enhance Android client or obtain assistance for your

deployment. Please contact your Guidewire or partner Implementation Manager to discuss options for

consulting assistance.

If you would like to provide us with feedback on this accelerator please post a suggestion through our

Customer Resource Portal, or alternatively post a comment directly on the accelerator.

1

https://guidewire.custhelp.com/app/resources/accelerator/accelerator_admin/action/download_file/panel_id/accelerators/file_id/14512039428/file_name/Guidewire+Accelerator+

Terms+of+Use.pdf

https://guidewire.hivelive.com/hives/b7ff2ec1f1/posts/create?type=216

10


Accelerator Component Overview This solution includes a standalone third-party monitoring server (VDAB

tm) and a large number of application moni-

toring components. Some standardized monitoring components, including the JVM Monitor, provide valuable information regarding the Guidewire Product. In addition to the standard monitoring components, the customized Guidewire monitoring and control components highlighted below, provide significant additional value when monitoring or controlling Guidewire products.

The key components used for monitoring and control are further described below:

Component Description

GW Check Source Checks to see whether the Guidewire service is available by accessing the web ping facility of the Guidewire product. Returns the status of the server. This can be enhanced with alerting.

Alerting features are not covered in this guide

GW Messaging

Source

The messaging node monitors the messaging backlog on the Guidewire Product and stores the data in a metric database.

JVM Monitor Source This standard monitoring component, reads key information from the product JVM including CPU and memory utilization.

GW Activity Agent

Event Stream Input

Supports the monitoring of business activities and sends this data directly to a standard event stream.

GW Product

VDAB Monitoring

Server

GW Control Service

GW Messaging

Source

GW Control Web Services

GW Activity Agent

GW

Database

JVM Monitor Source

Event Stream Input

GW Check

Source ping

JMX Android Client

Web Client

11


Deployment Server Requirements The Guidewire Monitoring and Control Accelerator can be installed on a) a separate server or b) directly on

the server that is running the Guidewire application.

Resource Recommendation*

Recommended

Memory

2 gigs – Unix

4 gigs - Windows

CPU 2 cores

Disk Space 10 gigs local disk

Software Java 1.7 or later

* While the accelerator can run on a smaller system, these resources are recommended

for Guidewire monitoring.

12


Standard Basic Installation The accelerator is provided as a zip file that simply needs to be unzipped to begin using the monitoring

server. Specific monitoring components require and some additional steps outlined below.

The Monitoring and Control Accelerator can be installed either a) directly on the system hosting your

Guidewire application or b) on an entirely different Windows or Unix system. Log monitoring and some other

features that work directly with the file system require installation directly on the server running the

Guidewire product.

The accelerator is installed by unzipping the accelerator zip file into the desired directory. The accelerator

creates a number of subdirectories and is preconfigured to support Guidewire product monitoring.

Since this standalone includes is a standalone application, the installation directory should not be under the

standard Guidewire installation subdirectory. (This could be C:\gwmonitor on Windows or

/var/lib/gwmonitor on Unix.)

Install Step Installation Details

Create a base

directory for

installation and

unzip the

accelerator

packages.

1. Create a base directory to contain the Monitoring Accelerator. (In this example we will use C:\gwmonitor)

2. Copy the accelerator zip (gwmonitor.zip) to a temporary director. 3. Unzip this file specifying the base directory you have chosen

Restart your

Guidewire

Product

1. Start or restart your Guidewire product.

Start the

GWMonitor

1. Go to the bin subdirectory (C:\gwmonitor\bin)

2. Run gwmonitor_start by clicking on it or running it from the command

line.

3. Open a web browser to http://localhost/vdab to view the monitoring

application

http://localhost/vdab

13


14


Server Configuration using the Web Client The server can be further configured using the web client or by directly editing the config.xml

file found in the config directory. (The Android Client can also be used for server configuration.)

While the server is preconfigured, editing the configuration using the admin screen will customize

the installation. Common customizations included:

Changing the security level of the web client to lock out further administrative changes

Changing the port of the web client to a port other than 80 (This is required on some Unix systems

when not running as root).

Renaming the processing container

1. Open the web client

Go to http://localhost/vdab to view the server administration screens. Click on the edit icon to edit

the container .

2. Edit the container attributes

The container attributes can be directly edited. For a description of individual attributes hover over the

attribute name.

Click submit to save the changes locally.


15


3. Save the Current Configuration

While changes to the container attributes are made after hitting submit, permanent changes to the

configuration require clicking the save icon which permanently saves the configuration changes.

4. Restarting the Server

Many changes to the server do not take effect until after it is restarted. After you have saved the changed

configuration, stop the server using the gwmonitor_stop script and restart after the system comes down.

5. Disabling further changes.

After the monitoring container is properly configured, disable further configuration changes using the web

client by setting the Security Class attribute to Standard. After saving this attribute change, the web client

can only be used to run the monitoring and control flows.

16


6. Re-enabling configuration editing

Once disabled, further edits can only be re-enabled by directly editing the config.xml. Open the

config.xml file in your preferred editor and change the Security Class attribute to Public. Restart the

server.

17


Monitoring Components

Many of the specialized Guidewire components

support enhanced monitoring.

This document provides complete information on

how to modify the sample monitoring flows to

perform this monitoring. All of these monitoring

flows write data to CSV file to facilitate later

analysis of the data.

All of these sample monitoring flows will work

remotely.

Monitoring the Guidewire Server Availability The GW Server monitor checks the accessibility to one or more Guidewire servers alerting when the system is

not accessible. While this sample does create an alert it does not describe how different alerts can be

managed. (See VDAB Tutorials and Documentation, http://vdabtec.com/vdab/tutorials, for more

information on alerts.)

Server Availability Monitoring

Sample Flow checkGWServer – Demonstrates monitoring the availability of a single Guidewire product using the GWCheckSource node. Availability status is written to a CSV file. An alert is generated when it is not accessible.

Special

Installation

NONE

Configuration You must edit the product and location of the Guidewire product in

the GWCheckService node.

You can edit the alert message in the AlertTarget node

18


Server Availability Configuration

1. Select the checkGWServer flow

Click on the checkGWServer flow to display the flow for monitoring the Guidewire server.

2. Configure the GWCheckService node

Click on the GWCheckService node to edit its attributes. Edit the product, host and port to match the

Guidewire product you are monitoring. Click submit to save the changes

3. Configure the AlertTarget node (optional)

Click on the AlertTarget node (labeled Alert) to modify the alert category, the alert message and other

properties of the alert.

19


4. Save and run the flow

Click first the save and then the run button on the monitoring flow.

5. Observe/Manage Alerts

If the Guidewire product is down, an alert will be generated and can be viewed on the monitor screen. Alerts

can also be configured to notify using email or XMPP. (Configuration requires the Android Client.)

20


Save and run the flow

Monitoring the Message Backlog The messaging system is critical to many integration and backlogs can indicate problems with the

downstream integrations or other performance issues. Monitoring the number of inflight and unsent

messages is essential.

The GWMessageSource node polls and records this information for standard Guidewire messaging at

selected intervals. (The GWMessageService node can be used to read this information at a single point in

time.) This node uses a DB query to obtain backlog information and requires an account with read only

access to the database. The query obtains information for all destinations and states in a single query and

requires a read only user login to the Guidewire product database.

While this sample flow does not include alerting, production monitoring should include the creation of alerts

whenever specific backlogs are exceeded.

Message Backlog

Sample Flow monitorMessages – Monitors all messaging destination and charts the messaging statistics using the GWMessageSource node. The messaging data is also written to a CSV file.

Special

Installation

A read only account is required for the Guidewire database

Configuration The database access information including the product, connect

string, user name and password needs to be configured for the

GWMessageSource node.

If needed, the tablespace can be defined.

Message Backlog Configuration The following procedure should be followed for monitoring standard messaging.

1. Select the monitorMessage flow

Select the monitorMessage flow from the main admin screen.

21


2. Configure the GWMessageSource node

The DatabaseType, DBDriver and ConnectURL needs to be entered for the Guidewire product database.

The User and Password are needed if the user must log in. (The password will not be saved directly but will

be encrypted prior to saving the flow information.)

The PollRate (in seconds) determines how often the database is queried and data saved to the database.

Hit the submit button when complete.

Special Connection String for H2

If using a local H2 database, please note the following special instructions.

Special

Instructions for

the H2 Database

If configuring the accelerator for a local H2 database, the AUTO_SERVER=TRUE

property needs to be set in the ConnectURL property which is the connection string.

This must be set in both the accelerator and the product database connection

string.

For the accelerator the connection string edited in the above web form or directly

in the xml defining the follow. For the Guidewire product set this in the database-

config.xml.

22


3. Configure the FileTarget (optional)

The message backlog is save to a data file. If you wish to customize the filename and the directory where the

data files are written, click on the FileTarget node and edit its properties.


After editing all nodes that need to be customized, click on the save icon to save the changes to the flow.

Click the run icon located (next to the save icon) to run the edited flow.

5. Download the metric data

See Retrieving Monitoring Data Files in this section.

23


Monitoring the Server JVM Monitoring JVM memory and CPU utilization at the JVM level provides significantly more insight then

monitoring the same metrics at operating system level. The actual resource cost can be calculated for

different integrations or business flows. The JVM Monitor Source uses JMX to communicate with the JVM and

return these values.

Server JVM Monitoring

Sample Flow monitorJVM– Using JMX with the JVMMonitorSource node this flow mon-itors the memory and CPU consumption in the JVM and charts the results. The data is also written to a CSV file.

Special

Installation

Enable JMX monitoring in the product JVM.

Set the appropriate JVM properties to enable JMX Monitoring. (See

Appendix A. for details)

Configuration The JMX connection information which include the domain, port and

security information must be configured in the JVMMonitorSource.

Server JVM Monitoring Configuration

1. Enable JMX

See Appendix A for details on enabling JMX monitoring on your Guidewire product. The specific approach will

depend on Application Server you are using.

2. Select the monitorJVM flow

Select the monitorJVM sample flow from the main admin screen.

24


3. Configure the JMVMonitor Node

The JVMMonitor node requires the configuration of the domain and port of the JMX server on your

Guidewire product. The Domain is the IP or server name the server hosting the product. The Port is the port

specified when you enabled JMX monitoring (See Appendix A.). The Poll Rate (in Seconds) can also be set.

Use a higher poll rate (60 secs or more) if you are concerned about the load on the server. Use a lower poll

rate if you are using the data for modeling the CPU usage of a single application action.

Click Submit to save the changes.


After editing all nodes that need to be customized, click on the save icon to save the changes to the flow.

Click the run icon located (next to the save icon) to run the edited flow.

25




Monitoring Event Activity Event activity monitoring accumulates statistics for all of the business and technical events that go to the

event rules. It can provide detailed insight into both the technical and business activity of the system.

Event Activity Monitoring

Sample Flow monitorGWEvents – Monitor all events sending the information to both a chart and a CSV file. This flow features the EventStreamInput node that ac-cumulates the event information received from the GWActivityAgent class invoked from the Guidewire product event rules.

Special

Installation

For V8 Products, install the GW Version 8 Agent jars. Go to the accelerator pkgs/GWInstall/V8/lib subdirectory

(c:\gwmonitor\pkgs\gwinstall\V8\lib by default). Copy the two jar files located here (GWActivityAgent.jar and VDAB-Core.jar) to the modules/configuration/plugins/shared/basic/lib directory located in the Guidewire product installation directories.

For V9 Products, install the GW Version 9 Agent jars Go to the accelerator pkgs/GWInstall/V9/lib subdirectory

(c:\gwmonitor\pkgs\gwinstall\V9\lib by default). Copy the two jar files located here (GWActivityAgent.jar and VDAB-Core.jar) to the modules/configuration/plugins/shared/basic/lib directory located in the Guidewire product installation directories.

Add an event rule to capturing business events.

Create an event rule to capture this data (See Appendix B. for details)

Configuration Modify the event rule to get the desired sampling rate

Monitoring Event Activity Configurations

1. Enable appropriate event rules

See Appendix B for details regarding setting up appropriate event rules..

2. Select the monitorGWEvents flow and start it

Click on the monitorGWEvents flow to select the flow. Hit the run button to start the flow.

26


3. Events can be monitored and archived.

The monitorGWEvents screen shows the events being processed. These are also being archived.



27


Retrieving Monitoring Data Files All of the sample monitoring flows write metric data to a file and this data can be downloaded for further

analysis. If desired, the data can be written to a different file location by editing the FileTarget node in the

respective flow.

1. Pick the proper data file from your web client

The metric data can be downloaded by selecting the proper file from those listed on the server.

(http://localhost/data_files).

2. Open the file in excel

These CSV files analyzed and data plotted once they are opened with excel.

http://localhost/data_files

28


Guidewire Product Control

The Guidewire Control Service allows

flexible control of Guidewire products

include control of the following features

While a simple demonstration control flow is

provided, complete configuration of this

component will require using the VDAB

Android Client.

Control Capabilities The GW Control Service can perform all of the operations on the GW product found in the table below. This

document is not intended to cover all of these capabilities and the VDAB Android Client is required to

configure most of these features.

These control features can by extended by creating Gosu classes. Use the existing Gosu code as a guide.

Control Area Options Description

Messaging RestartEngine Restarts the messaging engine.

Suspend Suspends specified messaging destinations.

Resume Resumes specified messaging destinations.

SuspendAll Suspends all messaging destinations

Logging SetLogLevel

Sets the log level to a specific level for specified categories of logging.

LogInfo Logs and informational message

LogError Logs an error message

ResetLogLevel Resets the log level to the default

Profiler Disable Disables profiling for a specified component

Enable Enables profiling for a specified component

DisableAll Disables all profiling

Batch Processes Start

Starts a specified batch process

Stop Stops a specified batch process

29


Suspend Messaging using the GW Control Service While the use of all of the features of the GW Control Service requires the use of the Android Client, a sample

flow is provided to illustrate the how these control services can be exposed and used by the web client. This

sample flow suspends all messaging.

As the GWControlService node communicates with the product using specific web services, the Gosu code for

the web services needs to be deployed. Copy the Gosu web service code to the product gsrc directory. (See the

Special Installation section in the table below.)

Suspend Messaging

Sample Flows stopGWMessaging – Uses the GWControlService node to suspend mes-saging

Special

Installation

For V8 Products, install the GW V8 Control Web Services Go to the accelerator pkgs/GWInstall/V8/gsrc subdirectory

(c:\gwmonitor\pkgs\GWinstall\V8\gsrc by default on Windows). Copy the entire vdab directory found here into the

modules/configuration/gosu directory of your Guidewire product

install.

For V9 Products, install the GW V9 Control Web Services Go to the accelerator pkgs/GWInstall/V9/gsrc subdirectory

(c:\gwmonitor\pkgs\GWinstall\V9\gsrc by default on Windows).

Copy the entire vdab directory found here into the

modules/configuration/gosu directory of your Guidewire product

install.

Exit and restart studio

Configuration You must edit the product, port and location of the Guidewire product in

the GWControlService node.

1. Select the stopGWMessaging flow

Click on the stopGWMessaging flow to select the flow.

30


2. Configure the GWControlService node

Click on the GWControService node to edit. Point to the desired GW product by setting the GW Product, Host

and Port of the server. It is not recommended that you edit the ControlArea and Command using the Web

Client. (Use the Android Client to select and configure other control operations.)

31


3. Start the stopGWMessaging flow

Start the flow by clicking on the run button

4. Suspend all messaging

Click on the suspend button to stop all messaging.

Verify that all queues are suspended on the Message Queue Screen

32


Web Server Paths The Guidewire Monitoring and Control accelerator can be managed using web pages.

By default these pages are located at http://localhost:80/vdab but server configuration can be used to

change the port number for the web server.

The paths in the table provide standard locations for key features.

Web Url Description Sample screen

<server_url>/vdab This displays all the monitoring flows that are loaded. Flows that are running are indicated by a green indicator on the flow icon.

<server_url>/vdab/docs_node Displays a list of the

available

processing nodes

that are available.

(You will need the

Android Client and

additional VDAB

documentation to

build flows with

these additional

nodes)

<server_url>/data_files Displays various data and other files that are available for download.


33


VDAB Reference Locations

Many of the capabilities that can be provided by the accelerator components require the VDAB Android

Client and additional reference information.

These can be found in the web locations indicated below:

Reference VDAB URL Description

Software Downloads http://vdabtec.com/vdab/software Location allowing the download of the standard Android client and server software. Additional installation information is also found here.

Tutorials http://vdabtec.com/vdab/tutorials Location of reference tutorials providing an overview

of visual dataflow programming and detailed

information on specific topics including alerting,

performance regression and database nodes.

Frequently Asked

Questions

http://vdabtec.com/vdab/faq Frequently asked question describing the VDAB Client

and Server.

34


Appendices

Appendix A: Enabling JVM Monitoring The JVMMonitor source node provides critical monitoring capabilities for all Guidewire products. CPU and

memory measurements provided by it are much more valuable than those metrics for the entire system

because they isolated the resources used just by the product.

In addition to configuring this node, JMX monitoring must be enabled for the Guidewire product. The

approach to doing this depends on whether you are using are running an application server or are running in

Enabling JMX monitoring in an Application Server

Each application server has different ways to set JVM arguments in the application server. Please consult

your application server manual to define the following JVM arguments. Authenticate can be set to false or

true. If authentication is set to true, which is recommended in most situations, you will need to configure the

user name and password in the plugin.

JVM arguments to enable JMX monitoring

-Dcom.sun.management.jmxremote

-Dcom.sun.management.jmxremote.port=7777

-Dcom.sun.management.jmxremote.ssl=false

-Dcom.sun.management.jmxremote.authenticate=false

Enabling JMX monitoring in Studio for QuickStart Development

When doing development in studio the JVM arguments can be set by selecting the run/edit configuration

option. Enter the same JMX options in the VM options field :

These can be cut and pasted from the above table. Set the port to an available port and make sure that port

is specified in the JVMMonitorSource node.

35


Appendix B: Event rule to capture business events The GWActivityAgent.jar and VDABCore.jar need to be placed in the plugins/shared/basic/lib

before creating the event rules shown below.

Code is added in the Event Rules to allow capturing of business events.

This logic can be added to a rule for the Console destination (68) or any other destination you wish to

monitor.

Configuration: Sending Events to a Local Monitoring Server

This code shown below will send activity summary information to the Dataflow Server located on the local

server (localhost) at the standard dataflow server port (1775). The data will be sent every 5 minutes (300

secs.).

var status = GWActivityAgent.getAgentStatus() if (status == GWActivityAgent.UNLOADED){ var agent = new GWActivityAgent() agent.setVDABLocation("localhost") agent.setReportInterval(300) agent.startAgent() agent.sendZeroCounts() } if (status == GWActivityAgent.RUNNING) { GWActivityAgent.pushActivityData(messageContext.EventNam

e) }

36


Configuration: Sending Events to a Remote Monitoring Server

The data can be sent to a remote Dataflow Server by changing the parameter setting the server location

which container the IP or server and the port if it is anything but the standard port (1775). The data source

can be identified by creating the GWActivityAgent with a label identifying the server. The events from this

server will be labeled as “pc_server4” and will be sent to a VDAB server at the domain

dataserver.mycompany.com listening at port 41005.

var status = GWActivityAgent.getAgentStatus() if (status == GWActivityAgent.UNLOADED){ var agent = new GWActivityAgent("pc_server4") agent.setVDABLocation("dataserver.mycompany.com:41005")

agent.setReportInterval(300) agent.startAgent() agent.sendZeroCounts() } if (status == GWActivityAgent.RUNNING) { GWActivityAgent.pushActivityData(messageContext.EventNam

e) }

37


Appendix C: Message Delegate Backlog Monitoring For Guidewire customers using the Message Delegate accelerator, the GWMsgDelegateSource is available for

monitoring the backlog of delegate work items. (The GWMsgDelegateService node is used to read this

information one time.)

A DB query is used to obtain backlog information and requires an account with read only access to the

database. The query obtains information for all destinations and states in a single query and requires a read

only user login to the Guidewire product database.

Message Backlog

Sample Flow monitorDelegate – Monitors all message delegate work items using the GWMsgDelegateSource node. The data is also charted and written to a CSV file.

Special

Installation

A readonly account is required for the Guidewire database

Configuration The database access information including the connect string, user

name and password needs to be configured for the

GWMessageSource node

Message Delegate Backlog Configuration

The Message Delegate monitor is setup using the same approach as the Message Backlog monitoring. See the

directions in that section to modify the monitorDelegate sample flow to work in your environment.

38


About Guidewire Software Guidewire delivers the software that Property/Casualty (P/C) insurers need to adapt and succeed in a time of

rapid industry change. We combine three elements – core processing, data and analytics, and digital

engagement – into a technology platform that enhances insurers’ ability to engage and empower their

customers and employees. More than 200 P/C insurers around the world have selected Guidewire. For more

information, please visit www.guidewire.com and follow us on twitter: @Guidewire_PandC.

© 2017 Guidewire Software, Inc. All rights reserved. Guidewire, Guidewire Software, Guidewire ClaimCenter, Guidewire PolicyCenter, Guidewire BillingCenter, Guidewire InsuranceSuite, Guidewire Live, Deliver Insurance Your Way, and the Guidewire logo are trademarks or registered trademarks of Guidewire Software, Inc. in the United States and/or other countries.

http://www.guidewire.com/

Monitoring and Control Accelerator · The Guidewire Monitoring and Control Accelerator can be...

Documents

Transcript of Monitoring and Control Accelerator · The Guidewire Monitoring and Control Accelerator can be...