In order to set up the Security Manager for use with a VTS application, the following steps must be taken:
• Machines on which the application will run must be designated as either servers or clients.
• Initial security settings for the application must be assigned.
• An account list for the application must be provided or created.
To illustrate this process in a meaningful way, the next subsections will walk the reader through the Security Manager setup for a fictitious VTS application called "Vapor". After everything is up and running, several situations will be examined to address concerns about data integrity.
As before, the following notational conveniences will be used throughout the example:
• VTS refers to the VTS installation directory.
• OEM[x] refers to zero or more intermediate directories, from which a VTS application can inherit objects and settings.
• App refers to the VTS application's end-user directory.
• Mx refers to a PC that is running the VTS application.
• Sx refers to a Security Manager RPC server.
• Cx refers to a Security Manager RPC client.
Topics in this section: