Problem:
Many users have requested information on running XDB configuration utilities in batch mode to deploy to multiple machines. Everything documented below assumes that the product is MFE 3.0 or 3.1
Resolution:
XDB Server Configuration Utility - srvcmfe.exe
If you would like to configure one server and then clone the settings to all other servers:
To dump the server settings to a file,
1) Start a MFE command prompt
2) Type "srvcmfe generatefile=path", where path is the full path of the file that settings will
be placed.
To use the file generated by srvcmfe.exe:
1) You can edit the setting file you would like to use in an editor.
2) At a MFE command prompt, type "srvcmfe usefile=path"
Make sure if you are cloning you remove the EngineOptions.ServerName setting so you don't modify every server to have the same name. This would cause problems with the XDB WinLocal protocol which is based upon "Named" pipes.
The following information is specific to Citrix/WTS users. What used to known as the "blue screen" head (XSRV40N) is now replaced by what we refer to as the "headless" head (XSRVN) in MFE 3.1. In Citrix/WTS environments, you have the option of running multiple headless heads or connecting to the service server as a system wide server. If you are running GUI Server Configuration Utility in Citrix/WTS environments, the radio buttons labeled "Type" will default to the "personal" server settings. Outside of Citrix/WTS environments, the GUI configuration tool will grey out the radio buttons since there will be no distinction between a personal server and a system wide server. In a srvcmfe-generated file, the "Type" option looks like the following,
EngineOptions.Type = SYSTEM-WIDE or
EngineOptions.Type = PERSONAL
Make sure EngineOptions.Type is set to "PERSONAL" if you are trying to configure individual personal servers on a Citrix machine.
You can access the GUI usage information by typing "srvcmfe usage"
Gateway Profile Utility - gprf40n.exe
Similarly, you can clone XDB Link configuration with the following:
To generate a setting file,
gprf40n generatefile=path username=name [password=password]
To use a output file generated by gprf40n.exe
gprf40n usefile=path username=name [password=password]
Please note that username is a required argument for Gateway Profile Utility as it needs to actually log into the XDB server to acquire some of the settings.
Type "gprf40n usage" for complete usage information
XDB Batch Options - bopt40n.exe
Client side settings can be modified using BOPT40N. You may wish to allow users to customize certain settings. Therefore, you probably don't want to just "push" an XDB.INI into a user's environment. It's easier to use BOPT40N to just modify the settings you want to standardize on.
To generate a setting file:
bopt40n /g path
To use the file generated:
bopt40n /u path
where path is the full path of the setting file.
To access help text: bopt40n /h
I have attached a zip which contains sample settings file generated by the three utilities (srvmfe.settings, gprf40n.settings and bopt40n.settings).
As the usage information/help text on these utilities has made apparent, the settings in the files generated by those three utilities can be also specified as individual arguments right on the command line. This comes in handy when you just want to adjust a couple of settings.
For example,
This command sets the server XDB engine version to DB2V8
srvcmfe EngineOptions.DB2Version = DB2V8
This command changes the Collection ID used with location UDB_81_OS390 to "LNKSYS"
gprf40n USERNAME = INSTALL Connection.LocationName = UDB_81_OS390 DRDASetup.CollectionID = LNKSYS
Command line arguments for BOPT40N have more variances than the help text shows.
This bopt40n command changes current location to UDB_81_OS390 and turns on client side security
bopt40n "/pConnection ROCKJENN.CurrentLocation=UDB_81_OS390" "/pSecurity.ClientSecurity=On"
Or alternatively,
bopt40n -p "Connection ROCKJENN.CurrentLocation=UDB_81_OS390" -p "Security.ClientSecurity=On"
Attachments:
#MFDS
#EnterpriseDeveloper
