Much of the information for the External Calls should be populated for you. When you are happy with the changes on this tab you can deploy the project by clicking theDeploy Project button at the bottom. This will generate all of the necessary runtime information to execute the application and write it to the correct location on the file system.
When the deployment is complete, the results of the process will be shown, telling you whether or not the deployment was successful. See Deployment Diagnostic Information for more details.
All Details
Most of the agents within an application will execute rules internally and some agents will serve web pages created using FormMaker. The tab called All Details contains all the agents present within the selected project, including the agents representing External Calls mentioned earlier. If you wish to change the runtime function of any existing agents, for example deploy an agent as a proxy to an external web service or a database, then you can use the All Details tab.
Within the All Details tab you can configure the runtime project location. This is the location where the project will be deployed for execution and testing and represents the root directory of the application, and in most situations you will not need to alter the default value. You can also specify the location of the Morphyc document that will be used to control the runtime application. Again, in most cases, you will not need to change the default value, but if you are using inter project communication for example you may want to alter this value (for more information on inter-project communication, please see the Hyfinity FAQ.
If you want to change the details for any of the listed agents then you have a number of available options:
Basic Generation - Deploys the agent to the specified location allowing it to be called at runtime by other Morphyc nodes or java applications on the local server machine. This is the default deployment option for agents.
Web Service Generation - Deploys the agent in a similar manner to the basic deployment, but also generates a web service interface for the agent. This allows the agent to receive XML client requests via HTTP and SOAP. In order to enable this, you must specify the location of an appropriately configured J2EE Web Server containing applications (webapps). This value should default to the location of the standard runtime environment installed for testing by default.
The action values that will be accepted by the web service interface, and processed by this agent are those actions defined against the agent. See Confirming Node and Action Information for details.
Web Application Generation - This deployment operation is only available for MVC WebMaker projects.
This option makes the selected agent visible from the web as the entry point to a web application. This uses the information defined within FormMaker to generate the correct action mappings and ensure the required web application resources (CSS files, images, scripts, etc.) are in the correct locations.
This option should be performed on the view agent within an MVC WebMaker project, and will be automatically performed when using the Deploy Application option within FormMaker.
As with the above option, this type of deployment requires the web application location to be specified, but in most cases you will be able to use the default value.
Web Service Proxy Generation - This option deploys the selected agent as proxy to a remote web service. When this option is selected the agent will not really exist at runtime. The agent is simply used to contain the location of a remote web service and any requests to this agent will be automatically forwarded to the remote service.
In order to use this option, you must specify the URI location of the remote service, and whether the service is a SOAP service, or just a standard HTTP based service.
There is also the option to allow dynamic URI and header support, which is discussed in more detail in the Advanced Options section of the WebMaker Overview document.
Inter Project Proxy Generation - This option is very similar to the web service proxy option above and deploys the node as a proxy to another Morphyc architecture agent in a different project.
To use this option, the full 4 part ID of the target agent must be entered and will be of the form
product-project-pattern-node. For more information, please see the inter-project proxy entry on the Hyfinity FAQ. Database Proxy Generation - This option provides the ability to proxy relational databases, which can then be used within Rules using the SQL Statement action to perform SQL queries. Clicking this option will request additional parameters, including the JDBC driver, URL, User Id and Password information. A screenshot of this is shown below:
Please note: You can also create and use database connections from within the SQL Statement action within RuleMaker and the Database Data Source option within the Page Structure tab of FormMaker
When you are happy with the changes on this tab you can deploy the project by clicking theDeploy Project button at the bottom. This will generate all of the necessary runtime information to execute the application and write it to the correct location on the file system.
When the deployment is complete, the results of the process will be shown, telling you whether or not the deployment was successful. See Deployment Diagnostic Information for more details.