How to Sandbox an Assemblyline in Tivoli Directory Integrator

Technote (FAQ)


Question

How should one configure an Assemblyline to be captured by the Sandbox feature made available in Tivoli Directory Integrator?

Cause

* Someone encounters a problem while developing an assemblyline in a closed environment. They need your help in debugging the Assemblyline, although aren't able to give you network access to the back-end systems which the connectors are communicating with.
* You have a resource which isn't always available on the network.
* You want to debug an Assemblyline without having connectivity to the Company's network.

Answer

By using the Sandbox feature included with the TDI Server, you're able to create a repository of the source which the Assemblyline interfaces with. With the Sandbox and the Assemblyline, you can run the TDI Server and debug the Assemblyline on a laptop without connectivity to the back-end resources.




NOTE: The Sandbox facility is not supported in AssemblyLines containing a Connector in Server mode, or an Iterator Connector with Delta enabled. The server will abort the running of the AssemblyLine if this is discovered.


Setup:
Define which resources you want captured in the Sandbox



The 'Database' name is the location used to store the Sandbox data. This name will be used to create a directory in your Solution directory. In this panel, we also define which resources we want available to Record and to Playback.







Record Mode:
On the initial run of the Assemblyline, you will have the Assemblyline's Run Mode set to ' Record'. This is done in the ' Specify Run Options' panel.






You'll see the following statement on the 'Record' run of the Assemblyline.
  • CTGDIS256I AssemblyLine AssemblyLines/'AL_Name' is started, recording to: 'Sandbox_Database_Name'.
  • You'll see the 'Database name' defined in the 'Sandbox Settings' panel appear as a directory in the Solution Directory.




NOTE: When you want to redirect the connector to using 'live' data, the Run Mode should be returned to 'Run'.




Playback Mode:
Now set the Run Mode of the Assemblyline to ' Playback'. Instead of the Assemblyline accessing the Active Directory as defined in the connector...the connector is simulated during playback. Now the Connector which you Sandboxed, has a copy of the source which will be referenced when the Assemblyline executes.


When the Assemblyline starts, you'll see the following line at the beginning of the ibmdi.log file.
  • CTGDIS257I AssemblyLine AssemblyLines/'AL_Name' is started, playing back from: 'Sandbox_Database_Name'.

NOTE: When you want to redirect the connector to using 'live' data, the Run Mode should be returned to 'Run'.


Portability of the Sandbox:
Portability is one of the benefits of the Sandbox. You are able to hand a few resources to another person and they'll be able to run the Assemblyline without any of the back-end resources/repositories. To move the Sandbox, do the following:

  • Place a copy of the 'Sandbox' directory into the 'Solution_directory' on the other machine.
  • Import a copy of the TDI Eclipse Project or TDI Config XML into the other machine.
  • When you run the Assemblyline, have the Run Mode of 'Playback' selected in the 'Specify Run Options' panel.



FYI: The table/view created in the Derby database held in the Sandbox directory is linked to the name of the Assemblyline. Don't rename the Assemblyline once the Sandbox recording has occurred.
  • CTGDIS084I Initialization of ActiveDirectoryChangeDetectionConnector failed: java.lang.Exception: [ActiveDirectoryChangeDetectionConnector] CTGDIS025E Exception while loading configuration: java.lang.RuntimeException: CTGDIS593E Internal IDI proxy object exception: Table/View 'ASSEMBLYLINES_AD_DOMINOA_ACTIVEDIRECTORYCHANGEDETECTIONCONNECTOR' does not exist.

Related information

InfoCenter Documentation for the Sandbox feature

Rate this page:

(0 users)Average rating

Document information


More support for:

IBM Security Directory Integrator
General

Software version:

7.1, 7.1.1

Operating system(s):

All Platforms

Software edition:

All Editions

Reference #:

1511937

Modified date:

2013-02-21

Translate my page

Machine Translation

Content navigation