WebInterfaceReference

stockiNail edited this page May 24, 2017 · 4 revisions

JEM, the BEE Web Interface

JEM provide a web site that is it's main interface. This can be used to:

  • what and how jobs are working on nodes
  • act on jobs and nodes
  • how nodes are working
  • manage roles and resources
  • explore the JEM file system
  • see health status of JEM cluster

Login

To view the web site, you need to open a web browser and go to JEM web site. Ask your system administrator if you don't know what it is.

Web application access is protected by username and password. This is the first page with login form:

http://www.pepstock.org/wiki/webui/Login-form.png

If wrong username and/or password is provided, a failed login message appears:

http://www.pepstock.org/wiki/webui/Login-error.png

The web UI is available if and only if the JEM environment is running. If there is not any node active, JEM is not able to retrieve the necessary user rights and will not allow login. The web UI will be not available and the following message will appear:

http://www.pepstock.org/wiki/webui/Login-group-error.png

Note: the authentication and authorization engine must be configured, based on environment where JEM is installed.

General layout

After logon, you will see the JEM home page:

http://www.pepstock.org/wiki/webui/Home.png

  1. This area displays a brief overview of the JEM environment, like the name, the jobs, the nodes count and the uptime of the environment
  2. Contains the current logged user details
  3. Logoff button, this terminate the session and bring you back to login page
  4. Main tab panel: from this you can access to all JEM functions (note: the number of available panels depends on user rights, see Roles section below)
  5. Messages history (infos, errors, ...). See Notifications Area below.
  6. About & Licenses: displays the credits and the currently installed licenses

The rest of space is used by panels to display their content.

Notifications area

The blue highlighted area of above image show where notification messages appears.

Examples:

http://www.pepstock.org/wiki/webui/Input-submit-confirmation.png http://www.pepstock.org/wiki/webui/Input-check-warning.png

This kind of messages disappears after some seconds, but if you miss something or need to review them just click on the http://www.pepstock.org/wiki/webui/Messages-history-icon.png icon to open messages history: http://www.pepstock.org/wiki/webui/Messages-history-detail.png

Search and Actions

In some JEM pages you may encounter a searcher, usually with a table and some action buttons, like this (taken from the Input view):

http://www.pepstock.org/wiki/webui/Searcher-Action-Table.png

  1. Search bar (with Search button) 1b. History: click here if you want to browse your past search
  2. Table headers. You can sort table content by the colum value (click, re-click to reverse order) or set a filter on it (see Search bar / Table headers below)
  3. Action buttons. Based on the currently active view, you can do some actions on one or more elements in table.

Search bar / Table headers

To view all entities related to page you are in, simply leave the search box empty then click on Search button.

If you want to search something or filter results, you can:

  • write free text into search box, this usually filter entities by name (or by most significant attribute of entities you're viewing)

http://www.pepstock.org/wiki/webui/Searcher-free-text.png

  • mouse over a table header, if the search can be filtered by the field a popup prompt you for a value. Type what you need, then strike Enter key to put it in the search bar (with right syntax), or Esc key if you want to closes the prompt

http://www.pepstock.org/wiki/webui/Searcher-header.png

You can use both free text edit and filter-by-header: the search bar will change the query string according

http://www.pepstock.org/wiki/webui/Searcher-search-bar.png

Notes:

  • free text always filter by name, or by main entity attribute
  • wildcard * may be used, but it's not necessary (if it is, you'll see a tooltip next to search bar)
  • you can filter by multiple fields at once, in AND condition (look at the following example)

Example: this search will return all jobs that:

  1. have return code 12
  2. were submitted by jemuser
  3. job name contains CH chars (you can also type name:CH, it's not mandatory because name is the default search field for job entities)

http://www.pepstock.org/wiki/webui/Searcher-search-bar-full.png

Editable properties

In some cases, users are allowed to edit entities properties at runtime, directly from web interface. Just click on property you want edit and, if permitted, a text box will be presented in which you can type the new value (strike Enter key to confirm the change):

http://www.pepstock.org/wiki/webui/Editable-cell.png

Actions

You can do some kind of actions in (selected) entities of current view clicking on buttons in the upper-right corner.

Each action is explained by the button label and by a tooltip which appears on mouse over.

http://www.pepstock.org/wiki/webui/Button-tooltip.png

Actions will be applied to all selected (checked) entities:

http://www.pepstock.org/wiki/webui/Input-check.png

Views

The UI offer different views:

http://www.pepstock.org/wiki/webui/Views-tabpanel.png

Of course, not all user can see all of these because they are based on user's authorization.

Job life-cycle views

Jobs views can show all jobs according to their status, as input, running, output and routing.

In each view you can search for jobs and see the general information, JCL and output. You can perform some actions on it, like Cancel or Hold.

When you see the result of searching, you can click on job name and see all its details:

http://www.pepstock.org/wiki/webui/Jobs-results.png

You can see general information about job execution:

http://www.pepstock.org/wiki/webui/Jobs-general-info.png

You can also see, modify and (re)submit the JCL used by job to be executed:

http://www.pepstock.org/wiki/webui/Jobs-jcl.png

And you can see both JEM log and standard error and output of job, directly from web interface.

If job has used SYSOUT data description, you can see the data from this interface. Here is a sample with JEM log (produced by JEM with information about step executions):

http://www.pepstock.org/wiki/webui/Jobs-JEM-log.png

Here is a sample standard error and output of job:

http://www.pepstock.org/wiki/webui/Jobs-output.png

Input view

In this view you can see all jobs in input queue, waiting for execution.

The jobs remains in input queue for any of these reasons:

  • Is on Hold
  • Needs a domain that no node can serve
  • Needs one or more affinities that no node have at this moment
  • Needs an amount of memory that no node can offer at this time
  • No node is available because all are in Active status, so are executing other jobs

After searching of jobs, you can see the list of jobs as following:

http://www.pepstock.org/wiki/webui/Input-list.png

In this view, you can see the following attributes of jobs in input queue:

  • Name: job name
  • Type: JCL type. JEM can manage more than one JCL. In the example is Ant
  • User: user who submitted the job (or the surrogate one)
  • Environment: name of JEM group (always the same in this queue) *
  • Domain: domain that job needs to be executed *
  • Affinity: affinities that job needs to be executed *
  • Submitted time: time-stamp when the job has been submitted
  • Priority: priority used in input queue and use from nodes to execute jobs in the correct order *
  • Memory: memory that job needs to be executed, indicated by submitter *
  • Hold: if true, job stay in queue and no node will execute it. To change this condition, you can release it using the Release action

* = editable property: just click over it!

Each row identify a job and one or more jobs can be checked (selected) to perform actions on a bounce of them.

The available actions in Input queue are:

http://www.pepstock.org/wiki/webui/Input-actions.png

Clicking one of these buttons, you can modify the selected jobs status:

  • Purge, remove the job from input queue. No execution will be performed and the job will be moved in output queue
  • Hold, mark the job on hold, avoiding its execution and maintaining it in input queue until released
  • Release, remove the hold status so that job can be executed

Before purging, you must confirm the action:

http://www.pepstock.org/wiki/webui/Input-purge-confirm.png

An additional action is also available:

  • Submit, you can submit jobs uploading the JCLs directly from web browser
Submitting jobs

In the Input panel, you could also find an action to submit jobs by uploading JCLs. The job will use the User Id and the Organizational Unit of the user that is logged in.

Clicking on Submit button, a popup will appear and let you drag & drop JCLs.

http://www.pepstock.org/wiki/webui/Input-multisubmit.png

Once file are dropped in the highlighted area, the upload begins. Overall progress and single file progress are displayed.

A legacy submitter which let you upload one JCL at a time is also available to maintain compatibility with old browser:

http://www.pepstock.org/wiki/webui/Input-legacysubmit.png

Click Submit button and you will be notified if everything has gone well or if an error occurs:

http://www.pepstock.org/wiki/webui/Input-submit-confirmation.png

The multi file drag & drop submitter is not proposed if JEM detect that the web browser you're using doesn't support Ajax upload.

Running view

In this view you can see all jobs in execution inside the JEM environment. After search, you can see the list of currently running jobs as following:

http://www.pepstock.org/wiki/webui/Running-list.png

Jobs attributes available in this view are:

  • Name: job name
  • Type: JCL type. JEM can manage more than one JCL. In the example is ANT
  • User: user who submitted the job (or the surrogate one)
  • Step: job step name currently in execution
  • Domain: the domain that job is executing
  • Affinity: the affinities that job needs to be executed
  • Running time: elapsed time from when the job is in execution
  • Memory: memory that job needed to be executed (specified by submitter)
  • Member: JEM node (in ip:port format) where the job is in execution

All jobs can be canceled. Before cancel, a confirmation panel appears and you must confirm the action. After canceling, the job will move in output queue.

http://www.pepstock.org/wiki/webui/warning.png WARNING: cancel a job execution mean that you kill job process! Pay attention about the files and the other resources used by killed job during execution because they could be corrupted.

Output view

This view show you the ended jobs. These jobs stay in output queue till one of following events will occurs:

  • Manually purged
  • Archiving process (not implemented yet)

After searching of jobs, you can see the list of jobs as following:

http://www.pepstock.org/wiki/webui/Output-list.png

The following attributes are available for jobs in output queue:

  • Name: job name
  • Type: JCL type
  • User: user who submitted the job (or the surrogate one)
  • Environment: name of JEM group (always the same in this queue)
  • Domain: domain that job needed to be executed
  • Affinity: affinities that job needed to be executed
  • Ended time: time-stamp when the job ended
  • Return code: exit code of job. If not 0 (zero), ended with an exception
  • Hold: if true, the job will stay in queue. Release it to allow the job to be removed from the list
  • Member: JEM node (in ip:port format) where the job was executed

All jobs can be checked to perform some actions on them. Here are the available actions:

http://www.pepstock.org/wiki/webui/Output-actions.png

Performing one of these actions, you can:

  • Purge, remove the job from output queue (except those on hold)
  • Hold, set the job "stocky" so archiving process can't remove it
  • Release, remove the hold status so that job can be removed by archiving process

Status view

In this view you can search for a job for its id or name on all queues (input, running, output, routing). No pattern is allowed. This view is very helpful to search for a job which you do not know its status.

After search, you can see on what queues its instances are, as following:

http://www.pepstock.org/wiki/webui/Status.png

No action is allowed on this view and you can only inspect the job.

Nodes view

Nodes view can show all nodes (except web ones) of JEM cluster and their status.

After searching, the node list is presented as following:

http://www.pepstock.org/wiki/webui/Nodes-list.png

Nodes can have the following attributes:

  • Name: node name, in ip:port format
  • Hostname: host name of machine on which the node is running
  • Domain: domain that node can serve *
  • Static Affinities: affinities that nodes can serve, fixed using the JEM node configuration file *
  • Dynamic Affinities: affinities that nodes can serve, may vary in time, by an affinity loader
  • Status: node status
  • OS: operating system where the node is running
  • Memory: amount of memory used to start new jobs **
  • Parallel jobs: number of jobs that JEM node is able execute at the same time **
  • Current Job: name of job which is currently running on node or the number of current executed jobs if the parallel jobs is set greater than 1. On mousing over, you see the list of running jobs by a popup view.

* = editable property: just click over it!

** = editable property, but a defined affinity loader could override this setting

Affinity loader

Nodes has some properties, called affinities. Several of these property values are computed at runtime, by running a script.

To edit a Groovy or Javascript affinity loader script, you should go to administration view, edit the script and change:

JavaScript

/**
 * Sets maximum number of parallel jobs
 */
RESULT.setParallelJobs(1);

Groovy

/**
 * Sets maximum number of parallel jobs
 */
RESULT.parallelJobs = 1; 

If an Affinity loader is set, it periodically may change the parallel jobs and memory values, overriding the updates done by user interface.

http://www.pepstock.org/wiki/webui/warning.png To completely avoid that policies overrides the value set directly from user interface, change the policy setting to a value less than 0 for parallelJobs and/or memory.

Node details

You can click on node name to see all details of nodes:

http://www.pepstock.org/wiki/webui/Node-general-info.png

You can also see system information:

http://www.pepstock.org/wiki/webui/Node-system-info.png

All nodes can be checked to perform some actions on them.

http://www.pepstock.org/wiki/webui/Nodes-actions.png

Performing one of these actions, you can:

  • Start, change the status of node from Drained to Active (if Input queue contains suitable jobs) or Inactive (if no suitable jobs found)
  • Drain, change the status of node from Active (or Inactive) to Drained, so the node terminates the current job execution, then will stop and no longer execute jobs

Swarm view

Swarm view can show the nodes of a particular JEM group that is different from the one you're logged in, but it's used by nodes from other different environments to exchange data.

The typical Swarm use case is the job routing. As an example, a job for Env-1 can be submitted to Env-2. This job, if the swarm is used between Env-1 and Env-2 will be routed to Env-2. Swarm act as a bridge between JEM environments.

An Env-1 node can route an Env-2 job to it's enviroment if:

  • Swarm is active on Env-1 with Smarm-0 group with swarm0password
  • Swarm is active on Env-2 with Smarm-0 group with swarm0password
  • Env-2 Swarm-enabled node needs the IP address of Env-1 node specified in configuration (see below)

In this situation a job with target environment Env-2 can be submitted to Env-1 and this will route it to Env-2 automatically.

In this view you can see the following node attributes:

  • Name: node name, in ip:port format
  • Hostname: host name of machine where the node is running
  • Environment: the environment name in which this node belongs
  • Status: node status
  • OS: operating system where the node is running

As in Nodes view, you can search for nodes by Name or other fields (wildcard/empty search supported).

The main indicator of Swarm status is the following, located on top-right corner of the view:

http://www.pepstock.org/wiki/webui/Swarm-status.png

You can also do the following actions:

http://www.pepstock.org/wiki/webui/Swarm-buttons.png

  • Start, simple enable this node to access Swarm group
  • Drain, brings out the node from the Swarm group
  • Edit Config, configure the Swarm group for this node

Swarm configuration needs some information about the environment:

http://www.pepstock.org/wiki/webui/Swarm-config.png

General configuration tab needs the following information:

  • Enabled, a flag that specify if Swarm is enabled or not
  • Group name, the name of the Swarm group you want this node will be a member
  • (Confirmed) Group password, the password of the Swarm group (must be the same on all web nodes you want be part of same Swarm group)
  • Port, the starting port value of the Swarm group. It's auto-increment
  • Network interface, an IP address that specify the network interface used for Swarm group (f.e. 10.182.5.*)

The Swarm group does not use multicast to discover other members, you must specify the other machines by it's IP address on Members configuration tab:

http://www.pepstock.org/wiki/webui/Swarm-config2.png

You have to:

  • type an IP address of a JEM node
  • click Add

You can remove a previously authorized IP address by clicking on it and then on Remove button.

http://www.pepstock.org/wiki/webui/Swarm-config3.png

Remember to save configuration: click Save button on bottom left corner.

Roles view

Roles views can show all roles and their defined permissions and users of JEM cluster. Out-of-the-box JEM creates 4 un-removable roles:

  • administrator, with all permissions and you can only add or remove users
  • grantor, with all permissions to manage roles
  • operator, with all permissions to monitor
  • developer, with permission to partially use JEM

With this view you can see all authorizations, create and clone new roles and assigning them to users. Changes will became effective after save.

You can search a set of roles and perform some actions on that, like clone, remove or create a new one.

To search roles by their names, you can leave the field empty (or you can put a * wildcard):

http://www.pepstock.org/wiki/webui/Roles-search.png

When you can see the result of searching, you can click on role name and see all authorizations. The following sample shows the users assigned to administrator role:

http://www.pepstock.org/wiki/webui/Role-admin-info.png

When you create a new role, you should decide all authorizations to assign. First authorization tab is what views and actions to authorize on web interface the users, grouped by type:

http://www.pepstock.org/wiki/webui/Role-new-views.png

Be careful that the authorization is a regular expression.

As a facility, the first element of all authorization groups is All (no need to flag every single permission).

You can choose what search the users can perform because not all users can see all job execution. The same for nodes:

http://www.pepstock.org/wiki/webui/Role-new-searches.png

Be carefully that the authorization is a regular expression.

Going on job execution, you can also define who can use the resources in JCLs:

http://www.pepstock.org/wiki/webui/Role-new-datasources.png

Be carefully that the authorization is a regular expression.

To address the right resource, remember to indicate the kind as well, in the format [type].[name]. For a complete list of supported resources, see section Resources below.

The authorization on files must defined here as well:

http://www.pepstock.org/wiki/webui/Role-new-files.png

Be carefully that the authorization is a regular expression. You can decide which kind of access you want to authorized, on the data path. This permissions are not used to access to other GFS paths (i.e. library). To grant the access to other GFS paths, please use Administration GFS permissions. The access could be:

  • Read, for all files that job can read
  • Write, for all files that job can write
  • Execute, for all files that a job can execute. This executable module can be located everywhere, not only in data path.

You can also defined if a role can use another user to submit jobs (the surrogate user).

http://www.pepstock.org/wiki/webui/Role-new-surrogate.png

Also a section is provided for special permissions:

http://www.pepstock.org/wiki/webui/Role-new-advanced.png

The panel allows to add or remove users or organizational units or wildcards of either to a role.

http://www.pepstock.org/wiki/webui/Role-new-users.png

After search, you can see the list of roles as following:

http://www.pepstock.org/wiki/webui/Roles-list.png

The following attributes of roles are available:

  • Name: role name, unique value in whole JEM cluster
  • Removable: true if role is a custom one and not out-of-the-box ones and you can remove it, false otherwise
  • Permissions: list of permissions of role
  • Users: list of users assigned to role
  • Modified: date and time of last modify
  • Modified by: user that last modify the role

All roles can be checked to perform some actions on them. To do that, you must be authorized.

Here are the available actions:

http://www.pepstock.org/wiki/webui/Roles-actions.png

Performing one of these actions, you can:

  • New, add a new custom role. A popup will appear
  • Remove, remove a existing role, only if the role has removable to true. For this action, a confirmation popup will appear
  • Clone, clone a existing role and prompt a new name. Role administrator is not clonable

Resources view

Resources view can show all common resources that jobs can see and use during their execution.

In this view you can see all common resources of JEM cluster.

You can manage from this interface all resources, defined as described in resources section. The name of these resources (unique key of a Resource) is very important because this name must be used inside of JCL to get the resource by JNDI, Java Naming Directory Interface.

The resources must be only used by java programs.

With this view, you can see all defined resources, create and clone new ones. Every change is working after save.

You can search a set of resources and perform some actions that, like clone, remove or create a new one.

To search by resource names, you can leave it empty (or put a wildcard):

http://www.pepstock.org/wiki/webui/Resources-search.png

After searching, you can see the list of resources as following:

http://www.pepstock.org/wiki/webui/Resources-list.png

When you can see the result of searching, you can click on resource name and see the details:

http://www.pepstock.org/wiki/webui/Resource-inspect.png

When you create a new resource, you have to decide what type of resource you want create:

http://www.pepstock.org/wiki/custom-resources/InstanceNameAndType.png

Each resource type has its own attributes to be defined (descriptions are on its panel), as defined in XML template.

In this view, you can see the following attributes of resources:

  • Name: resource name, unique value in whole JEM cluster
  • Type: type of resource
  • Properties: list of properties that define the resource

All resources can be checked to perform some actions on them (if authorized).

Here are the available actions:

http://www.pepstock.org/wiki/webui/Resources-actions.png

Performing one of these actions, you can:

  • New, add a new resource. A popup will appear
  • Remove, remove a existing resource. For this action, a confirmation popup will appear
  • Clone, clone a existing resource, you only need to choose a new unique name

Explorer view

Explorer view let you to browse the directories of the JEM Global File System directly from the web browser.

The directories available for browsing are:

  • Data, contains the data files
  • Library, contains the libraries files
  • Sources, contains the source code files
  • Class, contains the class files
  • Binary, contains the binary files

http://www.pepstock.org/wiki/webui/Explorer-main.png

  1. Main directory selector
  2. Path searcher (and button), for manual input
  3. Current directory, with clickable Home and path tokens (for a faster navigation)
  4. List area, where all files in current directory are listed

You can click on table headers (Name, Size, Last modified) to sort the list in desired order.

In Data directory, you can also view the file content:

http://www.pepstock.org/wiki/webui/Explorer-file_detail.png

Administration view

This is the area where you can manage JEM. Usually regular users doesn't see this because it's only for administration purpose.

If you think you need to go here and have no access rights, please contact your system administrator.

The administration section is divided into these subsection:

http://www.pepstock.org/wiki/webui/Admin-main.png

  • Cluster, where you can see the cluster data and statistics, for jobs, nodes, memory, resources and so on
  • Nodes, this subsection shows the node configuration, let you to send command and see system and queue status
  • Queues, give you an overview of JEM queue sizes and some statistics
  • Security, manage all security things, like certificates management and encryption utility

Cluster administration

  • Configuration, where you can see and manage cluster configuration
  • Job Workload, where you can see workload statistics
  • GFS usage, where you can see global file system usage
  • Resource contention, if GRS is configured, you can see the current contentions among running jobs in the cluster
  • Redo statements, where you can see the complete list of statements done in cluster but not store in database for being persistent
Configuration

In this section you can edit the two main JEM configuration file directly from web interface, with a powerful, simple and self-explaining editor. Every change on these configuration file will be used only when the nodes will be restarted.

Environment configuration file:

http://www.pepstock.org/wiki/webui/Admin-Cluster-Configuration-1.png

Hazelcast configuration file:

http://www.pepstock.org/wiki/webui/Admin-Cluster-Configuration-2.png

Jobs Workload

This section is designed to have information about job state in time, on a per-minute and per-node basis.

http://www.pepstock.org/wiki/webui/Admin-Cluster-JobsWorkload.png

As you can see, a graph show the number of submitted jobs (and JCLs checked) over time.

At bottom, the list show the re-partition of them for each node.

If you click on node name, you can see the details for it:

http://www.pepstock.org/wiki/webui/Admin-Cluster-JobsWorkload_detail.png

Note that a Back button is present in upper right corner, to return to cluster overview.

GFS usage

This view shows the current JEM Global File System usage data, at the current time and over time, on a per-minute basis.

http://www.pepstock.org/wiki/webui/Admin-Cluster-GFS.png

Resource contention

This shows the flow of common resources contentions between jobs. The resources can be either data sets or locks. You can search in top par a resource name pattern to filter results. See GRS page for more details.

http://www.pepstock.org/wiki/webui/Admin-Cluster-Resource_contention.png

Redo statements

Displays the queue of database statements that are on hold because the database is not available. See Persistence page for more details.

Nodes

  • Configuration, where you can see and manage single node configuration
  • Commands, where you can execute some command on single node and see the result
  • System status, provides a set of system performance indicators, as memory and cpu usage
  • Queues status, provides a set of queues indicators
Configuration

This panel let you to see the configuration files of each node which is part of current environment. Usage:

  1. Type a (part of) node name (or wildcard) and click Search button
  2. Select the node you want inspect the configuration
  3. Select a tab between Jem and Affinity policy
  4. The corresponding file will be shown

http://www.pepstock.org/wiki/webui/Admin-Nodes-Configuration.png

When the affinity file is changed, JEM node will be reloaded as soon as the file is saved.

Commands

You can execute from here a set of remote commands on a node, and see the output directly on web browser.

http://www.pepstock.org/wiki/webui/Admin-Nodes-Commands.png

Usage:

  1. Type a (part of) node name (or wildcard) and click Search button
  2. Select a found node from list
  3. Perform a command
  4. See the results

At the moment, these commands can be performed:

  • Get Log, shows the node log file. The amount of showed rows must be set in Apache Log4j configuration file. See Apache & Log4j for more details.
  • Exec Top, execs the OS top command (show the processes in execution on node)
  • View cluster, shows the Hazelcast message that summarizes the detected cluster nodes
System status

This view offer a table where you can see the node that are actually member of environment, with additional system data like:

  • Name, the node name
  • PID, the process id of JEM node
  • Time, the last sample time
  • Cpu, CPU usage at sample time, in percent
  • Memory available, the amount of free memory on system
  • Memory free, the amount of free memory of JEM node
  • Process Cpu, the percentage of CPU used by JEM process
  • Process Cpu Total, the amount (in milliseconds) of execution of JEM process
  • Process Memory used, the MB of memory used by JEM process

http://www.pepstock.org/wiki/webui/Admin-Nodes-SysStatus.png

This view can be filtered typing (part of) node name in the search field (real-time, no Search button needed)

You can also click on node name to see it's detailed data and history samples (per-minute).

Three graphs are also available to see the usage trend of:

  • Machine CPU %
  • Process CPU %
  • Process memory used

http://www.pepstock.org/wiki/webui/Admin-Nodes-SysStatus_detail.png

The Back button in top right corner bring you back to summary.

Queue status

In this table you can see all the nodes and some data about it:

  • Name, the node name
  • PID, the process id of JEM node
  • Time, the last sample time
  • Input, the number of jobs in Input queue
  • Input cost, the size (in KB) of Input queue
  • Running, the number of jobs in Running queue
  • Running cost, the size (in KB) of Running queue
  • Output, the number of jobs in Output queue
  • Output cost, the size (in KB) of Output queue
  • Running, the number of jobs in Running queue
  • Running cost, the size (in KB) of Running queue

http://www.pepstock.org/wiki/webui/Admin-Nodes-QueuesStatus.png

This view can be filtered typing (part of) node name in the search field (real-time, no Search button needed)

You can also click on node name to see it's detailed data and history samples (per-minute).

A graph for each queue is available to see the usage trend and the cost of queues.

http://www.pepstock.org/wiki/webui/Admin-Nodes-QueuesStatus_detail.png

The Back button in top right corner bring you back to summary.

Queues

This section shows you some information about JEM queues, all based on Hazelcast framework.

Current Status

This view show a chart that give to you a look on JEM job queues and the real-time dimension of them. The job queues are Input, Running, Output and Routing.

A per-node queues details are provided by the table at bottom.

http://www.pepstock.org/wiki/webui/Admin-Queues-Status.png

Statistics

This panel contains the statistics and history data from the job queues point of view. All indicators are provided by Hazelcast and they give important information about internal use of these queues. A chart summarizes the queues sizes (on top) and the table on bottom shows:

  • Queue, the name (kind) of the queue
  • Time, the last sample time
  • Entries, the number of jobs currently in queue
  • Hits, the number of hits (reads) of the locally owned entries
  • Locked Entries, the number of currently locked locally owned keys
  • Lock Waits, the number of cluster-wide threads waiting to acquire locks for the locally owned keys
  • Number of Gets, the number of get operations on map
  • Number of Puts, the number of put operations on map
  • Number of Removes, the number of remove operations on map

http://www.pepstock.org/wiki/webui/Admin-Queues-Statistics.png

For each queues displayed in the main panel, a detailed one is available and contains history data and charts for each item listed above:

http://www.pepstock.org/wiki/webui/Admin-Queues-Statistics_detail.png

The Back button bring you back to main panel.

Current Internals

This shows the size (in entries) of JEM internal queues:

  • roles is the map which contains all defined roles for security purposes
  • resources is the map which contains all defined resources instances, out-of-the-box and custom ones
  • preferences is the map which contains all user preferences on user interfaces
  • stats is the map which contains the last 20 statistics samples of the cluster (for all nodes)
  • routed is the map which contains all jobs routed on another environment for execution

http://www.pepstock.org/wiki/webui/Admin-Queues-Current_Internals.png

Security

This section manage everything related to security.

Please see also Roles section for user and roles administration.

Certificates Manager

This subsection let you to manage JEM x509 user certificates to let job submission if JEM is configured to use SocketInterceptor. In this case, the job needs to be submitted with a private key that match a public key stored here. This is used only when the client try to connect to the JEM cluster, because otherwise the connection will be refused. See Submitting jobs & keystore for more info.

The search bar on top let you to search certificates by alias:

http://www.pepstock.org/wiki/webui/Admin-Security-Certificates.png

If you want to add a new certificate, you can click on Add button on top right corner and you'll be asked for:

  • User ID, the User Id of the associated user
  • Certificate file, the file containing the certificate

http://www.pepstock.org/wiki/webui/Admin-Security-Certificates_add.png

You can also remove certificates: just select it and then click the Remove button. A confirmation dialog will be displayed.

Secret utility

This tool simply offer a way to encrypt and hash a secret pass-phrase (password). You can use it to encrypt a password that is used somewhere you don't want the password to be in clear.

Main use case for this features is when you want to define or update a resource by a batch, using the extended ANT utilities.

http://www.pepstock.org/wiki/webui/Admin-Security-SecretUtility.png

Usage: simply type your secret phrase twice and then click on Execute: the encrypted one and the hash will shown.

Clone this wiki locally
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.