Service-types are basically scripted tasks which perform an automated task on the network in the database. These tasks can be:
The service types can be executed through the NetYCE API interfaces or from the netYCE web-interface. Service types can create, modify or delete database objects, which can be located and used.
The Service-types form is divided in 3 sections:
Within the Service types section, the user has an overview of the service types which belong to the Client types to which the user has access. Here a new service type can be added , an existing service type can be deleted or duplicated .
When adding or duplicating a service type the following data must be entered:
With the and buttons resequencing of the rows is possible. The aliases will not be updated!
When selecting a row, the details will be displayed in the third section of the form. After each updated value, the next field will be updated to ensure the accurate syntax. The description field can be used as comment. It is also possible to add an empty row and use this as a comment row. In this case only the description field will be set.
The alias is being used only internally within a Service type script to use the result of one row as a variable in another row. It is advisable to use distinctive names for aliases as well as surround them by <hooks> to identify them visually as such.
Please refer to Service-types overview for some guidelines on Alias names.
The definition of a Service type is done with a specific syntax, which is guided by the visual editor. The Add and Locate can be assigned aliases, to be used as a reference to the object in the commands following it.
In general, everything written in UPPERCASE are syntax keywords, everything written in lowercase are aliases or values.
The article on Service type syntax offers a summary of the service-type commands available. They are grouped around the various object types that NetYCE supports.
The following example will add a node to a newly created service with a IP address assigned to interface Loopback0.
A whole set of example Service types is included in every distribution. You can copy and adapt them to suit your own architecture.
The below diagram shows how some of the database information for Nodes, Services, subnets, etc. is structured. This could help you design your service types and help you understand how each of the pieces tie together.