• Anonymous
  • Login
  • Register
DST Fix TooL

Owners Shawn Haybron Category
Admin Utilities
Contributors - Platform
R 8.5.2
Downloads 71 Last Release Feb 22, 2007
Rating
(0 ratings)
Project Creation Feb 22, 2007
Status Not active Short URL Not defined
Description Iterates through Mailfiles to Correct incorrect DST Calendar Entries In Catalog
No


I have Created a DST Centralized Fix TooL which allows you to import all users into the TooL either from your NAB via LotusScript and/or import from a spreadsheet in .wk3 format. Once these Person Documents are in in the TooL from your NAB you can then scan their mailfiles to pull their Template, client type (Pulled from $Mailer on documents in $Sent view). In our Case this is helpful for running the Agent first on just ND6/ND7 Template based mailfiles and then to selectively run the Agent on R5 Based mailfiles.

You can then selectively Queue Person Documents to have the TooL Process. This TooL should be run from a ND6 or ND7 client on a semi-beefy workstation using an ID file that has at least Editor Access to all Mailfiles you plan to process. This TooL WILL cross Servers but processes users in the following Sort Order: 1st by Server then by Mailfile Path.

Example: The tool will process all users on AServer/SVR/Co starting with first mailfile mail/aamailfile.nsf and then process all users on BServer/SVR/Co starting with first mailfile mail/aamailfile.nsf and finishing on mailz/zzmailfile.nsf.

This TooL uses a mildly modified/streamlined version of the IBM "Centralized" Agent provided. Some of the minor tweaks and modifications allow use of Documents in the TooL Database instead of a .txt file located at the root of the Server. This TooL also allows you to select which users you Proccess at any given time. To run the TooL you must first edit the Global Profile Document. You do this by going to the Administration--> All Documents View and clicking the "Edit DB Profile" button. There you will need to specify the NAB Server and NAB File Path. This is the NAB from which you will import your users and update documents as

I still have some work to do to embetter the logging and error trapping. This Version 2 now includes Documentation via Using/About Docs and thus, this TooL is production ready for those of you who want to start testing/using it. You will want to Sign the entire Template with your own Trusted ID and alter the ACL to include your own particular Admin Groups and Inheritance Admin/User Groups before creating the Active DB from it. The TooL does not use any Roles (yet) and likely won't need them. You may elect to alter/change/rebrand this TooL at your leisure, just as long as you throw a Bone to it's creator: Shawn Haybron of Columbus Ohio.


Projects can have short and readable URLs, e.g. http://mobilecontrols.openntf.org.

You can request a short URL to your project by sending a mail to support at openntf dot org. Put the word 'OpenNTF' somewhere in the subject.
Owners are the people with maximal rights. For example they can create releases and add more contributors.

In order to define multiple owners use "," (comma) as separator.

Because of data privacy you cannot lookup other people's names but you have to type them in.
Enter the contributors or owners here who you want to receive notifications and questions by email.

In order to define multiple owners use "," (comma) as separator.

Because of data privacy you cannot lookup other people's names but you have to type them in.
In addition to the owners additional OpenNTF contributors have to be listed here. Contributors don't have the same access rights as owners, e.g. they cannot create releases.

In order to define multiple owners use "," (comma) as separator.

Because of data privacy you cannot lookup other people's names but you have to type them in.
Enter a short description of the project here (up to 100 characters).

The short description shows up in the project UI and in some of the views.
In this field you should enter a more detailed description of your project.

You can use the rich text editor for rich text formating. You can also enter HTML to embed objects, e.g. to embed a YouTube video or a screenshot of the project. In this case use '[' and ']' to mark the passthrough HTML as such.

Please note that the first time you use the new UI your description is converted from rich text to MIME. You might want to copy and paste the raw plain text from the old UI in the new UI so that you don't loose information.
A Catalog Release is for projects that are production ready and that are end-user "install friendly".

This property describes whether any release of this project has been added to the catalog.

Learn more about the catalog.