IDM Driver movements
16/10/07 18:45 Filed in: Novell
In preperation for using the Entitlements driver in
our IDM solution I had to restrict our driverset to a
single server (version 3.5 of IDM overcomes this
restriction but I was also trying to streamline).
This meant moving the GroupWise driver from one
server to another. There are a number of ways to do
this but ultimately they involve, exporting the
driver, deleting the driver, importing the driver
specifying another server and then deleting the
superfluous server from the driverset. You can do
this with Designer, but I've not taken a liking to it
yet and prefer to use iManager. Before doing any work
with the driver, install the GW components on the new
recipient server.
To export the driver with iManager do the following:
1. Browse to the driver set and click on the driver in question
2. Select export and follow the prompts, exporting to an xml file on your PC
3. Once exported, delete the driver from the driverset
Import the Driver back into the driverset
1. Now that it's gone, we need to import it back in. Import the driver back into the same driverset selecting the other server and following the prompts
2. Because in my case the GW driver is not on a server other than the primary domain database, we have to specify a user account with RWCEMFs rights to the Domain DB. We also need to specify the IP address of the GW server and the path to the Domain DB.
3. Start the driver
NB: if you're running the IDM drivers on a Netware server, make sure you add a search path for the GW driver components before starting the driver. I add the following line up high in the AUTOEXEC.NCF file.
SEARCH ADD SYS:\SYSTEM\GWDRIVER
Once added to the AUTOEXEC.NCF file, type the same line at the console and press ENTER.
Because we didn't change the name of the driver in the driverset all associations remain current.. so no need for the driver to go off madly reassociating objects.
The final step is to delete the old server from the driver set.
1. Click on the IDM overview in iManager and then select the red X next to the server list.
2. Select the server about to be removed from the driverset and click apply.
3. Done. Go grab yourself a coffee.
FINAL NOTE: Run this process through your test environment. iManager crashed on me during test which cause a few skipped heartbeats. Plus I forgot to add the search line on the recipient server which accounted for a couple more.
To export the driver with iManager do the following:
1. Browse to the driver set and click on the driver in question
2. Select export and follow the prompts, exporting to an xml file on your PC
3. Once exported, delete the driver from the driverset
Import the Driver back into the driverset
1. Now that it's gone, we need to import it back in. Import the driver back into the same driverset selecting the other server and following the prompts
2. Because in my case the GW driver is not on a server other than the primary domain database, we have to specify a user account with RWCEMFs rights to the Domain DB. We also need to specify the IP address of the GW server and the path to the Domain DB.
3. Start the driver
NB: if you're running the IDM drivers on a Netware server, make sure you add a search path for the GW driver components before starting the driver. I add the following line up high in the AUTOEXEC.NCF file.
SEARCH ADD SYS:\SYSTEM\GWDRIVER
Once added to the AUTOEXEC.NCF file, type the same line at the console and press ENTER.
Because we didn't change the name of the driver in the driverset all associations remain current.. so no need for the driver to go off madly reassociating objects.
The final step is to delete the old server from the driver set.
1. Click on the IDM overview in iManager and then select the red X next to the server list.
2. Select the server about to be removed from the driverset and click apply.
3. Done. Go grab yourself a coffee.
FINAL NOTE: Run this process through your test environment. iManager crashed on me during test which cause a few skipped heartbeats. Plus I forgot to add the search line on the recipient server which accounted for a couple more.