Where to integrate AR System
The three options for integration points with are the client, the server, and the database server. The choice depends on the nature of the integration and whether user interaction is involved.
Integrating the client
to a third-party application—Integration with the client typically involves taking data from a form and passing it to another application where the user can then perform additional functions. Integration can also simply consist of launching another application that reads data from the database. In general, client integration assumes that the user will access the other application to some extent. Most instances are real-time, where a user is involved right now.
Third-party application to
—Often, a third-party application launches a mid tier and directs it to display specific data. For example, a network management system might have a graphical map of the network devices. Selecting a device on the map and then selecting List Open Tickets from a menu could cause the mid tier to be triggered with the ID of the selected device passed as a parameter, The mid tier can then generate a results list of all of the open trouble tickets for the device. This way, a network technician can quickly see all of the outstanding problems for a device, but does not need to know the details of starting and issuing queries.
Integrating the
Integration with the generally implies data sharing or transfer, either to or from the server. The integration might involve workflow that triggers secondary actions. Sometimes, the server initiates the interaction. For example, a filter is triggered and uses a Run Process action to send a notification to a technician. In other instances, a third-party application might submit new requests to the server or query for the status of existing requests. For example, a system management agent running on a PC might discover the addition of a new sound card. The agent sends a message to a (remote) management application that, in turn, submits a new request to an asset application in . users are not directly aware that a new request has been created, but the next time someone generates an asset report, the new information is included.
Integrating the database
The following modes of integration involve the database directly:
- A third-party application reading the database
- reading an external database
- writing to an external database
The first two modes, which involve reading databases, are relatively straightforward. Any application that can issue SQL commands and that has the appropriate permissions can read the data in the tables. In a similar manner, workflow actions can execute SQL read commands and scripts that query external database tables and retrieve information. For more information, see Integrating.
The third mode, having write data to an external database table, can be accomplished by using Direct SQL. Another method is to create workflow that executes an SQL command script, passing any data as parameters to the script.
View and Vendor forms are also available to provide access to external databases in forms.
Having a third-party application write data to a table is not supported. The maintains the relationships among the tables in the database. If a third-party application attempts to add data and does not maintain these relationships, the entire database can become corrupted.
Integrating the
The provides integration capabilities to interface with third-party products. Integration provides the mid tier access to external data, and third-party products can access data through the mid tier. allows applications to expose interfaces as web services, and it allows applications to consume external web services. You can also use the data visualization field for external web content integration.