Difference between revisions of "Retain Stubbing Server"
(→Why Stubbing May Not Work for Your System) |
(→Why Stubbing May Not Work for Your System) |
||
| Line 11: | Line 11: | ||
===Why Stubbing May Not Work for Your System=== | ===Why Stubbing May Not Work for Your System=== | ||
| − | *Stubbing CANNOT be reversed. (Once a message is stubbed, it cannot be returned to the same | + | :*Stubbing CANNOT be reversed. (Once a message is stubbed, it cannot be returned to the same position in the system). |
| − | position in the system). | + | :*User training for stubbed items may be necessary due to decreased access speed. |
| − | *User training for stubbed items may be necessary due to decreased access speed. | + | :*No method for protecting stubs from deletion in the GroupWise client (re-creation is difficult and complicated). |
| − | *No method for protecting stubs from deletion in the GroupWise client (re-creation is difficult | + | :*Non-mail items should not be stubbed (calendar and appointment items behave erratically when rescheduled). |
| − | and complicated). | + | :*Stub items are NOT COMPATIBLE with third party APIs. These applications view the stubs as posted items only, with no text or attachments. Mobile, Web, IMAP, and POP3 clients will only see posted empty items, not actual contents. |
| − | *Non-mail items should not be stubbed (calendar and appointment items behave erratically | + | |
| − | when rescheduled). | + | |
| − | *Stub items are NOT COMPATIBLE with third party APIs. These applications view the stubs as | + | |
| − | posted items only, with no text or attachments. Mobile, Web, IMAP, and POP3 clients will only see posted empty items, not actual contents. | + | |
Determine the correct option for your system. If you wish to enable Stubbing, you need to install and configure the Stubbing Server as well. | Determine the correct option for your system. If you wish to enable Stubbing, you need to install and configure the Stubbing Server as well. | ||
Revision as of 23:18, 5 March 2014
Contents |
Level 1
Stubbing is a new feature in GroupWise 8, where a message item may be "stubbed" -- removing the message permanently from GroupWise, and replacing it with an item (a stub) that connects to Retain to access the message. Effectively, the user has transparent access to the stubbed item from their GroupWise client and the stub behaves largely as if a native GroupWise item was still there.
Before enabling stubbing, make sure you understand the way stubbing works and how that will work in your system because once enabled, you cannot reverse the stubbing process. Plan your system and understand the positive and negative sides to Stubbing before you continue. To use stubbing, it is strongly recommended that the GroupWise system be at least 8.02HP1. Previous versions of GroupWise do not contain critical stability fixes.
Why Stubbing Is Good
- Save Disk space. Mail can be removed from the system without being deleted.
- Users have easy access to items stored in Retain
- Transparent access, no need to login to Retain for common tasks.
Why Stubbing May Not Work for Your System
- Stubbing CANNOT be reversed. (Once a message is stubbed, it cannot be returned to the same position in the system).
- User training for stubbed items may be necessary due to decreased access speed.
- No method for protecting stubs from deletion in the GroupWise client (re-creation is difficult and complicated).
- Non-mail items should not be stubbed (calendar and appointment items behave erratically when rescheduled).
- Stub items are NOT COMPATIBLE with third party APIs. These applications view the stubs as posted items only, with no text or attachments. Mobile, Web, IMAP, and POP3 clients will only see posted empty items, not actual contents.
Determine the correct option for your system. If you wish to enable Stubbing, you need to install and configure the Stubbing Server as well.
If you wish to only stub large items in your mail server, you may set a size threshold. Any item larger than the specified size will be stubbed. If this option is not set, all messages will be stubbed regardless of size.
Configuration
Stubbing Server Interface
Open a new browser tab or window and go to the Stubbing Server. The Stubbing Server answers to http://[IP address of StubServer]:48080/RetainStubServer (the address is case sensitive).
- Click ‘Browse’ and browse to the location where you saved the bootstrap file.
- Select the “StubConfig.cfg” file and select ‘Open’.
- Select the ‘Upload File’ button. After uploading the configuration file, the Stub Server will alert you that it requires authentication from a user with the “Manage Workers” right. Click ‘Continue’.
You can now login to the Stub Server. You must login with a user that has sufficient rights. See the User Rights section to add or remove rights. The Stub Server Interface is nearly identical to the Worker interface. You may check for updated versions of the Stub Server or manually trigger server polling by selecting the Refresh ‘Configuration now’ button.
Check the Server Connection tab to verify the connection to the Server.
Status
The Status tab gives statistics about up-time and function.
Scheduler
The scheduler tab contains the configuration details sent by the Server. This tab is mainly used for Support.
