Enterprises engaging in B2B communications with their trading partners are facing increased pressure to increase automation and reduce costs. Increased compliance requirements and globalization of economies are fuelling B2B adoption in every vertical. B2B Gateway solutions enable enterprises to connect with external trading partners using B2B protocols to meet these new requirements.
This book, written by the most knowledgeable Oracle B2B author team, is a step-by-step practical guide that provides you with the essential information required to implement Oracle B2B solutions, including multiple hands-on tutorials that will help you get up and run quickly.
Packed with practical examples, illustrations, and product screenshots explained with clear, step-by-step instructions, the book starts with a discussion on the B2B industry and the most relevant B2B standards. It goes on to provide Oracle B2B architecture internals. This includes an introduction to SCA and Oracle B2B integration with Oracle Fusion middleware. Based on Oracle's suggested best practices and methodologies, the book provides a wide coverage and detailed discussion of Oracle B2B functionality and features for new and advanced users. The book features helpful tips and information on Oracle B2B not available elsewhere coming from experts with real-world experience with hundreds of B2B customers.
Chapter 1, B2B Overview, introduces the reader to the concept of B2B, provide an overview of B2B architecture, message processing patterns and the B2B Gateway, and describe the most relevant B2B standards.
Chapter 2, Oracle B2B Overview, builds the groundwork for the reader's further journey into Oracle B2B. It will provide the reader with Oracle B2B installation tips, SCA concepts, and Oracle B2B architecture highlights.
Chapter 3, Creating Document Definitions, describes how to create different document guidelines in Oracle B2B Document Editor and import these guidelines as document definitions in Oracle B2B.
Chapter 4, Trading Partner Management, describes how to configure host and remote trading partners, and how to create trading partner agreements and deploy them.
Chapter 5, Setting up B2B Transactions, explains how to create the sequence of steps needed to set up different documents, partners, and agreements.
Chapter 6, SOA Suite Integration, explains how to connect Oracle B2B with Oracle SOA Suite using different mechanisms, and you will learn how to choose the right mechanism for your situation.
Chapter 7, Reporting and Monitoring, explains how to monitor the runtime transactions using the reports and monitoring capabilities.
Chapter 8, Exception Handling, explains about the specific types of inbound and outbound exceptions that can occur and will be introduced to a custom exception handling process that incorporates human workflow into the error resolution process.
Chapter 9, Oracle B2B Security Management, explains Oracle B2B security features and how they are integrated into the overall Oracle Fusion Middleware (OFM) security paradigm.
Chapter 10, Preparing to Go-Live, explains how to build your production B2B topology, how to migrate your B2B installation from test to production, what tools are available to perform B2B administration, and how to tune your environment for optimal performance.
Chapter 11, Advanced Topics, explains how B2B Callouts can be used to invoke custom Java code, how the B2B Self-Service APIs can be used to create metadata in bulk, and how B2B utilities can be used to enqueue and dequeue messages based on AQ and JMS based queues.
The virtual image of the Oracle SOA Suite patch release PS5 (11.1.1.6) installed on a LINUX platform has been used by the authors throughout the book. The deployment uses Oracle Database EE 11g as a common repository. This also applies to the version of JDeveloper. The Document Editor version used is 7.0.5
This tutorial is intended for a wide range of audiences which includes SOA developers, SOA Suite and B2B administrators, and SOA architects. However some prior experience with SOA Suite 11g is necessary. This experience should include basic knowledge of WebLogic Server, BPEL Process Manager, and Oracle Mediator.
In this book, you will find a number of styles of text that distinguish between different kinds of information. Here are some examples of these styles, and an explanation of their meaning.
Code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles are shown as follows.
Both CPA and CPP are XML documents that have the same root element CollaborationProtocolProfile with PartyInfo, Packaging, Signature, and Comment elements.
A block of code is set as follows:
<Segment-ST>
<Element-143>850</Element-143>
<Element-329>0001</Element-329>
</Segment-ST>When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:
<Segment-BEG> <Element-353>00</Element-353> <Element-92>AB</Element-92> <Element-324>B1234567</Element-324> <Element-328>1</Element-328> <Element-373>20120929</Element-373> </Segment-BEG>
Any command-line input or output is written as follows:
cd /ProgramData/Propeople rm -r Drush git clone --branch master http://git.drupal.org/project/drush.git
New terms and important words are shown in bold. Words that you see on the screen, in menus or dialog boxes for example, appear in the text like this: "On the Select Destination Location screen, click on Next to accept the default destination."
Feedback from our readers is always welcome. Let us know what you think about this book—what you liked or may have disliked. Reader feedback is important for us to develop titles that you really get the most out of.
To send us general feedback, simply send an e-mail to <[email protected]>, and mention the book title via the subject of your message.
If there is a topic that you have expertise in and you are interested in either writing or contributing to a book, see our author guide on www.packtpub.com/authors.
Now that you are the proud owner of a Packt book, we have a number of things to help you to get the most from your purchase.
You can download the example code files for all Packt books you have purchased as well as the high resolution graphics of this book from your account at http://www.packtpub.com. If you purchased this book elsewhere, you can visit http://www.packtpub.com/support and register to have the files e-mailed directly to you.
Although we have taken every care to ensure the accuracy of our content, mistakes do happen. If you find a mistake in one of our books—maybe a mistake in the text or the code—we would be grateful if you would report this to us. By doing so, you can save other readers from frustration and help us improve subsequent versions of this book. If you find any errata, please report them by visiting http://www.packtpub.com/submit-errata, selecting your book, clicking on the errata submission form link, and entering the details of your errata. Once your errata are verified, your submission will be accepted and the errata will be uploaded on our website, or added to any list of existing errata, under the Errata section of that title. Any existing errata can be viewed by selecting your title from http://www.packtpub.com/support.
Piracy of copyright material on the Internet is an ongoing problem across all media. At Packt, we take the protection of our copyright and licenses very seriously. If you come across any illegal copies of our works, in any form on the Internet, please provide us with the location address or website name immediately so that we can pursue a remedy.
Please contact us at <[email protected]> with a link to the suspected pirated material.
We appreciate your help in protecting our authors, and our ability to bring you valuable content.
You can contact us at <[email protected]> if you are having a problem with any aspect of the book, and we will do our best to address it.