By default no composite name is set when a SCA composite is executed. For runtime monitoring and tracking purposes it might be useful to set a custom name at design time for your SCA composite. Especially, when the number of instances increases in production.
By using embedded Java for BPEL components and XPath for Mediator components you are able to manipulate the title of a SCA composite during design time.
XPath for Mediator components:
I recently have decided to start blogging again. I don't no exactly why, but most probably it's due to the fact that I want to share my enthusiasm for SOA and Java technology with you. Especially those with an Oracle flavor..
The main topics of this blog will be:
Staying on the topic of hosted applications and security I thought I'd bring this to your attention. MessageLabs, a Symantec Company, is organising a breakfast seminar on Hosted Security in Dublin, in November. Although I won't be attending, you may find the presentations interesting and maybe get a free croissant or two.
Posted by Mike Rollings
But in some environments you are not allowed or you just don't want to put your authorized_keys to the servers, which you want to access. But how to automate logins to this servers?
SOA Station has it's own domain now: soastation.org. The blog is still hosted via Google's Blogger service and will be still accessible at soastation.blogspot.com.
In his keynote Larry Ellison nicely explains SOA in the context of Fusion Applications. His point is that customers do not want to replace exisiting apps, but integrate with them. He even used the word BPEL ;-). He made a very interresting point: A packaged application is no longer closed, but through usage of SOA middleware at its core opens itself up to integrate internally with other custom or third party applications.