- Installing the SIS server and the collectors
- Installing the Reserved WEBDEV Server for SIS
- Installing the collectors
- Operating mode of the collection mechanism
- Configuring the development environment
- Address of the SIS server
- Using the SIS
- Connecting to SIS
- Using the SIS
- Automatic audit of an element
- Summary of a network resource
- Impact study of a server stoppage
- Finding the dependencies of a component or an application
- Generating the use statistics
- The centralized recovery of the messages issued by the monitoring robot
- Generating statistics about the errors
The Software Infrastructure Supervisor (SIS) is a monitoring system of a set of WINDEV and WEBDEV applications. It is used to get dashboards and statistics about the status of the applications deployed, the components and the servers used.
The SIS includes two elements:
- The SIS server: WEBDEV application server containing the SIS database as well as the Web site for consultation.
- The data collectors: Services deployed on all the network computers to check.
The SIS operates by collecting statistical information on all the network computers and by producing a summary and dashboards from this information.
The principle is as follows:
- The WLanguage applications (WINDEV applications and components, WEBDEV sites, ...) periodically send information to the collection service installed on the computer where they are run.
- The collection service sends the collected information to the SIS server.
- The SIS server presents the results of thee analysis.
- In order for the information to be relevant, the service for collecting information must necessarily by installed ON EACH NETWORK COMPUTER.
- The information displayed by the SIS being the result of a statistical collection, it never represents the status of a network at a given time.
Installing the SIS server and the collectors
Installing the Reserved WEBDEV Server for SIS
The setup of Reserved WEBDEV Server for SIS is supplied with WINDEV, WEBDEV and WINDEV Mobile.
The setup pack is found in the "Install\WDRServer" sub-directory of the product directory.
All you have to do is run the WXxxxPACKRSRV.exe executable and follow the indications given by the setup wizard.
- The setup should be performed on a "Server" operating system (Windows 2008 Server for example).
- The setup cannot be performed on a Linux server.
- The setup directory must be local to the computer.
Two directories are requested when installing the SIS:
- The setup directory of the Reserved WEBDEV Server that will contain the server executables and the SIS site.
- The reference setup directory of the collectors.
Installing the collectors
The setup of the collectors on the network computers is performed in "push" mode from the reference directory chosen when the SIS was installed.
The "push" setup is performed from WDAdminEXE.exe.
See the documentation about the setups in "push" mode
for more details.
Important: To get relevant information, the collector must be deployed on all the network computers.
Operating mode of the collection mechanism
The collector locally stores the data collected during a period (5 minutes by default, this duration can be configured in the management options of SIS accessible from the site).
When this time-out is exceeded (or if the volume of collected data has reached a given level), the data is sent to the SIS server.
If the server is not accessible when this send operation is performed (network failure, server down, etc.), the data collected since the last send operation are lost but the service is not stopped. It restores a standard cycle of collect and a new attempt to send the data will be performed at the end of the next period or when the volume of data is sufficient.
Stopping the collector service
The collector service can be stopped for one of the following reasons:
- Fatal error in the collector.
- Failure during the identification toward the SIS server (incompatible version for example).
- Failure creating or accessing the shared memory zone.
The service will be automatically restarted when the computer is rebooted. It can also be restarted manually by using the control panel ("Control panel .. Management tools .. Services"). The service name is WDCollector (full name PC SOFT SIS Collector).
Configuring the development environment
Address of the SIS server
The SIS can be directly accessed from the project dashboard by clicking the "Infrastructure audit" button.
If the SIS collector is installed on the local computer, a browser is automatically started on the SIS site.
If the collector is not found, a configuration window allows you to enter the address of the SIS server (computer name or IP address).
Connecting to SIS
During the first access to the Web site of SIS, the connection must be established with the "admin" user name and with the "admin" password.
Then, you have the ability to define the accounts for the different users ("Management" menu, "Manage the user accounts" option).
Note: You also have the ability to allow each user to create his own account from the home page of SIS ("Management" menu, "Configuration" option, "Allow the users to create their accounts" option).
Using the SIS
The methods for using the SIS differ according to the requested information. The main uses are as follows:
Automatic audit of an element
The audit of an element provides a set of features for improving the quality and the performances:
- of an application
- of a component
- of a server
- of a user
- of a user computer
For example, you can find out the distribution of the network accesses by a server, or a by user, or a by client computer. SIS can also list the most often used applications. You can also find out which components are used by a given application.
Summary of a network resource
The summary of a network resource lets you find out for example:
- The number of network accesses per server
- The number of applications connected to a server
- The list of applications accessing a HyperFileSQL server
- The number of accesses to a file or a directory
- The distribution of the number of accesses per type of resource
Impact study of a server stoppage
When a maintenance operation must be performed on a server and when this server must be stopped, it is important to find out what is the impact of its operation on the applications and on the users.
To do so, you can find out:
- what are the resources used by the server
- the applications connected to this server
- the time distribution of the accesses to this server
- which computers or users access the server the most
Finding the dependencies of a component or an application
When implementing a new version of an application or component, it is important to identify the modules that will have to be updated or checked. You can find out:
- for a component, what are the applications that use this component,
- for an application, which components are used.
Generating the use statistics
From the Consultation
menu of SIS, you have the ability to view a summary table that groups several statistics:
- The n users who perform the most network accesses
- The n computers performing the most network accesses
- The n applications performing the most network accesses
- The n servers most accessed
- The n network resource types the most accessed
- The n most accessed network resources (Caution: the compute time may be long)
The centralized recovery of the messages issued by the monitoring robot
From the SIS dashboard, you have the ability to display the messages returned by the monitoring robot. You have the ability to configure the display (refresh time or volume of data to collect).
Generating statistics about the errors
From the SIS dashboard, you have the ability to display the errors that occurred when the running the applications. The error table presents the list of applications as well as statistics regarding the number of errors per application.
Furthermore, you have the ability to see the full details of the error.
This page is also available for…
Click [Add] to post a comment