This section explains how to install the Systemwalker Single Sign-On Agent.
Install the Systemwalker Single Sign-On Agent by executing the following F4AMsetup command (the command for setting up the Systemwalker Single Sign-On function).
Execute this command only once even if multiple Systemwalker products have been installed.
F4AMsetup -i -p <installed product name> -s -o SSO |
The following tables show the execution and storage locations of the F4AMsetup command, and the parameters to specify for the names of the installed products.
[Command execution location]
Systemwalker product name | Installation type |
|---|---|
Systemwalker Centric Manager | Operation Management Server |
Systemwalker Service Quality Coordinator | Operation Management Client |
[Storage location]
OS | Location |
|---|---|
Windows | %F4AM_INSTALL_PATH%\F4AMidmg\client\setup |
UNIX | /opt/FJSVswaic/client/setup |
[Parameters to specify for the names of the installed products]
Systemwalker product name | Parameters to specify for the names of the installed products |
|---|---|
Systemwalker Centric Manager | SWCMGR |
Systemwalker Service Quality Coordinator | SWSQC |
Refer to the "F4AMsetup (Systemwalker Single Sign-On Function Setup Command)" for details on the F4AMsetup command.
Point
If you wish to install a Systemwalker Single Sign-On Server or Interstage Application Server after a Systemwalker Single Sign-On Agent has been installed, uninstall the Systemwalker Single Sign-On Agent first.
Customizing IPC key values for System V IPC resources
The Systemwalker Single Sign-On Agent uses the System V IPC resources provided by the operating system (message queues, semaphores and shared memory resources) to communicate between processes.
These IPC resources are identified uniquely within the system by values (known as IPC key values) that are specified when the resources are created.
IPC key values must be unique within the system, but arbitrary values can be used, which means that the values sometimes conflict with the values used by other products or applications that use IPC resources.
If an IPC key value conflict occurs, the Systemwalker Single Sign-On Agent will notify the user of this fact by outputting the following message.
[Message]
SSO: ERROR: sso00205: Could not get IPC resource due to duplicated key. ServerKind=(%s1) Kind=(%s2) Id=(%s3) Detail=(%s4) Code=(%s5)
[Variable information]
%s1: Server name or command name
%s2: Server type
%s3: Job Server ID0
%s4: Maintenance information
%s5: Maintenance information
In this case, the functions of the Systemwalker Single Sign-On Agent services that use the IPC resources corresponding to these IPC key values cannot be used.
To resolve this kind of situation, the IPC key values used by the Systemwalker Single Sign-On Agent can be customized using the method shown below. Taking this action makes it possible to operate the Systemwalker Single Sign-On Agent when a message is output notifying that an IPC key value conflict has occurred.
IPC key values are made up of four bytes (32 bits), but arbitrary values can be defined for the low-order 12 bits (three hexadecimal digits) so that they do not conflict with the IPC key values used by other products. Note that the remaining high-order 20 bits are determined by the Systemwalker Single Sign-On Agent.
Create a new definition file for the IPC key values as follows, and specify the low-order 12 bits of the IPC key values using three hexadecimal digits.
Define the IPC key values so that they do not conflict with other values on the system.
Note that if the definition file contains anything other than three hexadecimal digits, the Systemwalker Single Sign-On Agent will operate in the same way as it would if IPC key values were not specified.
[Common definition file]
OS | Common definition file |
|---|---|
Solaris | /var/opt/FJSVisas/system/default/FJSVisas/etc/ipc_key |
Linux | /var/opt/FJSVisas/system/default/FJSVisas/etc/ipc_key |
Example:
If the definition file is created as below and the high-order 20 bits used by the Systemwalker Single Sign-On Agent are set to "0x01280", the IPC key values will be "0x01280FFF" when displayed in hexadecimal.
FFF |
