Specifying a bundled subscription
You can specify a bundled subscription by using the integration server.
Bundling subscription data for several users enables you to specify the same collaboration and messaging subscription for many users simultaneously. This provides an alternative to specifying user subscription and provisioning individually in the user provisioning change file or individually in the cloud user account.
HardBundle is a new subscription option for the most recent version of Integration Server that enables the provisioning of users for without activating all services at one time. The HardBundle subscription enables an administrator to provision users for IBM Connections™ Cloud S1 without activating all services at one time. Administrators can activate messaging, meetings, connections, and instant messaging independent of one another for their business users, eliminating the need to request customer service resource assistance.
You can specify a bundled subscription to both initially upload users in bulk, and to make changes to existing users. For some operations, you can change a user from a bundled subscriber to a single seat subscriber or a single seat subscriber to a bundled subscriber.
To initiate this user provisioning process, you must first request integration server enablement from your customer services representative and then configure your FTP site as instructed. See Requesting integration server enablement for details.
- Your organization's account contains a single subscription that includes the specified bundled subscription entitlements.
- Each user is provisioned as one seat in the bundle; that seat includes the designated Connections Cloud S2 and IBM SmartCloud Notes entitlements.
- All users are provisioned identically, for example you cannot provision some users with just IBM Connections Cloud S2 and others with IBM SmartCloud Notes.
Capture your bundled subscription information in the required CSV file format and upload the CSV file to the integration server. All user provisioning change file operations, as listed in the Creating user provisioning change files topic, support bundled subscriptions. Considerations that are specific to these operations for bundled subscriptions are as follows:
- Add and AssignSeat operations
- Use an Add or AssignSeat operation to add a user and assign a collaboration and/or mail subscriber (single seat) as a bundled user.
- ChangeSeat
- Use a ChangeSeat operation to replace a user’s
single seat subscription with a bundled subscription.
- If the user is subscribed to a collaboration service and a mail service, that user is swapped to the bundled subscription and their mail is preserved.
- If the user is subscribed to a single collaboration service, a
mail service, or a bundled subscription the following results occur:
- Target subscription is a bundled subscription
- If the user is subscribed to a collaboration seat and a mail subscription, the user is swapped to the bundled subscription and removed from their single seat subscription designation. Their collaboration subscription content (for example, data from Profiles, Files, and Communities) and mail data is preserved and is reassociated with their bundled subscription.
- Source subscription is a bundled subscription
- You can specify the source bundled subscription in one field and the target subscription as a new field in the ChangeSeat operation.
- The keyword values DELETECOLLAB and DELETEMAIL allow you to change a user from a bundled subscription to a single seat mail or collaboration subscription.
- Target subscription is a bundled subscription
- Remove and RevokeSeat
- These operations remove a user from the bundled subscription or
revoke the seat of a user within the bundled subscription.
- If no new user is listed, a RevokeSeat operation removes the user from the subscription but does not delete their mail or collaboration service data. The BUNDLE keyword is needed.
- If no new user is listed, a Remove operation removes the user from the subscription and deletes all their mail and collaboration service data.