Wednesday Jul 22, 2015

Document Editor – Defining a custom message (Part 1 of 3) b2b SOA Suite by Bernardo Cabaços

clip_image002Oracle Document Editor is an application used for creating and testing document definitions for Oracle B2B.

The document definition (ECS) file is required in B2B for translating and validating documents.

With Document Editor you are able to create new guideline documents or use a template from the comprehensive library of standards available for download. You can download Document Editor and the standard definitions available here.

The available document guideline templates include EDI, HL7, positional flat file (which includes some SAP iDocs), XMLSchema and so on, as seen below.

Thanks to the countless templates available you can easily and quickly create a message definition (ECS) and respective XSD to import to B2B. Making the necessary changes if needed.

Below is an example of a message definition from the template library.

However, specially with Positional Flat File (PFF) messages, you might have to create a custom definition.

In this post I will go through the steps needed to create a custom PFF document definition in Document Editor. This post will be divided in 3 parts, in the first part I will focus on Message Segments', afterwards I'll cover the Field's types and properties, finalizing with testing and XSD generation.

Let's start by creating an empty definition. Read part I here and read part II here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

Thursday Jun 04, 2015

B2B 12c – HTTP Generic Channel with transport callout by Bruno Neves Alves

First of all, season's greetings to everyone!

Then, let me introduce this post saying that, already in the version 11g, a generic HTTP listening channel for message posting to B2B using the HTTP protocol was available. Any configured trading partner could use this generic channel to post messages to B2B.

A single common URL was available by default:
http://[host-name]:[host-port]/b2b/httpReceiver

In this way, a single listening channel is able to serve multiple trading partners for every HTTP communications with B2B.

When this channel is used, the process follows the default steps for message processing, namely:

Sender identification (i.e. using HTTP Header);

Document protocol/version/type identification ;

Agreement identification;

Message processing (parsing and validation);

Synchronous delivery to a back-end application.

The only differentiation factor is: since this channel is generic and not configurable or even available on the list of listening channels in B2B console, make it unavailable for channel callout configuration.

This has now changed with the 12c version.

With the version 12c of B2B is now possible to define a generic HTTP transport callout and associate it with a specific transport level callout.

As of now, this is driven by an B2B configuration Fusion Middleware property that needs to be added on Oracle Enterprise Manager Fusion Middleware Control

Read the complete article here.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

Monday Apr 20, 2015

SOA Suite/B2B as a Critical Mission Hub for a High Volume Message Use Case by Bruno Alves

clip_image002

In this article, you will find described high availability solution architecture, covering B2B and core SOA Suite components as BPEL, along with Business Rules, Mediator and BAM integration, as well as lessons learned in conducting such a complex and mission-critical project starting from a set of legacy applications. Read the complete article here.


SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

Saturday Apr 18, 2015

B2B 12c – What’s New! by Tiago Teixeira

clip_image002This post serves as the first of a series of posts dedicated to Oracle B2B. What better way to start this series than to highlight the many new features have been added to Oracle B2B 12c which can change the landscape of the target usage for B2B.
Let's look at some of these new features:

· Document Translation Callout Framework

o Introduced Document Callout for custom document parsing (inbound), validation and construction (outbound)

· Regular Expression Document Identification

· Trading Partner Metadata API

o Parameters, Identifiers and TP Agreements accessible via Java API and WS

· SSL Support for SMTP

· Trading Partner Identifier via Regular Expression

· Batching of Custom Documents

· xPath payload extraction from SOAP Body

· xEngine (B2B Native Parser) API for EDIFACT

· Bulk Listening Channel activation

· Enriched exchange information on message metadata

Read the complete article here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

Friday Apr 17, 2015

B2B 12c – Listening Channel activation and deactivation in bulk Bruno Neves Alves

clip_image002With the version 12c of B2B the possibility to activate and deactivate all listening channels in one single command was introduced. Previously, it was necessary to provide the name of the listening channels to perform the action, what, in scenarios with a considerable number of listening channels, made the task ineffective.

Different scenarios can be pointed out where this functionality is extremely useful:

· After importing a B2B configuration the channels are always in deactivated status. This command can be then executed in order to activate all the listening channels in bulk;

· Deactivate all listening channels to stop momentously all message consumption for corrective or preventive reasons into B2B or back-end applications;

· Switching the message consumption between two environments;

The feature is also provided in a command line based approach since is an extension to the already existing feature of enable/disable a particular listening channel. Therefore it is respecting the same prerequisites.

Prior to executing any B2B command line tool is necessary to set the following environment variables: Read the complete article here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

Friday Feb 20, 2015

B2B Event Queue Management for Emergency by Shub Lahiri

Executive Overview

clip_image002Many customers face a crisis in production system when, for some reason, they end up with several B2B messages stacked up in the system, that may not be of a high priority to be processed at that point in time. In other words, it would greatly help many customers if, in such critical situations, they had an option to flush the backed-up messages from the system for later resolution and simply continue with processing of the current messages.
A-Team has been involved with different customers worldwide helping them implement such a solution for emergency use. Without getting into too much technical details, a high-level approach for such a solution is discussed here. The methodology accomplishes two key tasks, that are of primary importance during an emergency crisis within a B2B production gateway:

  • Allows to flush the event queue while the gateway is down, so that the gateway can be brought up quickly
  • Introspect the messages created from the event queue for resubmission or rejection

The primary objective of this framework is to allow the B2B engine to come back up quickly after flushing the messages from the event queue. The recovery or resubmission of messages is usually reviewed manually by the operations and business teams off-line and takes a longer cycle to complete. But this should not affect the down-time of the production system after the fast removal of the messages from the event queue. The downtime, thus encountered, is only driven by the first task, as listed above.

Solution Approach

Overview

The solution consists of immediate cleanup of messages from the system. The entries will be stored in files. After the files are created, the gateway will be ready for normal processing without any impact of messages that were previously present in the system.
After the gateway is opened for normal business, the analysis of the file contents can be carried out, in parallel, to decide which messages will be resubmitted or discarded. This analysis can be done via scripts to extract relevant pieces of business data for the messages removed. The scripts are decoupled for various types of transient message data and built on basic query utilities. The basic building blocks for data introspection are typically custom scripts, that are created based on specific business needs for analysis.
The analysis will create 2 lists of message IDs – one for resubmission and the other for rejection. Existing command-line utilities can be invoked to resubmit the messages in a scripted loop with configurable delays in between the resubmissions. For rejection, there is typically no processing required. However, the list of IDs will be used to update the database to reflect a final state for the appropriate messages.

Tasks and Activities

The following sections describes the tasks in greater detail. Sections I and II cover the activities that need to be completed while the gateway is down. Sections III and IV include the post-mortem phase for analysis of messages removed from the system.
The flowchart below can be used as a reference for the critical cleanup tasks covered in Sections I and II.

I. Preparation of Environment Read the complete article here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

Sunday Aug 03, 2014

B2B Demo System hosted at Oracle

To get access to the demo environment please contact Oracle PartnerNetwork (OPN)!
Demonstration: GSE - Enhanced Oracle B2B Demo - DemoStore | Demo Corner | Run Demo

  • Showcases widely accepted documents and exchanges - EDI, AS2, Web Services.
  • Includes integration with BAM to showcase business level reports, dashboards
  • Integration with E-Business Suite to demo end to end integrations

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

Saturday Jun 21, 2014

B2B SOA Suite Demo System

To get access to the demo environment please contact Oracle PartnerNetwork (OPN) first!
Hello Partners! We’ve also just moved Partners to https://demo.oracle.com (See announcement). This strategic change means that Oracle will be significantly easier and more competitive for Partners to work with, as our demo services (demo Reservations, Partner-appropriate Demo Store items, and internet-facing website and demos) will be directly accessible to Partners in ways they’ve never experienced before.

GSE is very pleased to announce the availability of Enhanced Oracle B2B Demo. The demo showcases creation of Oracle B2B documents, channels and agreements. It also includes integration of Oracle B2B with Oracle Business Activity Monitoring (BAM) and end to end integration with Oracle E-Business Suite.
Highlights

  • The demo showcases widely accepted documents and exchanges, in the B2B industry, such as EDI, AS2, and Web Services.
  • Includes integration with BAM to showcase business level reports and dashboards.
  • Integration with E-Business Suite to demo end to end integrations that customers often want to see during demos and POCs.

Call to Action

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

Thursday May 22, 2014

New B2B & Cloud integration & API management presentations & cheat sheets

At our SOA Community Workspace (SOA Community membership required) you can find the latest presentations and cheat sheets for:

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

Saturday Apr 12, 2014

MDN Usage in AS2 by Scott Haaland

An MDN (Message Disposition Notification) is a transmission level acknowledgment used in the AS2 standard, so that the sender knows that the receiver successfully acquired the message in a B2B scenario. B2B (Business to Business) is an integration term used to describe the sending and receiving of business messages between business partners. When the business messages are being sent over the internet via HTTP or SMTP, it is critical to business operators to know that the messages were transmitted successfully to the right party. In order to give assurance to the business operators, specific B2B transmission standards have been developed. We call these standards "Message Exchange Standards".

These include AS1, AS2, AS4, ebMS and RNIF, to name a few. AS2 is a very common standard for EDI messaging. It is important for everyone using the standard to do so in the same way, or else inter-operation becomes very difficult or impossible. Here is a diagram showing a typical EDI interaction over AS2 between two fictitious partners named OracleServices and MarketInc. Read the complete article here.

SOA & BPM Partner Community

For regular information on Oracle SOA Suite become a member in the SOA & BPM Partner Community for registration please visit www.oracle.com/goto/emea/soa (OPN account required) If you need support with your account please contact the Oracle Partner Business Center.

Blog Twitter LinkedIn image[7][2][2][2] Facebook clip_image002[8][4][2][2][2] Wiki

About





Search

Archives
« September 2015
SunMonTueWedThuFriSat
  1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today