When you install Access Gateway, it is automatically imported into Administration Console you specified during installation. If Access Gateway does not appear in the server list, repair the import.
If the repair option does not resolve the problem, see the following sections:
If Access Gateway does not appear in Administration Console within 10 minutes of installing an Access Gateway, perform the following steps:
If a firewall separates Administration Console and Access Gateway, ensure that the required ports are opened. See Table 1-3.
Click Devices > Access Gateways.
Wait for a few minutes, then click Refresh.
If the device import fails, a message similar to the following appears at the bottom of the table:
Server gateway-<name> is currently importing. If it has been several minutes after installation, click repair import to fix it.Click repair import.
If the device still does not appear or you do not receive a repair import message, continue with Triggering an Import Retry.
If triggering an import retry does not solve the problem, reinstall the device.
If the import process does not complete successfully, the device does not show up in the Access Gateway list. The following sections describe the import process, where to find the log files, and how to use them to determine where the failure occurred:
The following operations are performed during the import process:
A user specifies the IP address for Administration Console during installation.
A Java process called “JCC” (Java Communication Channel) detects that Administration Console IP address or port has changed between its own configuration and the CLI-updated settings.
An import message is sent to Administration Console, notifying it of the IP, port, and ID of Access Gateway.
Administration Console then connects to the Access Gateway device to fetch its configuration and version information. The Access Gateway import process is now complete.
As a separate asynchronous operation, the Embedded Service Provider (ESP) of Access Gateway connects and registers itself with the JCC.
When the ESP connects to the JCC, a similar import message is sent to Administration Console notifying it to import into the system.
Administration Console connects to the JCC, asking for the ESP configuration and version information. On Administration Console, an LDIF (Lightweight Directory Interchange Format) file containing the default configuration for the ESP is applied on the local eDirectory configuration store.
Administration Console then makes a link between the ESP and its configuration.
If the entire process completed properly, Access Gateway appears in the list of Access Gateways in Administration Console.
Various Access Manager components produce log files. Use the following logs on Administration Console or Access Gateway:
Administration Console log: /opt/novell/devman/share/logs/app_sc.0.log
Tomcat Log on Administration Console: /opt/novell/nam/device name/logs/catalina.out
The device name can be idp, mag, or adminconsole.
JCC log on Access Gateway: /opt/novell/devman/jcc/logs/
Go to the /opt/novell/devman/jcc/ directory:
Run the sh conf/reimport_ags.sh jcc script.
Specify details against the following prompts:
Choose a local listener IP address [x.x.x.x]:
(Optional) Choose a local NAT IP address [optional]:
Choose Administration Console’s IP address []:
Enter Admin User’s DN [cn=admin,o=novell]:
Enter Admin Password: *****
Wait for a few minutes for the configuration to finish.
Run the sh conf/reimport_ags.sh agm script.
For example, if the username is admin, then run conf\reimport_ags.bat agm admin
Specify details against the following prompts:
(Linux) Do you want to import the device with current configuration or initial configuration after installation (Enter C for current configuration, I for initial configuration).
(Linux) Enter Admin User’s DN [cn=admin,o=novell]:
Enter Admin password: