2. Repository
• Provide an understanding of the Neuron ESB repository
• Learn how to leverage Repository Documents in other areas of Neuron ESB
Goals
3. Repository
• Introduction to the Neuron ESB Explorer Repository
• Using Repository Documents in Business Processes
• Using Repository Documents in Workflows
• Using Repository Documents with code editors
Lesson Plan
4. Repository
Repository
• Central location for the storage and management of
documents that can be leveraged inside of Neuron ESB
• Documents hosted in the repository can be accessed
and used by Business Processes and Workflows
5. Repository
Using Repository Documents in Business Processes
• In Business Process steps, such as the Transform XSLT
step, you can choose from documents in the repository
(rather than entering in the data for the step)
• Documents located in the repository, that match the
type that the process step is looking for (such as type
XSLT for the Transform XSLT step) will be auto-
populated for selection in the drop down selector
6. Repository
Using Repository Documents in Workflows
• In Workflows activities, such as the Transform XML
activity, you can choose from documents in the
repository (rather than entering in the data for the step)
• Documents located in the repository, that match the
type that the activity is looking for (such as type XSLT for
the Transform XML activity) will be auto-populated for
selection in the drop-down selector
7. Using Repository Documents : Demo
Purpose:
To familiarize users with using Repository Documents in Business Processes and Workflows inside of the Neuron ESB
Explorer
Objectives:
To acquaint users with the following areas of the messaging section:
• Creating a repository document
• Using a repository document in a Business Process
• Using a repository document in a Workflow
8. Repository
Using Repository Documents in Language Editors
• Documents located in the repository can
be accessed inside code editors
• Setting the property with the prefix
Neuron followed by the appropriate
property name (xsltName,
schemaNames, etc) will allow
subsequent steps to locate the proper
document in the repository
• Subsequent business processes can
show a warning indicating that no
document has been selected
• However as it is being set dynamically in
code, this is perfectly valid
9. Using Repository Documents in Language Editors : Demo
Purpose:
To familiarize users with using Repository Documents in Code Editors inside of the Neuron ESB Explorer
Objectives:
To acquaint users with the following areas of the messaging section:
• Accessing a repository document set in code inside of a business process step
• Accessing a repository document set in code inside of a workflow activity
10. Repository : Lab
Goal
In this lab, you will learn how to create a simple business process, test it at design time, attach it to a party to be executed
on every message that the party handles and finally ensure that it works at runtime as well.
Objectives
• Create a document in the Neuron Repository
11. Introduction to Neuron ESB
Review
• Many different types of documents can be stored in the Neuron ESB Repository
• Repository documents can be used in both business processes and workflow definitions via
activities that make use of them
• Repository documents can be accessed via Language Editors in both business processes and
workflow definitions.
Editor's Notes
The Neuron ESB repository is a centralized location for the storage and management of documents which can be leveraged inside of the Neuron ESB solution from inside of business processes and workflow definitions.
Business process steps, such as the Transform XSLT process step, can make use of repository documents. While most of these process steps can take copy and pasted documents, having the documents in a central location, allows them to be managed easily, and used by multiple process steps by reference instead of redundancy. Process steps using repository documents do require that a document of the expected type be present in the repository. For example the Transform XSLT process step requires an XSLT be in the repository as it cannot make use of other repository document types.
Workflow activities, such as the Transform XML activity, can make use of repository documents. Like the process steps that use repository documents, workflow activities can take copy and pasted documents, though in the same regard it is better to have these documents located in the repository to avoid redundancy. Workflow activities using repository documents do require that a document of the expected type be present in the repository. For example the Transform XML workflow activity requires an XSLT be in the repository as it cannot make use of other repository document types.
Not only can repository documents be used by specific business process steps, they can also be used by the Language editor process steps. For example you can use the language editor to dynamically set the XSLT property for the Transform XSLT process step. This provides a level of flexibility as you can use the same business process to handle and transform many different XMLs without making any changes to the business process.
