Assigning ACLs to Files the Server Can Serve

The server can serve files that reside in the pub directory for a package or a subdirectory of the pub directory. For more information about how to serve files from the Integration Server, see the webMethods Service Development Help.

You control access to files by placing an .access file in the directory that contains files you want to protect. You can use an operating system tool of your choice to edit the .access file.

Note: The .access files control access to files the server serves, such as DSP and HTML files. To control access to a service that a DSP or HTML file calls, you must assign an ACL to the service itself. See Assigning ACLs to Folders, Services, and Other Elements for more information.

If the directory contains subdirectories, they will not inherit the protection, so you must provide an .access file in each directory. For each file in the directory that you want to protect, place a line in the .access file to identify the file and the ACL you want to use to protect the file.

For example, assume you have a directory that contains three files (adminpage.dsp, home.dsp, and index.htm). You want to protect the adminpage.dsp file with the Administrators ACL so that only administrators can access this file. You want to protect the home.dsp file with the Developers ACL so only developers can access this file. You also want to assign the Default ACL to the index.htm file so all users can access it. To accomplish this, you would place the following records in the .access file:

Note: In the above example, because you want all users to be able to access the index.htm file, you could omit the index.htm Default from the .access file. The server uses the Default ACL for files that are not identified in an .access file or all files in a directory without an .access file.

Important: Integration Server loads .access files when a package is loaded; therefore, if you want the changes you make to take effect immediately, reload the package.