Policy Server Guides › Policy Server Administration Guide › Policy Server Tools › XPSExport › Map the Active Directory inetOrgPerson Attribute

Map the Active Directory inetOrgPerson Attribute

If any of your SiteMinder user stores are on Microsoft Active Directory servers, you need to map the inetOrgPerson in each Active Directory server before counting the SiteMinder users in it.

To map the inetOrgPerson attribute

1. Open the Administrative UI.
2. Click Infrastructure, Directory, User Directory, Modify User Directory.

   The search screen appears.

3. Click the Directory you want and click Select.

   The Modify User Directory: Directory_Name window opens.

4. In the Attribute Mapping List group box, click Create.

   The Create Attribute Mapping dialog appears.

5. Click Create a new object of type Attribute Mapping, and then click OK.

   The Create Attribute Mapping: dialog appears.

6. Click the Name field and type the following:

   inetOrgPerson
   

7. (Optional) We recommend clicking the Description Field and enter the following:

   Custom Mapping to Count Active Directory Users (with XPSCounter)
   

8. In the properties group box, do the following:
   1. Make sure the Alias radio button is selected.
   2. Click the Definition field and type the following:

      User
      

9. Click OK.

   The Modify User Directory window appears.

10. Click Submit.

    Your changes are saved and the inetOrgPerson attribute is mapped.

Determine the Number of Users Associated with SiteMinder Policies

To comply with the SiteMinder licensing terms, you can determine how many users in your organization are associated with SiteMinder policies.

Note: If you do not have write access to the SiteMinder binary files (XPS.dll, libXPS.so, libXPS.sl), an Administrator must grant you permission to use the related XPS command line tools using the Administrative UI or the XPSSecurity tool.

To determine the number of users

1. Open a command window on the Policy Server, and then enter the following command:

   XPSCounter
   

   The tool starts and displays the name of the log file for this session, and the License Parameters menu opens.

2. Enter 1.

   The Parameter menu appears.

3. Enter C.

   The Counter menu appears.

4. Enter I.
5. Enter ? to search for a user directory XID. Only those user directories that are defined in your policy store appear in the list.
6. Enter the number of the directory that contains the users you want to count.

   Note: This tool counts the number of user objects in each directory that you specify. It does not account for the same user object being listed in multiple directories or multiple user objects for the same user in a directory. You must consider this when interpreting the results provided by this tool.

7. (Optional) Enter a comment to describe the results.

   The users are counted and a confirmation message appears.

8. (Optional) Repeat Steps 5 through 8 to count the users in another directory.
9. Enter V.

   The following information appears for each directory counted:

   XID

   Displays the unique identifier for the specified user directory.

   Example: CA.SM::UserDirectory@0e-50ea30f0-b5c0-450c-a135-1e317dd25f11

   Name

   Displays the name of the specified user directory (as defined in the Administrative UI).

   : count

   Displays the most-recent user count of the specified user directory. You do not have to delete any previous values stored in the counter because this value is updated automatically every time the counter is run.

   Example: : 23

   Total

   Displays the total of number of users from all of the user directories you counted. For example, if you counted number of users for two different directories, and each directory has 23 users, the total shown will be 46.

XPSConfig

XPSConfig is an interactive command-line utility that allows administrators and members of operations to view product parameters and, if allowed, edit their settings. While you may have your own product-specific configuration tool using XPS programming interfaces, XPSConfig is available so that this is not a requirement.

For each vendor and installed product, XPSConfig manages the parameters or named settings that are defined in the product's Data Dictionary. Each product can read, write, and validate its own parameter settings.

To use XPSConfig, you must be an administrator with XPSConfig rights.

Parameters have the following attributes:

Name

Specifies the name of the parameter.

Limits:

• Names must start with a letter or underscore and contain only letters, numbers, and underscores.
• Names can be up to 32 characters in length.
• Names are not case-sensitive.

Type

Specifies the data type of the parameter value:

Logical | Numeric | String

Logical

Specifies a Boolean value: TRUE or FALSE.

Numeric

Specifies an integer.

String

Specifies a string of characters.

Scope

Specifies the value or scope of the parameter:

Ask | Global | Local | Managed | Overrideable | Read Only

Ask

Specifies that the value is managed by the product, not by XPS, and that the value is read only.

Global

Specifies that the value is stored in the policy store and accessible by all Policy Servers sharing that policy store.

Local

Specifies that each Policy Server stores its own value.

Managed

Specifies that the value is managed by the product, not by XPS, and that the value is read-write.

Overrideable

Specifies that a value stored locally on a Policy Server can override a value stored globally on a shared policy store.

Read Only

Specifies that the value is both the default value and read only.

Export

Specifies whether the parameter is included in exports of the policy store.

Type: Boolean

Report

Specifies whether the parameter is included in capabilities reporting for the Policy Server.

Type: Boolean

RemoteAccess

Specifies what type of access the remote API has to the parameter:

None | Read | ReadWrite

Description

Describes the purpose of the parameter.

LicenseType

Specifies the type of license limit:

None | SoftLimit | HardLimit | ExpDate

None

Specifies that the parameter is not a license limit.

SoftLimit

Specifies that the parameter is a soft or advisory license limit.

HardLimit

Specifies that the parameter is a hard or absolute license limit.

ExpDate

Specifies that the parameter is the date on which the license expires.

Default Value

Specifies a default value for use when the current value is undefined.

Note: If the default value is undefined, its value is specified according to its data type:

String

space

Number

zero

Boolean

FALSE

Visible

Specifies whether the parameter is visible to XPSConfig.

Type: Boolean

Syntax

XPSConfig has the following format:

XPSConfig [-vendor vendor] [-product product]
[-?] [-vT | -vI | -vW | -vE | -vF]
[-l log_path] [-e err_path] [-r rec_path]

Parameters

XPSConfig includes the following options:

-vendor

(Optional) Specifies the name of the vendor whose data you want to view.

-product

(Optional) Specifies the name of the product whose data you want to view.

-?

(Optional) Displays help information for this utility.

-vT | -vI | -vW | -vE | -vF

(Optional) Specifies when to log error information to the error file and how much information to log.

-vT

Logs detailed information so that you can TRACE errors.

-vI

Logs information in case there is an error.

-vW

Logs error information in the event of a WARNING, ERROR, or FATAL error.

-vE

Logs error information in the event of an ERROR or FATAL error.

-vF

Logs error information in the event of a FATAL error.

-l

(Optional) Outputs logging information to the specified location.

Default: stdout

-e

(Optional) Outputs error information to the specified location.

Default: stderr

-r

(Optional) Outputs a record of the session to the specified location.

XPSEvaluate

XPSEvaluate is an interactive command-line utility that allows administrators and application developers to evaluate expressions and test performance. To use XPSEvaluate, you must be an administrator with XPSEvaluate rights.

Syntax

XPSEvaluate has the following format:

XPSEvaluate [-np] [-trace] [-dbg debuglist]
[-f DB | formulapath] [-c contextpath] [-u userpath] [-step]
[-?] [-vT | -vI | -vW | -vE | -vF]
[-l log_path] [-e err_path] [-r rec_path]

Parameters

XPSEvaluate includes the following options:

-np

(Optional) Specifies no prompt.

-trace

(Optional) Turns on tracing.

-dbg

(Optional) Specifies the debug list.

-f

(Optional) Specifies the location of the named expressions.

Note: DB specifies the policy store.

-c

(Optional) Specifies the location of the context values.

-u

(Optional) Specifies the location of the user attributes.

-step

(Optional) Shows evaluation steps.

-?

(Optional) Displays help information for this utility.

-vT | -vI | -vW | -vE | -vF

(Optional) Specifies when to log error information to the error file and how much information to log.

-vT

Logs detailed information so that you can TRACE errors.

-vI

Logs information in case there is an error.

-vW

Logs error information in the event of a WARNING, ERROR, or FATAL error.

-vE

Logs error information in the event of an ERROR or FATAL error.

-vF

Logs error information in the event of a FATAL error.

-l

(Optional) Outputs logging information to the specified location.

Default: stdout

-e

(Optional) Outputs error information to the specified location.

Default: stderr

-r

(Optional) Outputs a record of the session to the specified location.

More information:

Attributes and Expressions Reference

XPSExplorer

XPSExplorer is an interactive command-line utility that allows an administrator or application developer to view the data in a policy store. XPSExplorer has two uses:

• To determine the identifiers of objects for a granular export or import by exploring a list of domains or realms
• To repair the object store in the event that the store is damaged and must be repaired manually. This action should be performed only under the guidance of CA support.

To use XPSExplorer, you must be an administrator with XPSExplorer rights.

Syntax

XPSExplorer has the following format:

XPSExplorer [-?] [-vT | -vI | -vW | -vE | -vF]
[-l log_path] [-e err_path] [-r rec_path]

Parameters

XPSExplorer includes the following options:

-?

(Optional) Displays help information for this utility.

-vT | -vI | -vW | -vE | -vF

(Optional) Specifies when to log error information to the error file and how much information to log.

-vT

Logs detailed information so that you can TRACE errors.

-vI

Logs information in case there is an error.

-vW

Logs error information in the event of a WARNING, ERROR, or FATAL error.

-vE

Logs error information in the event of an ERROR or FATAL error.

-vF

Logs error information in the event of a FATAL error.

-l

(Optional) Outputs logging information to the specified location.

Default: stdout

-e

(Optional) Outputs error information to the specified location.

Default: stderr

-r

(Optional) Outputs a record of the session to the specified location.

Export a Subset of Policy Store Data

To export a subset of policy store data, you need the identifiers of the objects (XIDs) that you want to export. You can use XPSExplorer to locate object identifiers. To use XPSExplorer, you must be an administrator with XPSExplorer rights.

In this use case, you export the following accounting applications:

• Accounts Payable
• Accounts Receivable
• General Ledger
• Payroll

Export a subset of policy store data

1. Open a command prompt on the machine hosting the Policy Server.
2. Enter the following command:

   XPSExplorer
   

   The main menu opens and lists vendors, products, and classes.

   Note: Only objects in top-level classes can be exported. Top-level classes are marked with asterisks.

3. Enter the number corresponding to the class of objects that you want to export.

   The Class Menu opens.

   Example: If the number 15 corresponds to accounting, enter 15.

4. Enter S to view the objects in the class.

   The Search Menu opens and the objects in the class are listed.

   Example Search Results:

   1-CA.SM::Accounting@0e-08c6cadb-e30b-4e06-9e2e-b3d7a866fab8

   (I) Name : "Accounts Payable"

   (C) Desc : "accounts payable"

   2-CA.SM::Accounting@0e-3b0f4ccf-71f3-4968-b095-2b5a830c3244

   (I) Name : "Accounts Receivable"

   (C) Desc : "accounts receivable"

   3-CA.SM::Accounting@03-1c7ac22e-6646-4c61-8f2f-6261a0ef3a92

   (I) Name : "General Ledger"

   (C) Desc : "general ledger"

   4-CA.SM::Accounting@10-8d78bb81-ae15-11d1-9cdd-006008aac24b

   (I) Name : "Payroll"

   (C) Desc : "payroll"

   5-CA.SM::Accounting@@12-88f119a0-3fd1-46d0-b8ac-c1e83f00f97d

   (I) Name : "Job Costing"

   (C) Desc : "job costing"

   Example Object Identifiers (XIDs):

   CA.SM::Accounting@0e-08c6cadb-e30b-4e06-9e2e-b3d7a866fab8

   CA.SM::Accounting@0e-3b0f4ccf-71f3-4968-b095-2b5a830c3244

   CA.SM::Accounting@03-1c7ac22e-6646-4c61-8f2f-6261a0ef3a92

   CA.SM::Accounting@10-8d78bb81-ae15-11d1-9cdd-006008aac24b

   CA.SM::Accounting@@12-88f119a0-3fd1-46d0-b8ac-c1e83f00f97d

5. Enter Q three times to exit the Search, Class, and Main Menus and return to the command prompt.
6. Enter the following command at the command prompt:

   XPSExport output_file -xo object_XID_1 -xo object_XID_2
   -xo object_XID_3 -xo object_XID_4
   

   output_file

   Specifies the XML file to which the policy store data is exported.

   -xo object_XID

   Specifies the identifier of each object that you want to export.

   Note: You can copy the object identifiers (XIDs) from the Search results and paste them in the command line.

   Example:

   XPSExport accounting.xml
   -xo CA.SM::Accounting@0e-08c6cadb-e30b-4e06-9e2e-b3d7a866fab8
   -xo CA.SM::Accounting@0e-3b0f4ccf-71f3-4968-b095-2b5a830c3244
   -xo CA.SM::Accounting@03-1c7ac22e-6646-4c61-8f2f-6261a0ef3a92
   -xo CA.SM::Accounting@10-8d78bb81-ae15-11d1-9cdd-006008aac24b
   

   The policy store data for the specified accounting applications is exported to accounting.xml.

XCart Management

XPSExplorer includes the XCart feature. XCart allows you to collect the identifiers of the objects (XIDs) that you want to export and save them to a file for later use without manually copying and pasting each one. To use XPSExplorer, you must be an administrator with XPSExplorer rights.

To access XCart, enter X for XCart Management in the Main Menu of XPSExplorer. The XCart Menu opens and displays any objects that are in the XCart. The following options are context-sensitive and may or may not be displayed depending on the context:

C - Clear cart.

Empties the XCart.

L - Load cart from file.

• Initial load - Loads the XCart with the contents of the specified file and remembers the specified file name as the XCart file.
• Subsequent loads - Adds the contents of the specified file to the XCart.

  Note: The name of the XCart file does not change.

S - Save cart to file: xcart_file

Saves the contents of the XCart to the XCart file.

Important! The S command overwrites the contents of the XCart file without prompting first.

N - Save cart to new file.

Saves the contents of the XCart to the specified file and remembers the specified file name as the XCart file.

Note: The N Command prompts before overwriting the specified file.

Each object is tagged with an import mode that determines how it will be imported from the XPS file to the policy store:

A - Set import mode to ADD.

Adds new objects; does not replace existing objects.

O - Set import mode to OVERLAY.

Replaces existing objects; does not add new objects.

R - Set import mode to REPLACE.

Replaces existing objects and adds new objects.

D - Set import mode to default.

Specifies the default import mode.

Note: For each product class, there is a default import mode defined in the product's data dictionary.

Q - Quit

Exits the XCart Menu and returns to the Main Menu.

Export a Subset of Policy Store Data Using XCart

To export a subset of policy store data, you need the identifiers of the objects (XIDs) that you want to export. You can use the XCart feature of XPSExplorer to locate objects and save them in an XCart file for later use when you export. For example, an administrator can set up an XCart file for members of operations to use as needed. To use XPSExplorer, you must be an administrator with XPSExplorer rights.

In this use case, you save the following four accounting applications in a file for later use:

• Accounts Payable
• Accounts Receivable
• General Ledger
• Payroll

Export a subset of policy store data using XCart

1. Open a command prompt on the machine hosting the Policy Server.
2. Enter the following command:

   XPSExplorer
   

   The Main Menu opens and lists vendors, products, and classes.

   Note: Only objects in top-level classes can be exported. Top-level classes are marked with asterisks.

3. Enter X for XCart Management.

   The XCart Menu opens.

4. Create a text file.

   Example: C:\xcart\accounting.txt

   Note: This is where you want the contents of the XCart to be saved.

5. Enter L for Load cart from file.
6. Enter the path and name of the text file you created.

   The specified file name is remembered as the XCart file.

   Example: C:\xcart\accounting.txt

   Note: The file must exist. If not, L has no effect.

7. Enter Q to return to the Main Menu.
8. Enter the number corresponding to the class that you want to export.

   The Class Menu opens.

   Example: If the number 15 corresponds to Accounting, enter 15.

9. Enter S to view the objects in the class.

   The Search Menu opens and the objects in the class are listed.

   Example Search Results:

   1-CA.SM::Accounting@0e-08c6cadb-e30b-4e06-9e2e-b3d7a866fab8

   (I) Name : "Accounts Payable"

   (C) Desc : "accounts payable"

   2-CA.SM::Accounting@0e-3b0f4ccf-71f3-4968-b095-2b5a830c3244

   (I) Name : "Accounts Receivable"

   (C) Desc : "accounts receivable"

   3-CA.SM::Accounting@03-1c7ac22e-6646-4c61-8f2f-6261a0ef3a92

   (I) Name : "General Ledger"

   (C) Desc : "general ledger"

   4-CA.SM::Accounting@10-8d78bb81-ae15-11d1-9cdd-006008aac24b

   (I) Name : "Payroll"

   (C) Desc : "payroll"

   5-CA.SM::Accounting@@12-88f119a0-3fd1-46d0-b8ac-c1e83f00f97d

   (I) Name : "Job Costing"

   (C) Desc : "job costing"

10. For Accounting applications one through four:
    1. Enter the number corresponding to the application.
    2. Enter X for Add to XCart.
    3. Enter Q to exit the XCart Menu and return to the Search Menu.

       Note: An asterisk before an application indicates that it is in the XCart.

11. Enter Q twice to exit the Search and Class Menus and return to the Main Menu.
12. Enter X for XCart Management.
13. Enter S to Save the cart to the XCart file: C:\xcart\accounting.txt.
14. Enter Q twice to exit the XCart and Main Menus and return to the command prompt.
15. Enter the following command at the command prompt:

    XPSExport output_file -xf xcart_file
    

    output_file

    Specifies the XML file to which the policy store data is exported.

    -xf xcart_file

    Specifies the path and name of the XCart file containing the identifiers of the objects (XIDs) to export.

    Example:

    XPSExport accounting.xml C:\xcart\accounting.txt
    

    The policy store data for the accounting applications saved in the XCart file is exported to accounting.xml.

Add an Application to an XCart File

In this use case, you add a fifth accounting application, Job Costing, to the following four accounting applications already in the XCart file, accounting.txt, using the XCart feature of XPSExplorer:

• Accounts Payable
• Accounts Receivable
• General Ledger
• Payroll

Note: To use XPSExplorer, you must be an administrator with XPSExplorer rights.

Add an application to an XCart file

1. Open a command prompt on the machine hosting the Policy Server.
2. Enter the following command:

   XPSExplorer
   

   The Main Menu opens and lists vendors, products, and classes.

   Note: Only objects in top-level classes can be exported. Top-level classes are marked with asterisks.

3. Enter X for XCart Management.

   The XCart Menu opens.

4. Enter L for Load cart from file.
5. Enter the path and name of the existing text file containing the four accounting applications.

   The specified file name is remembered as the XCart file.

   Example: C:\xcart\accounting.txt

6. Enter Q to return to the Main Menu.
7. Enter the number corresponding to the class that you want added to the XCart file.

   The Class Menu opens.

   Example: If the number 15 corresponds to accounting, enter 15.

8. Enter S to view the objects in the class.

   The Search Menu opens and the objects in the class are listed.

   Example Search Results:

   1-CA.SM::Accounting@0e-08c6cadb-e30b-4e06-9e2e-b3d7a866fab8

   (I) Name : "Accounts Payable"

   (C) Desc : "accounts payable"

   2-CA.SM::Accounting@0e-3b0f4ccf-71f3-4968-b095-2b5a830c3244

   (I) Name : "Accounts Receivable"

   (C) Desc : "accounts receivable"

   3-CA.SM::Accounting@03-1c7ac22e-6646-4c61-8f2f-6261a0ef3a92

   (I) Name : "General Ledger"

   (C) Desc : "general ledger"

   4-CA.SM::Accounting@10-8d78bb81-ae15-11d1-9cdd-006008aac24b

   (I) Name : "Payroll"

   (C) Desc : "payroll"

   5-CA.SM::Accounting@@12-88f119a0-3fd1-46d0-b8ac-c1e83f00f97d

   (I) Name : "Job Costing"

   (C) Desc : "job costing"

   Note: An asterisk before an application indicates that it is in the XCart.

9. To add Job Costing to the XCart file:
   1. Enter 5 for the Job Costing application.
   2. Enter X for Add to XCart.
   3. Enter Q to exit the XCart menu and return to the Search Menu.

      The asterisk before the application indicates that it is in the XCart.

   4. Enter Q twice to exit the Search and Class Menus and return to the Main Menu.
   5. Enter X for XCart Management.
   6. Enter S to Save the XCart to the XCart file: C:\xcart\accounting.txt.

      Job Costing is added to accounting.txt.

10. Enter Q twice to exit the XCart and Main Menus and return to the command prompt.

XPSSecurity

XPSSecurity is an interactive command-line utility that allows administrators and members of operations to create and delete administrators and edit their rights. To use XPSSecurity, you must be an administrator with XPSSecurity rights.

Syntax

XPSSecurity has the following format:

XPSSecurity [-?] [-vT | -vI | -vW | -vE | -vF]
[-l log_path] [-e err_path] [-r rec_path]

Parameters

XPSSecurity includes the following options:

-?

(Optional) Displays help information for this utility.

-vT | -vI | -vW | -vE | -vF

(Optional) Specifies when to log error information to the error file and how much information to log.

-vT

Logs detailed information so that you can TRACE errors.

-vI

Logs information in case there is an error.

-vW

Logs error information in the event of a WARNING, ERROR, or FATAL error.

-vE

Logs error information in the event of an ERROR or FATAL error.

-vF

Logs error information in the event of a FATAL error.

-l

(Optional) Outputs logging information to the specified location.

Default: stdout

-e

(Optional) Outputs error information to the specified location.

Default: stderr

-r

(Optional) Outputs a record of the session to the specified location.

Make an Administrator a Super User

A super user is defined when the connection to the external administrator store is configured. The super user is used to create and manage all other administrator accounts. If the super user is unavailable, use XPSSecurity to make any user in the external store a super user.

To make an administrator a super user

1. Log into the Policy Server host system with a SiteMinder administrator account that has XPSSecurity rights.

   Note: If an administrator with XPSSecurity rights is not available, you can log in as one the following:

   • (Windows) the system administrator
   • (UNIX) root
   • the user who installed the Policy Server
2. Be sure that the XPSSecurity utility is located in policy_server_home/bin.

   policy_server_home

   Specifies the Policy Server installation path.

   Note: If the utility is not present, you can find it in the Policy Server installation media available on the Support site.

3. Open a command window and run the following command:

   XPSSecurity
   

   The main menu appears.

4. Type A and press Enter.

   The administrator menu lists the SiteMinder administrators in the external store. Each administrator is prefixed with a number.

5. Type the number of the administrator and press Enter.

   The administrator menu displays attributes specific to the administrator you chose. Each attribute is prefixed with a number.

6. Type 2 and press Enter.

   The administrator menu updates with flag settings.

7. Type a question mark (?) and press Enter.

   The Disabled and Super User flags appear. Each flag is prefixed with a number.

8. Type 2 and press Enter.

   The Super User flag is selected.

9. Type Q and press Enter.

   The administrator menu displays attributes specific to the administrator. The Flags attribute is set to Super User.

10. Type U and press Enter.

    The administrator record is updated.

11. Type Q and press Enter.

    The administrator menu lists the SiteMinder administrators in the external store. The administrator you chose appears as a super user.

12. Type Q and press Enter for the next two prompts to exit the utility.

    The administrator you chose is a super user. Use this administrator to restore modified or deleted permissions.

More information:

Locate the Installation Media

XPSSweeper

XPSSweeper is a command-line utility that can also be run as a batch job. You can use XPSSweeper to synchronize XPS and SiteMinder policy stores. Usually, XPS synchronizes the different policy stores. However, when legacy tools are used, the policy stores may need to be resynchronized using XPSSweeper. In any case, XPSSweeper does not harm the policy stores and can be run as a precaution.

Syntax

XPSSweeper has the following format:

XPSSweeper [-f] [-s seconds] [-m entries]
[-?] [-vT | -vI | -vW | -vE | -vF]
[-l log_path] [-e err_path]

Parameters

XPSSweeper includes the following options:

-f

(Optional) Runs XPSSweeper in a loop forever.

Note: Use Control-C to exit.

-s

(Optional) Sleeps for the specified number of seconds between iterations of XPSSweeper.

-m

(Optional) Outputs a milestone message every time the specified number of entries has been logged.

-?

(Optional) Displays help information for this utility.

-vT | -vI | -vW | -vE | -vF

(Optional) Specifies when to log error information to the error file and how much information to log.

-vT

Logs detailed information so that you can TRACE errors.

-vI

Logs INFOrmation in case there is an error.

-vW

Logs error information in the event of a WARNING, ERROR, or FATAL error.

-vE

Logs error information in the event of an ERROR or FATAL error.

-vF

Logs error information in the event of a FATAL error.

-l

(Optional) Outputs logging information to the specified location.

Default: stdout

-e

(Optional) Outputs error information to the specified location.

Default: stderr

Run XPSSweeper as a Batch Job

You can run XPSSweeper as a batch job by setting the following two XPS configuration parameters using XPSConfig:

CA.XPS::$Autosweep

Specifies whether to run XPSweeper according to the Autosweep schedule or not to run XPSSweeper at all.

Type: Boolean

CA.XPS::$AutosweepSchedule

Specifies the Autosweep schedule in GMT using the following format:

DDD@{HH:MM}[,DDD@{HH:MM}] ... [,DDD@{HH:MM}]

DDD

(Optional) Specifies the day of the week:

Sun | Mon | Tue | Wed | Thu | Fri | Sat

HH

Specifies the hour.

Range: 00-23

MM

Specifies the number of minutes past the hour.

Range: 00-59

Examples:

Sun@08:30

Every Sunday at 8:30am GMT

Tue@14:00

Every Tuesday at 2:00pm GMT

15:15

Everyday at 3:15pm GMT

Sun@08:30,Tue@14:00,15:15

Every Sunday at 8:30am, every Tuesday at 2:00pm, and everyday at 3:15pm except Tuesday

Note: Multiple Autosweep times can be separated by commas, spaces, or semicolons.

Policy Servers manage XPSSweeper Autosweep times as follows:

• XPSSweeper may run a few minutes off schedule because the cache check frequency is every several minutes.
• If XPSSweeper is already running when it is scheduled to run, it is not stopped and restarted, but allowed to finish the sweep process.
• XPSSweeper is not run more frequently than every two hours, even when scheduled.

  Example: If XPSSweeper is scheduled to run at 2:00pm on Tuesday and daily at 3:15pm, the latter sweep is not run on Tuesdays.