Creating and deploying server macro libraries

Start of changeServer macro libraries are available for the HTML model pages and Config model users. For the HTML page, users can use Deployment wizard to customize the server macro library; for the Config model, users can use the Z and I Emulator for Web admin console. GUI based configuration allows the administrator to configure for each session. For the administrator to configure for all the sessions defined, use the HTML parameter SetServerMacroLibraryPath.End of change

Start of changeThe value of SetServerMacroLibraryPath is share path or relative path. You can use the values to create and maintain a central repository of macros for users to access from their Z and I Emulator for Web sessions. These macros are downloaded to the user's machine only when it is needed. When you make changes to a server macro, users automatically get your updates the next time when they access the macro.End of change

Server macro libraries have several benefits:
  • They provide a convenient way to store, edit, and administer macros, all from one easy-to-access location.
  • They allow easy sharing of macros among multiple users and across any number of sessions.
  • They eliminate the need to import macros into the Z and I Emulator for Web session, and can therefore reduce the size of the session. The macros are only downloaded to the user's machine if and when the user accesses them.
  • You can edit macros and replace the files in the server macro library at any time without regenerating Z and I Emulator for Web sessions or modifying the HTML files. Any changes you make are automatically available the next time a user requests that macro.

Server macro libraries can reside on a Web server or on a shared network drive. For both types of libraries, you can control which macros are available to particular Z and I Emulator for Web sessions. If you use a Web-based macro library, you need to create a text file that identifies the specific macros that you want to be available for the session that you are configuring. If you use a shared drive-based macro library, then all the files in the specified directory will be available to the session. Users will not be allowed to write to a Web-based macro library, but they may update a shared drive-based macro library if they have write-access.