Direct Link Operation Flow

This section describes different scenarios in which direct links are used to embed UCMDB applets into external machines.

Regular Login

This flow describes a regular login to the Universal CMDB server. It serves as a base reference for the direct link flows.

1. The user enters the direct link URL (into the browser) to log into the Universal CMDB server.

2. The browser sends the login request to the Universal CMDB server.

3. The server checks the user credentials and creates a user session if required.

4. The server returns the requested first page of Universal CMDB.

5. The browser loads the Java virtual machine (JVM) with the code base location parameter (which instructs the JVM from where to load the UCMDB applet files) as the Universal CMDB server.

6. UCMDB applet files (jars) and data are transferred between the Universal CMDB server and the JVM loaded in the browser.

At this point, the UCMDB applet is loaded and regards Universal CMDB as the server with which it should communicate.

An Embedded UCMDB Applet Using a Direct Link URL

This flow shows how to use the direct link to open a UCMDB applet (opened to a specified context) in a new browser frame.

1. The external application has a page that needs to show the UCMDB applet.

2. The returned page includes a directive to open the direct link in an IFrame or new browser window.

3. The browser opens a new frame (IFrame or new window) with the direct link as the frame URL.

4. The new frame sends the direct link to the Universal CMDB server.

5. If the user is not already logged into Universal CMDB, Universal CMDB displays the login page and waits for the user to enter credentials and click the login button.

6. The user session is created, if required.

7. The Universal CMDB server returns a page that includes the directive to load the UCMDB applet.

8. The browser processes the page. When the browser encounters the directive to load the UCMDB applet, it starts the JVM. The browser then passes the needed parameters to the JVM, including the Universal CMDB server location as "code base."

9. UCMDB applet files (jars) and data are transferred between the Universal CMDB server and the JVM loaded in the browser.

Caution The Universal CMDB server must be accessible from the browser machine.

An Embedded UCMDB Applet Using a UCMDB Applet Tag

This flow shows how to use the UCMDB applet tag in conjunction with direct links to embed the UCMDB applet (opened to a specified context) in an external application page.

1. The UCMDB applet tag is included in the processed JSP in the external application.

2. The UCMDB applet tag uses the parameters given to it to create an HTTP/HTTPS connection to the Universal CMDB server and requests the applet HTML snippet code.

3. If the user is not already logged in, the parameters from the UCMDB applet tag are used (see the tag itself for reference information regarding this step). If login fails, the UCMDB applet tag returns an error message, either the preset one or the one specified in the UCMDB applet tag parameters.

4. The Universal CMDB server returns the HTML snippet code (with embedded Javascript) that loads the UCMDB applet. The external application can now incorporate this snippet code into the page, and send the page to the browser.

5. The external application sends the complete page that includes the HTML snippet code to the browser.

6. The browser processes the page. When the browser encounters the HTML snippet code that loads the UCMDB applet, the JVM is started. The browser then passes the needed parameters to the JVM, including the Universal CMDB server location as "code base".

7. UCMDB applet files (jars) and data are transferred between the Universal CMDB server and the JVM loaded in the browser.

Caution The Universal CMDB server must be accessible from both the browser machine as well as the external application machine.

Related Information