BEA WebLogic® Integration in a Services-Oriented World

GET INVOLVED

Blogs
Newsgroups
Submit Articles

CENTERS

SOA
Governance
SOA Integration
Enterprise Social Computing
Virtualization
Event-Driven Architecture

RESOURCES

Arch2Arch Media Center
Article Index
Events Calendar
About Arch2Arch

Arch2Arch Advisor
RSS Feeds

Arch2Arch > Community > Arch2Arch Media Center > Webinars

Webinar: BEA WebLogic® Integration in a Services-Oriented World

Date: This event took place on March 21 2007

Presentation:

View Webinar
Download Presentation!

Description:

In addition to enabling traditional integration scenarios, companies use WebLogic Integration (WLI) to build composite applications, or applications that create new capabilities by orchestrating activities across a series of backend systems. For companies looking to adopt a Services Oriented Architecture, how can you get the most out of your existing WLI assets? How do WLI processes relate to AquaLogic Service Bus (ALSB) and other BEA integration products? Please join WebLogic Integration product management for a discussion of WLI's role in a Services Oriented Architecture. This webinar will demonstrate a use case showing WebLogic Integration and AquaLogic Service Bus.

Presenter:

ASHISH KRISHNA - Ashish Krishna is an engineering product manager for WebLogic Integration at BEA Systems. Prior to this, he was an SOA solution architect. He has a diverse background in enterprise integration and software development, including legacy systems, EDI and ERP integration technologies. Ashish holds a Masters degree in Aerospace Engineering, and a Bachelors degree in Mechnanical Engineering and a Ph.D. candidacy in Mechanical Engineering at Texas A&M University.
VICTORIA GRIGGS - Victoria Griggs is Director of Product Management for WebLogic Integration at BEA Systems. Victoria has nearly 12 years’ experience in designing, implementing, and managing enterprise software ranging from web applications to ERP systems. Prior to BEA, Victoria managed a portfolio of products at Selectica, a product configuration company, where she was in charge of their Quoting, Mobile, and Integration product lines. She also spent several years in product management at industry2industry, an online procurement company, and over 5 years in professional services at Accenture where she implemented SAP systems. Victoria holds a bachelor's degree from Yale University.

Showing messages 1 through 2 of 2.

Do we need WLI for new SOA implementations?
2007-06-14 03:43:36 muddana [Reply | View]

Currently we have a home grown integration system and we are moving towards SOA with bus, BPM and registry. Is WLI is going to add any value at this point as we are going to use BPM?

Do we need WLI for new SOA implementations?
2007-06-15 16:57:25 vgriggs [Reply | View]

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.

Showing messages 1 through 2 of 2.

Discuss

Post your questions or comments below