GWAVACon 2015: Open Horizons - How to convert a GroupWise user into a resource

24.09.2015
@ copyright Diethmar Rimser 2015 1 1
How to Convert a GroupWise
User into a Resource
Diethmar Rimser
Paul Van der Cruyssen
© Open Horizons. All rights reserved. Diethmar Rimser 2015, 2
About this Session
There are two types of mailboxes: GroupWise users
and GroupWise resources with different properties
and different organisational background.
Sometimes there is a request to convert into another
object type because of business needs.
A small showcase has been prepared to show how to
convert a user mailbox into a resource mailbox in a
GroupWise 2014 environment using ReST API.

24.09.2015
Agenda
● Background
● Tay Kratzer’s legendary paper
● GroupWise: user and resource mailbox
● Why to convert?
● GroupWise 2014 is different!
● HTML based administration tool
● gwadminservice
● ReST API
● Our way to follow Tay’s idea
● Demo
● Conclusion
Background

24.09.2015
Tay Kratzer’s Paper
It’s a long time ago …
Original title: “Converting a GroupWise User Mailbox To
a GroupWise Resource Mailbox”
A very informational description of GroupWise mailbox objects
Enhanced explanation of mailbox databases
Tricky use of ConsoleOne (therefore for GW2012 and older)
Just “legendary”
Tay Kratzer
Well known GroupWise guy – knows GroupWise in detail
Author of GroupWise books
“Father” of Gwava Reload
User Databases
Excerpt from original documentation
Each member of the post office has a personal database
(userxxx.db) that represents the user’s mailbox. The user
database contains the following:
• Message header information
• Pointers to messages
• Personal groups
• Personal address books
• Rules
Local user databases and prime user databases are stored in the
ofuser folder in the post office.
Because resources are addressable just like users, resources
also have user databases.

24.09.2015
GroupWise: User and Resource
Users and Resources are very similar
• Mailboxes contain the same type of data
• Mails, appointments, tasks, address books, …
• Shares, proxy rights work in the same way
• … even options and properties
• But
• Resources need an owner!
• Owner has full proxy rights
• Internet address is resource.resource@internet-domain.
Why to Convert?
• User has left the company
• but his mailbox contains a lot of important information
• but he is owner of many shares
• Deletion is not the right solution
• GroupWise Archive is not the right solution
• Conversion?
• No loss of information
• No loss of internal behaviour (shares, proxies, …)
• Reduced license costs

24.09.2015
Tay‘s Idea
• Mailbox(=user) databases for users and resources are
working in the same way.
• Some thoughts:
• So if we create a resource using the old, original user
database …
• We should not lose the old user database!
• Is there a way to change the file id for a user or a resource?
• Maybe if ConsoleOne does not “understand” GroupWise?
Tay‘s Way for Conversion
• Find out the according FID (i.e. „XYZ“)
• Rename the respective „XYZ“ user database
• Check if the post office agent (POA) feels it
• Delete that user in ConsoleOne
• Create a resource
• Assign the file id „XYZ“ to this resource using some
weird ConsoleOne behaviour
• Rename the “XYZ” user database back to its original
name

24.09.2015
GroupWise 2014 is Different!
• No ConsoleOne!
• Tay‘s concept will not work …
• GroupWise Administration Console
• The GroupWise Administration console is a web-based
administration tool that provides convenient access to your
GroupWise system in your web browser. Your web browser
can connect to the GroupWise Administration Service on any
domain server (excerpt from original documentation)
• New tool – new procedure!
GroupWise 2014 - gwadminservice
• Runs next to other agents
• Listens usually on port 9710
• Accepts ReST API calls
• ReST API = Representational State Transfer API
• GroupWise SDK: Administration REST API Guide
• See: https://server:9710/gwadmin-service

24.09.2015
Our Way to Follow Tay‘s
Idea
Conversion Idea for GW2014
Mailbox(=user) databases for users and resources are
working in the same way.
Some thoughts:
So if we create a resource using the old, original user
database …
• We should not lose the old user database!
• Is there a way to change the file id for a user or a resource?
• Or is there a way to create a resource with a “requested” file
id?
• Does ReST API offer this possibility?

24.09.2015
Conversion Steps for GroupWise 2014
• Find out the according FID (i.e. „XYZ“)
• Rename the respective „XYZ“ user database
• Check if the post office agent (POA) feels it
• Delete that user
• Create a resource with file id “XYZ” using ReST API
• Rename the “XYZ” user database back to its original
name
The Day Before
If you have to convert a user into a resource then take care of
following conditions.
• This user must not be owner of resources. (Move resource
ownership to other users)
• He must not be administrator of GroupWise distribution lists.
• He must not be administrator of post offices, domains or your
system (GW2014 feature)
• He must not be librarian in your GroupWise DMS (document
management system).
• Check if all the rules fit to the behaviour of a resource instead of
user (Reply rules, …).
• Check if membership of distribution lists is still reasonable.

24.09.2015
My Conversion: User aeinstein
I will convert user
aeinstein, Albert Einstein
to resource
resource1, owner: admin
File Id - FID

24.09.2015
Rename User Database & C05D
mv user5da.db user5da.bak
Curl Script for Creating a Resource
with Predefined FID
curl -k --user admin:password
https://server:9710/gwadmin-service/domains/dom
/postoffices/po/resources -H "Content-Type:
application/json" –X POST -d ’{"name": "resource1",
"fileId": "abc","owner": "owner1"}’
• Replace the word admin with the userid used to login to Administration
Console.
• Replace password with the admin’s password
• Replace https://server:9710 with the URL of the Administration Console
• Replace dom with the domain name
• Replace po with the post office name
• Replace resource1 with the resourceid to be created
• Replace abc with the FID to be assigned
• Replace owner1 with an existing userid of the same post office.

24.09.2015
Create resource1 with FID „5db“
curl -k --user admin
https://172.16.2.254:9710/gwadmin-
service/domains/do1/postoffices/po1/resources -H
"Content-Type: application/json" -X POST -d
'{"name":"resource1", "fileId": "5da","owner":
"admin"}'
Rename User Database Back to
Original Name & Access Resource
mv user5da.bak user5da.db

24.09.2015
The Day After
• All shares will survive! The (new) owner of the
resource has the ability to add, delete and configure
these shares and add new one.
• Maybe the user who has been converted to a
resource has been proxied by other users. These
proxy rights will still exist.
• But if you changed the original name into a different one then you
have to search for the new name before you can proxy.
• The owner of the resource is able to access the
resource’s archive.
Demo

24.09.2015
Conclusion
Conclusion
Follow the steps strictly!
Conversion with GroupWise 2014 is easier and without
tricky activities.
A good example how powerful ReST API can be.
A conversion in both directions is possible.

24.09.2015
A Short Session here,
but an Advanced
Workshop at Our
OH Summit!

GWAVACon 2015: Open Horizons - How to convert a GroupWise user into a resource

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Andere mochten auch

Andere mochten auch (20)

Ähnlich wie GWAVACon 2015: Open Horizons - How to convert a GroupWise user into a resource

Ähnlich wie GWAVACon 2015: Open Horizons - How to convert a GroupWise user into a resource (20)

Mehr von GWAVA

Mehr von GWAVA (16)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

GWAVACon 2015: Open Horizons - How to convert a GroupWise user into a resource