18.04.2013 Views

B2B Integration : A Practical Guide to Collaborative E-commerce

B2B Integration : A Practical Guide to Collaborative E-commerce

B2B Integration : A Practical Guide to Collaborative E-commerce

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Integration</strong> Brokers 281<br />

Continued from page 280<br />

cus<strong>to</strong>m Java servlet application for quoting and enCommerce for<br />

Web cus<strong>to</strong>mer authentication.<br />

In addition, Juniper works with numerous contract manufacturers<br />

<strong>to</strong> produce products and components, so it required a way <strong>to</strong> link its<br />

internal business processes with critical trading partners. In particular,<br />

Juniper needed <strong>to</strong> improve its Available-<strong>to</strong>-Promise (ATP) application<br />

<strong>to</strong> streamline the Purchase Order/Change Order process and ensure<br />

immediate answers for cus<strong>to</strong>mers about product availability and order<br />

fulfillment. In the past, this manual ATP process — which required a<br />

significant amount of back-and-forth communication as well as<br />

duplicate data entry — could take anywhere from three days <strong>to</strong> a<br />

week <strong>to</strong> complete.<br />

Integrating Internal Applications for e-Business<br />

After evaluating a range of potential solutions <strong>to</strong> integrate its internal<br />

business processes, Juniper selected a combination of webMethods<br />

Enterprise as its EAI solution and webMethods <strong>B2B</strong> <strong>to</strong> handle<br />

transactions with trading partners beyond the firewall.<br />

webMethods Enterprise was selected by Juniper for a variety of<br />

reasons:<br />

• To provide a flexible, scalable platform for its network <strong>commerce</strong><br />

initiative;<br />

• To provide a fast return on investment and very rapid<br />

implementation;<br />

• To solve the problems of synchronizing data between applications<br />

and building and au<strong>to</strong>mating multi-step, cross-application business<br />

processes; and<br />

• To keep pace with the rapid change in the e-business marketplace.<br />

With webMethods Enterprise, they could easily integrate new bes<strong>to</strong>f-class<br />

applications as they emerge. The architecture enabled<br />

them <strong>to</strong> swap applications they were currently using for better<br />

ones or add new applications — all without the time-consuming<br />

work of rewriting point-<strong>to</strong>-point interfaces.<br />

Continue on page 282

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!