Administering Insight Server
To ensure that your solutions run efficiently, you must administer the Insight Server in a single-server or multiple server topology. Administration tasks include starting and stopping the servers, setting system properties, managing solutions and its entities, working with solution connectivity, and how to resolve common problems.
- Administrator toolkit
The administrator toolkit consists of a set of MBeans (managed beans), scripts, and other tools that help you administer Decision Server Insights solutions and servers. - Creating, starting, and stopping servers
You can use the server script in the WebSphere® Liberty profile bin directory to create, start, stop, and check a server process. You can also run the serverManager shutdown command to stop a server, or isonline to determine whether a server is running. - Restarting a server to enable a persistence change
After you set up database persistence in your production topology, you must restart the runtime servers and then run the finalize command. - Maintaining operations in a production environment
You can do maintenance, repair, and overhaul (MRO) tasks in a production environment by removing each server from the multiple-server topology, and then add the servers back into the topology after the update is complete. - Modifying server behavior by setting properties
Run the propertyManager script with the list, get, or set command to retrieve the value of server properties and modify or set the property values. You can also set or get server properties by using the GlobalPropertiesMXBean API. - Reducing the size of stored rule agent state
For solutions that have many entities and that rely heavily on rule agents, you can reduce the size of the database significantly by changing the format of the memento to JSON. - Tuning Java virtual machines (JVM)
You can customize a server Java™ virtual machine (JVM) by editing the jvm.options file. - Simulating a runtime server fail-over
Decision Server Insights protects itself against an unexpected failure of a runtime server by employing redundant copies of cache data, called replicas. However, high availability of a Decision Server Insights application requires careful planning, sizing, and configuration of these replicas. - Ensuring a successful cluster restart
Before you deploy a Decision Server Insights application in production, you must test and measure the behavior of your cluster during a restart. Make these tests in a preproduction environment that emulates the production environment as closely as possible. - Connecting to the MBean server
You must establish a connection to the MBean server to use the JMX MBeans for managing Insight Server, solutions, and connectivity. - Synchronizing the clocks in a testing or production environment
To prevent unexpected results from a solution, ensure that the clocks on your Decision Server Insights servers and your event sources are synchronized within the required tolerance of the solution. - Managing deployed solutions
Run solutionManager commands to manage deployed solutions. You can also manage solutions by using MBean APIs. - Managing global aggregates
An administrator can intervene to manage global aggregate jobs and can fine-tune how global aggregates are run. - Managing connectivity
A solution can include a connectivity file that defines a set of inbound and outbound endpoints and their bindings. Decision Server Insights uses the solution connectivity definition files when it receives events from its inbound endpoints and sends events to its outbound endpoints. - Managing entities
Manage solution entities by using a solution agent, or by using the REST APIs. You can create, delete, and modify entities and also retrieve information about existing entities in a Decision Server Insights solution project. - Managing data returned from a data provider
By default, Decision Server Insights stores all of the enriched data that is returned by a data provider in an in-memory cache. To prevent the system from using too much memory, you can set the maximum size of the cache. Once the maximum size is reached, a least recently used (LRU) algorithm removes entries to maintain the cache size. - Monitoring solutions
You can monitor your solutions and see how they behave as a result of an event arriving in the server. - Monitoring server activity
Insight Monitor shows event rates, memory utilization, and processor utilization on runtime servers. - Creating threshold alarms
You can create threshold alarms to monitor the performance and response time data of your single server and generate a message when an anomaly is found. - Generating performance statistics
Use Performance Monitoring Infrastructure (PMI) to generate statistics that can help you identify performance-related patterns on a running server. The pmiManager script generates statistics that you use to identify specific agents or events that are causing performance problems, such as bottlenecks. - Restoring data after a system shutdown by running dataLoadManager
You can restore persisted data from the database as part of a disaster recovery procedure, and load the data back onto the Decision Server Insights system by running the dataLoadManager script commands. - Troubleshooting
Log and trace messages are captured in .log files in the logs directory of each server. You can use these messages to troubleshoot problems with the Decision Server Insights run time and the server.