|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (23)
View Page History...
We will use XPath to control conditions on EIP patterns.
...
# Create a new EIP Technical service with the following configuration:
# JBI properties of the configuration service:
# JBI properties of the configuration service:
## Interface namespace: *[http://test.petalslink.com|http://test.petalslink.com*]*
## InterfaceName: *EipSplitterInterface*
## Service Namespace: *[http://test.petalslink.com|http://test.petalslink.com*]*
## Service Name: *EipSplitter*
## End-point Name: *EipSplitterEndpoint*
## InterfaceName: *EipSplitterInterface*
## Service Namespace: *[http://test.petalslink.com|http://test.petalslink.com*]*
## Service Name: *EipSplitter*
## End-point Name: *EipSplitterEndpoint*
## *Interface namespace*: [http://test.petalslink.com|http://test.petalslink.com*]
## *InterfaceName*: EipSplitterInterface
## *Service Namespace*: [http://test.petalslink.com|http://test.petalslink.com*]
## *Service Name*: EipSplitter
## *End-point Name*: EipSplitterEndpoint
## *InterfaceName*: EipSplitterInterface
## *Service Namespace*: [http://test.petalslink.com|http://test.petalslink.com*]
## *Service Name*: EipSplitter
## *End-point Name*: EipSplitterEndpoint
# Project Name and Location:
## Project Name: su-EIP\-*EipSplitter*\-provide
## *Project Name*: su-EIP-EipSplitter-provide
# Specific Component properties:
## Eip: *Splitter*
# Service Parameters:
## Select _su-jsr181-MathOperations-provide_ for automatic configuration.
# XPath Condition:
## *//\[local-name()="AddIntegers"\]*
# Service Parameters:
## Select _su-jsr181-MathOperations-provide_ for automatic configuration.
# XPath Condition:
## *//\[local-name()="AddIntegers"\]*
## *Eip*: Splitter
# *Service Parameters*: _Select "su-jsr181-MathOperations-provide" for automatic configuration._
# *XPath Condition:* //*\[local-name()="AddIntegers"\]
# *Service Parameters*: _Select "su-jsr181-MathOperations-provide" for automatic configuration._
# *XPath Condition:* //*\[local-name()="AddIntegers"\]
# Additional Parameters
## Operation Namespace: *[http://test.petalslink.com|http://test.petalslink.com*]*
## Operation: *AddIntegers*
## Mep: *InOut*
## Operation: *AddIntegers*
## Mep: *InOut*
## *Operation Namespace*: [http://test.petalslink.com|http://test.petalslink.com*]
## *Operation*: AddIntegers
## *Mep*: InOut
## *Operation*: AddIntegers
## *Mep*: InOut
# CDK properties
## Validate WSDL: *false* (there is no wsdl)
## *Validate WSDL*: false _(there is no wsdl)_
h2. Configure the Aggregator
...
# Create a new EIP Technical service with the following configuration:
# JBI properties of the configuration service:
# JBI properties of the configuration service:
## Interface namespace: *[http://test.petalslink.com]*
## InterfaceName: *EipAggregatorInterface*
## Service Namespace: *[http://test.petalslink.com]*
## Service Name: *EipAggregator*
## End-point Name: *EipAggregatorEndpoint*
## InterfaceName: *EipAggregatorInterface*
## Service Namespace: *[http://test.petalslink.com]*
## Service Name: *EipAggregator*
## End-point Name: *EipAggregatorEndpoint*
## *Interface namespace*: [http://test.petalslink.com]
## *InterfaceName*: EipAggregatorInterface
## *Service Namespace*: [http://test.petalslink.com]
## *Service Name*: EipAggregator
## *End-point Name*: EipAggregatorEndpoint
## *InterfaceName*: EipAggregatorInterface
## *Service Namespace*: [http://test.petalslink.com]
## *Service Name*: EipAggregator
## *End-point Name*: EipAggregatorEndpoint
# Project Name and Location:
## Project Name: su-EIP\-*EipAggregator*\-provide
## *Project Name*: su-EIP-EipAggregator-provide
# Specific Component properties:
## Eip: *Splitter*
## Aggregator Correlation: *boolean(/*\[local-name()="AddIntegers"\])*
# Service Parameters:
## Select _su-EIP-EipSPlitter-provide_ for automatic configuration.
# XPath Condition:
## *boolean(/*\[local-name()="AddIntegers"\]/*\[local-name()="equals"\])*
## Aggregator Correlation: *boolean(/*\[local-name()="AddIntegers"\])*
# Service Parameters:
## Select _su-EIP-EipSPlitter-provide_ for automatic configuration.
# XPath Condition:
## *boolean(/*\[local-name()="AddIntegers"\]/*\[local-name()="equals"\])*
## *Eip*: Aggregator
## *Aggregator Correlation*: \*boolean(/*\[local-name()="AddIntegers"\])\*
# *Service Parameters*: _Select "su-EIP-EipSPlitter-provide" for automatic configuration._
# *XPath Condition*: boolean(/\[local-name()="AddIntegers"\]/\[local-name()="equals"\])
## *Aggregator Correlation*: \*boolean(/*\[local-name()="AddIntegers"\])\*
# *Service Parameters*: _Select "su-EIP-EipSPlitter-provide" for automatic configuration._
# *XPath Condition*: boolean(/\[local-name()="AddIntegers"\]/\[local-name()="equals"\])
# Additional Parameters
## Operation Namespace: *[http://test.petalslink.com]*
## Operation: *AnyOperationName* (since EipSplitter does not have an operation name)
## Mep: *InOut*
## Operation: *AnyOperationName* (since EipSplitter does not have an operation name)
## Mep: *InOut*
## *Operation Namespace*: [http://test.petalslink.com]
## *Operation*: AnyOperationName _(since EipSplitter does not have an operation name)_
## *Mep*: InOut
## *Operation*: AnyOperationName _(since EipSplitter does not have an operation name)_
## *Mep*: InOut
# CDK properties
## Validate WSDL: *false* *Validate WSDL*: false (there is no wsdl)
h2. Create and deploy an EIP Service Assembly
...
There is a tight-coupling between both EIP. Assembling them in one single SA can be a good idea (especially with EIP, which can chain lots of patterns, each requiring a different SU).
# Create a new Service Assembly.
# Create a new Service Assembly.
## Name: *sa-Eip-AggregatorSplitter*
## *Name*: sa-Eip-AggregatorSplitter
# Add the two EIP Service-Units you created, and confirm
# Fast-export the Service Assembly for Petals.
# Fast-export the Service Assembly for Petals.
...
*Other orchestration ways: BPEL, SCA, JSR181 or POJO. More info in whitepaper*
...