|
|
| Event: |
BEA WebLogic® Integration in a Services-Oriented World
|
| Subject: |
Do we need WLI for new SOA implementations? |
| Date: |
2007-06-15 16:57:25 |
| From: |
vgriggs |
|
Response to: Do we need WLI for new SOA implementations?
|
|
WLI, along with the other products you mentioned, can be used as a foundational aspect of your services oriented architecture (SOA). The processes created in WLI can consume services and WLI processes themselves can be exposed as services to be called by ALSB, ALBPM, or any other product (BEA or non-BEA). The answer to your question of whether WLI will add value to your project really depends on your own project's specific requirements. BEA has customers who are using only WLI, only ALBPM, only ALSB, or a combination of these products (and more) in their integration architectures.
While there are no hard and fast rules, WLI is typically used for more system-centric processes where straight-thru processing and high performance is key. We sometimes see the processes created in WLI being called as a step within a larger process that has been created in ALBPM. For example, if you have created an order management process in ALBPM, part of that high-level process could be "order fulfillment". Order fulfillment could entail updating multiple systems and orchestrating provisioning activities across multiple partners. WLI would be a good fit here.
If you have specific questions on whether WLI would be a good fit for your requirements, I recommend that you work with your BEA contact who is likely more familiar with your particular project. |
|
