The Maximo® Asset
Management configuration
program can automatically configure middleware. You must enable a
remote access protocol for each system on which you intend to configure
the middleware.
Use SSH for accessing remote Linux and UNIX systems.
Use Windows SMB
accessing remote Windows systems. Windows SMB
is a Windows protocol.
The IBM JRE on the Maximo Asset
Management administrative
workstation includes SSH.
Before you start the Maximo Asset
Management configuration
program, ensure that you can log on to any remote servers with the
protocols that you intend to use. Use the credentials that you plan
to supply to the Maximo Asset
Management configuration
program.
For remote
Windows systems,
ensure that the following requirements are met before you configure
the software.
- The user name that you provide to the Maximo Asset
Management configuration
program must exist as a local account on the remote system. This user
must be a member of the Windows Administrators
group.
- The following Windows services
must be started on the remote system before you begin a remote configuration:
- winmgmt (Windows Management
Instrumentation)
- RemoteRegistry (Remote Registry)
- lanmanserver (Service)
- The SMB protocol must be enabled and configured to send NetBIOS
over TCP/IP, by choosing to use port 139. Alternatively, you can configure
SMB to use TCP/IP as the transport protocol, without NetBIOS, by configuring
it to use port 445.
- Ensure that any ports that you use for remote protocols are not
blocked by firewall software or security policies, including ports
137 and 139. Port 139 is used if SMB is configured to run on NetBIOS
over TCP/IP. Port 445 is used if SMB is run directly on TCP/IP, without
NetBIOS.
- To disable simple file sharing, start Windows Explorer.
Click , and clear the Use Simple File Sharing check
box.
- The Windows administrative
share (C$) and the interprocess communications (IPC$) folder must
be shared.
- For Microsoft Windows Server
2008 systems
that support password-protected sharing, disable password-protection.
Shares must be shared for the Guest or Everyone accounts.
- For Windows systems
that have User Account Control (UAC) enabled, it must be disabled
before software can be remotely installed and configured.
- If Cygwin is installed on the remote Windows system
the SSH daemon (sshd) must be uninstalled or disabled.
For remote
Linux or
UNIX systems,
ensure that the following requirements are met before you configure
the software.
- For AIX® systems,
set the following SSH parameters in the /etc/ssh/sshd_config file.
- ClientAliveInterval 900
- ClientAliveCountMax 10
Stop the SSH daemon with the stopsrc -s sshd command
and then restart it using the startsrc -s sshd command.
- For AIX systems,
set the TMOUT and TIMEOUT variables
in the user profile script to 0. This setting prevents the user from
idling out and being logged off the remote system during the configuration.
- The user name that you provide to the Maximo Asset
Management configuration
program must exist as a privileged account (for example, root) on
the remote systems.
- Ensure that a current version of OpenSSH is installed and running.
Do not use OpenSSH 4.7.0.5302.
- For Oracle Solaris systems,
the remote access protocols require the use of internal shell scripts
that must be run within the Korn (ksh) shell. The methods need ksh,
even if the user ID that you use to log on to the remote system is
configured to use a different shell. Oracle Solaris systems
must have the ksh environment installed and properly configured.
- If you plan to remotely configure software on remote Linux or UNIX computers,
ensure that SSH is installed.
Remote configuration does not support accessing network drives
on the local or remote system.