The JIA solution is deployed in a 2-step process to the client machine where the automation is to be executed:
•Deployment of the project binaries (script and WCF service)
•Deployment of the JIA core binaries (JIA Engine, JIA Desktop Agent, and APIs)
This process provides for a lean deployment model (client-only) in which the solution interacts with various applications within the same workstation. (For more information about deploying JIA, refer to Deployment.)
The following illustration displays the different components that are part of the JIA deployment. The components are described in the table following the figure.
Component
|
Description/Notes
|
Script
|
The solution developed by the developer to fulfill a business requirement (using the JIA APIs).
The script contains the application logic and processing as it relates to the automation on applications or the real-time guidance provided to a user in the context of a given event.
|
Exposed WCF Service
|
A standard service, compliant with Windows Communication Foundation, that is exposed on the client workstation. External applications may interact with the service directly to leverage various operations that have been exposed through the service. For example, the service may be leveraged to invoke automations at will on a client workstation.
|
JIA Desktop Agent
|
The JIA Agent displays a set of panels that provide configuration (WCF service, logging) and status information about the automations.
|
JIA Engine
|
The core product component that drives integration and automation with various applications.
|
APIs
|
JIA’s coverage for various applications and platforms is delivered in a modular fashion, as part of the product code.
|
The script and the WCF service expose the functionality developed in JIA to meet various business requirements. The JIA Desktop Agent provides a console for managing the configuration of the JIA environment. The JIA Engine and the APIs belong to the product, and do not require any customization during solution development.
|
