 |  |  |  |  |
| | | | |
 |  |
Developing a router application involves these high-level steps:
Determine the routes your application needs to implement.
Map out the routes from beginning to end.
Determine what the expected inputs and outputs are, such as data types and formats; what connection and transmission protocols must be integrated; and so on.
Determine whether and how you need to process messages (modify, redirect, track, and so on) before they reach their destination.
Define routing rules.
You define routing rules either in Java DSL, XML DSL, or a combination of these.
Implement business logic.
When necessary, you can implement custom business logic using plain old Java objects (POJOs).
Configure components.
If you need to use components other than those embedded in Fuse Mediation Router's core, you must configure them using either Java code or XML (if you're using a Spring container or an OSGi Blueprint container).
Choose a deployment option.
Standalone deployment
Write a main() method in your application code, which is responsible for creating
and registering RouteBuilder objects (that establish routing rules) and for
configuring and registering components.
Spring Framework-based deployment
Deploy your router application into a Spring container, using the Spring XML configuration file to define routes and configure components.
OSGi-based deployment
There are several ways to deploy your router application into an OSGi container.
An easy way is to bundle the .jar files with an OSGi manifest file,
then drop the bundle into the hot deploy folder.
For details, see Fuse ESB Deploying into the OSGi Container.
![[Tip]](imagesdb/tip.gif) | Tip |
|---|---|
There are many more environments in which you can deploy your router application; for example, Tomcat, WebSphere, JEE server, The Cloud, and so on. |
Deploy the router.
Follow the instructions provided for the particular container or deployment option that you chose. For detailed instructions, see the Fuse Mediation Router Deployment Guide and Fuse ESB Deploying into the OSGi Container.
| |  | |
 |
