Principles of assyst
From wiki.axiossystems.com
At the centre of assyst’s operation is a common database of details about your organization and how you want to use assyst (see Relational Databases For Beginners for a primer on databases).
The core areas, Incident, Problem, Change, and Asset and Configuration Management, require for their operation information that is common to the other areas. One database minimizes the effort in recording the data, ensures the information is consistent and makes it easier to keep the data up to date. It also makes it easier for the different areas to share information and communicate.
The assyst Database
The assyst Configuration Management DataBase (CMDB) supports three database types:
- Microsoft SQL.
- Oracle.
- IBM DB2.
These databases have to be installed prior to the installation of assyst.
The current databases that assyst supports are given in the Supported Versions Document
The assyst Database is built using the windows based utilities installed during the installation of the underlying assyst Enterprise Windows Edition. Full details of these operations are provided in the Windows Edition Installation Notes which accompany the release DVD or download.
Web Application Server
assyst Enterprise Web Edition is an implementation of assyst which makes it available over the Internet. As such this is dependent on it being hosted on an Application Server. assyst supports two application servers; JBoss and WebSphere. Further details about their use by assyst can be found in the related installation guides:
- assyst Web Client JBOSS Installation and Configuration Guide (further guidance on optimization of JBOSS is given in JBOSS Clustering).
- assyst Web Client WebSphere Installation and Configuration Guide.
Administration of the assyst Web Client
A number of features for the administration of the assyst Web Client are managed via the assyst Administration Application. These include:
- Default data settings in assyst can be set using the assyst Parameters Form.
- Locking of Events can be managed using the Current Event Soft Locks Form.
- Control of data access based on group membership of specific entities on a database table basis - Using the Customer Service Groups.
- Standard eMailing controls can be defined using the Global SMTP Settings Form.
- JNDI Parameters - Using the Additional Parameters Form.
- The control of licensing of can be set using the License Entry Form, the Login Sessions Form, License Usage Threshold Graphical Plot Form and the Mail Users Form. Further controls can be established to maintain Contact User Concurrent License groupings using the Contact User License Grouping Form.
- The amount of data returned by the system from the database on lookup searches can be defined using the Lookup Thresholds Form.
- The ability to operate with Service Department and Suppliers in different time zones can be managed using the Service Department Time Zones Form and Supplier Time Zones Form.
- Expressions to control the activities of Service level Agreements can be defined using the SLA Expressions Form.
In the assyst Web Client a number of administrative tasks can be performed. These are located on the Tools menu, or under the options on the Configuration menu. These include:
- Grouping Contact Users to provide administrative units on the Contact User Query Profile Form.
- assyst Users can also be grouped as administrative users using the Privilege Group Form.
- Managing information messages to assystNET and assyst Web Client users can be done usingthe Message Center.
- Transmitting the knowledge base for assystNET and assyst Web Client users can be performed using the Knowledge Base, as can the online Help for to assystNET users.
