Using Deep Links
The OneData deep link feature enables you to access the data manager functions from an external application. The deep link routes users to the Data Manager screen in the work area in Nova mode, and displays the menu options that correspond to the user’s security privileges.
To access the deep link, users must provide log on credentials. If SSO is configured and there is already an active OneData browser session, the deep link directs users to the Data Manager screen without requiring the user to re-enter log on credentials. For more information on SSO, see Administering webMethods OneData.
When using deep links, OneData displays:
The
Data Manager screen that corresponds to the user account privileges. If the user does not have privileges to access the work area,
OneData directs the user to the release area.
The
Deep Link Filter screen in Nova mode only. Therefore network and self-recursive structures in conceptual objects are not supported in deep links, because these types of objects can be viewed either in default mode or flex mode only.
The structure of the deep link is as follows:
http://[hostname]:[port]/[contextRoot]/dmdirect/[repositoryId]/[projectName]/[type]/[objectName]
The following table describes the deep link parameters.
Parameter | Description |
[hostname] | Name of server on which OneData is deployed. |
[port] | Port on which OneData is deployed (optional based on deployment). |
[contextRoot] | Context name of OneData in the application server. |
dmdirect | Name of the service provider bean as configured in web.XML. (This is a constant value.) |
[repositoryId] | Repository ID where the object resides. |
[projectName] | Name of the project where the object resides. |
[type] | The type of object. Valid values are: CO—Conceptual object. DO—Data object. |
[objectName] | Name of the data or conceptual object |