Solution projects
The solution project is the starting point for building your event driven application. To design your solution, you create a solution project in Insight Designer, and then export the solution to an archive file that you can deploy to the server.
The solution project is an Eclipse project that references the agent projects and the shared business object model. The solution project also contains the files to define the connectivity and the deployment configurations.
When you create a solution project, you also create a project for your business object model. After you complete the design of the business object model, you can create the agent projects that you want to include in your solution. The agent projects use the BOM project that is referenced in the solution project. You can view the referenced projects in the properties of the solution project.
- Solution project
- The solution project contains the following folders and files:
- Connectivity Definitions folder: stores the connectivity definition (.cdef) files. The .cdef files define the inbound and outbound bindings and endpoints for the solution.
- Transformations folder: stores XSL transformation files for converting unrecognized inbound messages.
- solution_properties.xml file: contains the custom properties of the solution project.
- SOLUTION.MF file: contains the version information
of the solution, and the solution symbolic name.
At export time, the solution symbolic name is used along with the version number to create the symbolic name of the OSGi feature. The manifest specifies the latest version of the solution that is exported. By default, when you create a solution project the version is set to 0.0. You can increment the version before you export the solution archive. The manifest file is then updated with the new version.
In the solution manifest, you can also specify the time zone to use instead of the time zone of the server.
- Deployment Configurations folder: contains the custom deployment configurations. This folder is created when you deploy your solution by using the menu.
- Entity Loaders folder: stores the entity loader (.eldr) files. You create .eldr files to initialize entities for testing.
- Event Sequences folder: stores the event sequence (.eseq) files. You create .eseq files to define a sequence of events to use for testing.
- BOM project
- The BOM project is created along with the solution project. The
BOM project is the container for the following artifacts:
- A bom folder that stores the business model definition files (.bmd), and the BOM entry that holds the generated BOM classes for event and entity types.
- A aggregates folder that stores the global aggregate definitions (.agg).
- Java™ Model project
- The solution Java Model
project is created along with the solution project. This project is
a container for the executable object model that is generated from
the business object model. The name of this project is based on the
solution project name. If you rename the solution project, the reference
to the Java Model project is
lost. To reestablish the reference, you must update the symbolic name
of the Java Model project to
the name that would have been generated automatically: solution.modelExecutable,
where solution is the name of
your solution project.
By default, the executable object model is automatically generated. If you delete the Java Model project, the executable object model is not generated unless you migrate the project.
Warning: You must not manually edit this project and its contents, the automatic generation overwrites any modifications. - Rule agent project
- The rule agent project is a container for rules that define the
business logic. The rules are created in the rules folder
of the agent project.
The agent project also contains a descriptor that you must complete to define the routing logic of the agent.
- Java agent project
- The Java agent project is
a container for Java code to
process events. In the Java agent,
you import the package that contains the Java interfaces.
The agent project also contains a descriptor that you must complete to define the routing logic of the agent.
- Predictive scoring agent project
- The predictive scoring agent project calls a scoring configuration
on an external scoring server by using Java code.
The agent project also contains a descriptor that you must complete to define the routing logic of the agent.