Category list

Setting Up the Server Policy PackageThe Server Scripts Policy

Setting Up the Server Policy Package—The Server Scripts Policy

This policy is a plural policy, which means that you can create multiple instances of this policy in a single policy package. You create this policy by clicking the Add button at the bottom of the main Server Policy Package screen. When you click the Add button, you are prompted to select a policy and to name the policy. You need to select Server Scripts for the policy and enter a unique policy name . After you do this, you can activate and modify the policy. Figure 5.25 displays a sample Server Script policy.

Figure 5.25. Script policy page of the scheduled load/unload policy in a Server Policy Package.

graphics/05fig25.jpg

This policy enables you to specify a set of scripts that you want to have run on your server.

You add a script to the policy by clicking the Add button. When you click the Add button, an entry is placed in the left window and you can edit the name of the script. After you name the script, you can choose the type of script that you will be creating. The choices of script types are currently NCF, NETBASIC, and PERL. After you identify the script type, you are free to type the script in the provided window. ZENworks for Servers provides no syntax checking or validation for the script you enter. You may enter ZENworks for Servers variables into the script and they will be processed prior to the script being executed.

You can add multiple scripts of any of the available types into this one policy. The scripts are executed in the order shown on the administration screen (from top to bottom). If you want to reorder the running of the scripts, you must select a script name from the left pane and click the up or down arrows to move the script into a different order.

When the ZENworks for Servers policy engine launches this policy, it creates a temporary script file (in its working directory) that contains the specific script, and then launches the corresponding NLM that works with the identified script, passing the NLM the name of the script to run. Consequently, netbasic.nlm and perl.nlm must already exist on the server where the script is to be run. These are normally installed with the standard NetWare server. Regardless whether a script fails or succeeds, the engine proceeds on to the next script.

On the Policy Schedule page, you may specify the time frame within which you want the system to enforce this policy. The details concerning your choices for the schedule are described in the next section, "Setting Up the Server Policy Package—The SNMP Community Strings."

Setting Up the Server Policy Package—The SNMP Community Strings

This policy enables you to specify the various SNMP community strings that are used in your system for the various levels: Monitor, Control, and Trap. Figure 5.26 displays a snapshot of this simple screen. NDS Rights are described earlier in the chapter in the "Setting Up a Container Policy Package" section.

Figure 5.26. SNMP Community Policy page of the SNMP Community Strings policy in a Server Policy Package.

graphics/05fig26.gif

In this page, you simply need to go to each of the fields and type in the community string that you want configured. These community strings are placed into the SNMP agents on the server, causing the SNMP agents to reset their strings to these values.

The Policy Schedule page enables you to customize (outside of the package default schedule) when you want the community strings applied to the system.

This page enables you to select when the package should be applied: Daily, Weekly, Monthly, Yearly, Relative, Run Immediate, Event, Interval, or Time.

After you select when you want the package applied, you must select additional fields in the lower portion of the screen. The following sections discuss the various options you have with scheduling the package.

Package Schedule

This option runs this policy based on the schedule that has been identified for the entire policy package. This is the default for all policies.

Daily

When you choose to have the policy applied to the system daily, you need to select when the policies are enforced.

This schedule requires that you select the days when you want the policy applied. You select the days by clicking the days you want. The selected days appear as depressed buttons .

In addition to the days, you can select the times the policies are applied. These start and stop times provide a range of time where the policies will be applied.

You can have the policy also reapplied within the time frame every specified hour /minute/second by clicking the Repeat the Action Every field and specifying the time delay.

Weekly

You can alternatively choose that the policies be applied only weekly.

In this screen, you choose on which day of the week you want the policy to be applied. When you select a day, any other selected day is deselected. After you select the day, you can also select the time range in which the policy may be applied.

To keep all the policies from simultaneously applying to the servers, you can select the Randomly Dispatch Policy During Time Period option. This causes each server to choose a random time within the time period when it retrieves and applies the policy.

Monthly

Under the monthly schedule, you can select on which day of the month the policy should be applied or you can select Last Day of the Month to handle the last day, because all months obviously do not end on the same calendar date.

After you select the day, you can also select the time range within which the policy may be applied.

Yearly

You select a yearly schedule if you want to apply the policies only once a year.

On this screen, you must choose the day on which you want the policies to be applied. This is done by selecting the Calendar button to the right of the Date field. This brings up a Monthly dialog box where you can browse through the calendar to select the date on which you want your policies to be applied. This calendar does not correspond to any particular year and may not take into account leap years in its display because you are choosing a date for each year that will come along in the present and future years .

After you select the date, you can also select the time range within which the policy may be applied.

Relative

This option enables you to repeat the policy every x unit of time. The specified time can contain days, hours, minutes and/or seconds. You may specify each length of time by typing the number of each unit in each of the respective fields.

After you identify the intervals, the policy is applied, and the system does not apply the policy until the next specified interval has passed.

Run Immediately

In the Run Immediately option, the system runs the policy immediately upon administration (or refresh of the server). You can then also specify how often to repeat the policy by selecting the Repeat the Action Every field and identifying the delay time. After the policy is applied, the system reapplies the policy after each of the intervals has passed.

Event

When you choose this option, the policy is applied when certain events have occurred. The events that you can select are as follows :

System Startup . This applies the policy just after the system has started up.
System Shutdown . This applies the policy just before the system is shut down.
Custom Event ID . This is a third-party event. This is to be a Java class event that is identified by a third party that they can plug into the ZENworks for Servers policy engine. This feature is currently not documented in ZENworks for Servers. At some future time, the team may provide documentation on the methods to register with the system.

Interval

This schedule type enables you to specify how often to repeat the policy. You can specify the interval with a combination of days, hours, minutes, and seconds. This is very similar to the Run Immediate type, except that this type waits for the interval to pass before applying the policy for the first time.

Time

This enables you to specify a specific calendar date and time when the policy is to be applied. When the current date on the server is beyond the identified date, the policy is applied.