Skip to Content

 

/wp-content/uploads/2016/08/disc1_1023341.png

 

 

 

This is a continuation from part 3 (LINK)

 

 

5. Integration Builder Configuration

 

 

The configuration here consists of creating:

 

  • Communication Scenario
  • Communication Channels
  • Receiver Determination
  • Interface Determination
  • Sender Agreement
  • Receiver Agreement

 

 

 

5.1 Creating Communication Scenario

 

 

The configuration of the Communication Scenario is performed in the Integration Builder:

 

/wp-content/uploads/2016/08/image114_1023166.png

 

Start ‘Integration Builder’

 

 

Depending on your stings, this might start up on different views. Make sure you change this to the ‘Configuration Scenario View’ – see below:

 

 

 

/wp-content/uploads/2016/08/image116_1023171.png

This will change the view to look like this:

 

/wp-content/uploads/2016/08/image118_1023172.png

 

You see a list of all of the already configured Communication Scenarios.

 

First we create a new Communication Scenario – this is the ‘container’ where we will add all the configuration needed.

 

/wp-content/uploads/2016/08/image119_1023176.png

 

 

/wp-content/uploads/2016/08/image120_1023177.png

 

 

Select a name for your scenario and click ‘Create’.

 

This will open an empty scenario:

 

 

/wp-content/uploads/2016/08/image122_1023182.png

At this point, the ‘Objects’ list is empty, as we have not assigned or created and objects.

 

Now ‘Save’ and ‘Activate’.

 

 

/wp-content/uploads/2016/08/image124_1023183.png

 

When we are done we will have the following objects:

 

/wp-content/uploads/2016/08/image126_1023184.png

 

 

The ‘Business Systems’ are already configured in the system (REMEMBER THAT ONE OF THE ASSUMPTIONS IS THAT WE ALREADY HAVE PI COMMUNICATING WITH ERP AND C4C).

What we will create is:

 

  • 2 Communication Channels (one for sender and one for receiver)
  • 1 Sender Agreement
  • 1 Receiver Agreement
  • 1 Receiver Determination
  • 1 Interface Determination

 

For ‘Communication Channels’ we will use the following names:

 

  • ‘zbh_tech_comm_chan_sender’ – for the sender channel
  • ‘zsbh_tech_comm_receiver’ – for the receiver channel

 

 

 

THE OTHER COMPONENTS DOES NOT HAVE A NAME, BUT ARE ASSIGNED TO OUR COMMUNICATION SCENARIO.

 

 

 

5.2 Creating Communication Channels

 

 

Click on the ‘Create’ icon:

 

/wp-content/uploads/2016/08/image128_1023186.png

 

 

/wp-content/uploads/2016/08/image130_1023187.png

 

Select ‘Communication Channel’ – you will also see that the object is automatically assigned to our scenario, because we executed the ‘Create’ from within the scenario.

 

First select ‘Communication Component’, and then provide the name for the Communication Channel and a description:

 

 

/wp-content/uploads/2016/08/image132_1023188.png

 

Since this is the sender – we select CfC_ERP_UTIL from the drop down list.

 

In the beginning of the document, we stated that CfC_ERP_UTIL is the C4C system, and in our case the sender of the web service request.

 

The click ‘Create’.

 

/wp-content/uploads/2016/08/image134_1023189.png

 

On ‘Adapter Type’ select the search and select SOAP, SAP BASIS 7.11.

 

 

/wp-content/uploads/2016/08/image136_1023190.png

 

Then mark ‘Use Query String’.

 

/wp-content/uploads/2016/08/image138_1023194.png

 

Then ‘Save’ and ‘Activate’.

 

Go back to the ‘Configuration Scenario’

 

 

/wp-content/uploads/2016/08/image140_1023195.png

 

Now ‘Save’ and ‘Activate’

 

 

/wp-content/uploads/2016/08/image142_1023196.png

 

Pay attention to that the ‘Business System’ was also added.

 

 

—-

 

Now we create the receiver communication channel.

 

 

/wp-content/uploads/2016/08/image144_1023210.png

 

 

/wp-content/uploads/2016/08/image146_1023211.png

 

The communication Component for the receiver is the ERP system, in our configuration ECA_100.

 

 

Select ‘Create’.

 

 

/wp-content/uploads/2016/08/image148_1023212.png

Like before – search for the ‘Adapter Type’ and select SOAP, SAP BASIS 7.11.

 

 

/wp-content/uploads/2016/08/image150_1023213.png

 

Click on ‘Receiver’ and you will see a target URL opening up. This URL is the one provided from the WSDL of our service.

 

One option is to find our service in SOAMANAGER (ERP).

 

HERE WE ARE JUMPING TO SOAMANAGER – Find our service in SOAMANAGER, then click in the icon (see arrow below):

 

 

/wp-content/uploads/2016/08/image152_1023214.png

 

 

/wp-content/uploads/2016/08/image154_1023221.png

 

Click on execute and a browser will open with the WSDL. Go to the end of the WSDL and copy the URL listed in the address location:

 

 

/wp-content/uploads/2016/08/image156_1023222.png

 

This URL you paste in to the ‘Target URL’ for the communication channel configuration:

 

 

/wp-content/uploads/2016/08/image159_1023223.png

 

At the end of the URL point to the right client, in our case client 100 (adding ?sap-client=100 after the URL):

 

 

/wp-content/uploads/2016/08/image160_1023227.png

 

/wp-content/uploads/2016/08/image163_1023228.png

The select ‘User Authentication’. This is a user from ERP with authorization execute web service.

 

Also, check the ‘Use Query String’.

 

Now ‘Save’ and ‘Activate’.

 

Then go back to the Configuration Scenario and save and ‘Activate’ again.

 

 

/wp-content/uploads/2016/08/image164_1023233.png

 

We have now finished the configuration of both Communication Channels.

 

 

Continued in PART 5

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply