Sun Identity Manager 8.1 Resources Reference


Use the Identity Manager debug pages to set trace options on the following classes:

The hostAccess object may be traced in Identity Manager. The class to trace through the debug pages is com.waveset.adapter.HostAccess. Trace level 3 is sufficient to identify which keystrokes and wait messages were sent to the mainframe; trace level 4 will display the exact message sent and the response from the mainframe.

Note –

Verify that the Trace File location is meaningful. By default the trace file is placed in the application directory under InstallDir/idm/config. If the application is deployed from a WAR, the path may need to be hard-coded with an absolute directory path. In a clustered environment, the trace file should be written to a network share.

In addition to source tracing, it may also be useful to log the screen text before each attempt to send keystrokes. This can be accomplished through a file writer. The sequence of commands is:

ProcedureLogging Screen Text Before Each Attempt to Send Keystrokes

  1. var file = new”<filename>’);var writer = new;writer.write(hostAccess.getScreen());writer.flush();

  2. hostAccess.sendKeysAndWait(<cmd>,<msg>);

  3. writer.newLine();

  4. writer.write(hostAccess.getScreen());

  5. writer.flush();

  6. writer.close();

    <filename> should reference a the location of a file on the local file system of the application server. The writer will open a handle to that location and write what is stored in it’s buffer when the flush() method is invoked. The close() method releases the handle to the file. The getScreen() method is useful to pass to this function to get a dump of the screen contents for debugging purposes. This tracing should, of course, be removed once the screens are successfully navigated and login / logout is performed successfully.