b2b edits and keywords

Author: george-hoffer

.gitconfig

@@ -0,0 +1,7 @@
+[filter "media"]
+	clean = git media clean %f
+	smudge = git media smudge %f
+	required = true
+[user]
+	name = george-hoffer
+	email = george.hoffer@mulesoft.com

anypoint-b2b/_images/B2B_AS2EDI_01.png

@@ -1,4 +1,5 @@
 = AS2 Connector
+:keywords: b2b, as2, connector
 
 The AS2 Connector allows you to send and receive data from AS2 certified servers.
 
@@ -14,7 +15,7 @@ After reading this page you should be able to accomplish the following:
 
 This document assumes that you are familiar with Mule, the http://www.mulesoft.org/documentation/display/current/Anypoint+Studio+Essentials[Anypoint Studio interface], and http://www.mulesoft.org/documentation/display/current/Global+Elements[Global Elements]. Further, it is assumed that you are familiar with AS2 endpoints and have received endpoint configuration requirements.
 
-=== Namespace & Schema Location
+=== Namespace and Schema Location
 
 The XML namespace and schema location are as follows:
 
@@ -87,74 +88,74 @@ The following example requires basic familiarity with AS2, Anypoint Studio, and
 
 Create a new Mule Project with Mule Server 3.6.0 EE as runtime:
 
-image:/docs/download/attachments/131467593/receive-example-step-1.png?version=1&modificationDate=1435344041211[image] +
+image:receive-example-step-1.png[receive-example-step-1] +
 
 ==== Step 2
 
 Locate the AS2 Connector on the right hand-side palette:
 
-image:/docs/download/attachments/131467593/receive-example-step-2.png?version=1&modificationDate=1435344041221[image]
+image:receive-example-step-2.png[receive-example-step-2]
 
 ==== Step 3
 
 Drag the connector over to the canvas:
 
-image:/docs/download/attachments/131467593/receive-example-step-3.png?version=1&modificationDate=1435344041229[image]
+image:receive-example-step-3.png[receive-example-step-3]
 
 ==== Step 4
 
 The connector requires an AS2 Connector Configuration. To create a connector configuration, you must first create a global HTTP endpoint and then bind the connector configuration to the endpoint. The connector’s operations leverage the HTTP endpoint to receive and send AS2 messages.
 
 Click on the Global Elements tab and create an HTTP endpoint:
 
-image:/docs/download/attachments/131467593/4+http+global.png?version=1&modificationDate=1435344041010[image]
+image:4+http+global.png[4+http+global]
 
 ==== Step 5
 
 Give the HTTP endpoint a more descriptive name like “receive-as2-http-endpoint”. Click on the Connector Configuration add symbol to bring up the HTTP connector configuration dialog:
 
-image:/docs/download/attachments/131467593/5+configure+http.png?version=1&modificationDate=1435344041016[image]
+image:5+configure+http.png[5+configure+http]
 
 ==== Step 6
 
 Give the HTTP connector name a more descriptive name like “as2-http-connector” and press OK to go back to the global HTTP endpoint dialog box:
 
-image:/docs/download/attachments/131467593/6+as2+http.png?version=1&modificationDate=1435344041022[image]
+image:6+as2+http.png[6+as2+http]
 
 ==== Step 7
 
 Press OK to close the global HTTP endpoint dialog box:
 
-image:/docs/download/attachments/131467593/7+endpoint.png?version=1&modificationDate=1435344041028[image]
+image:7+endpoint.png[7+endpoint]
 
 ==== Step 8
 
 In this step, you will make an AS2 connector configuration and bind it to the global HTTP endpoint. Create an AS2 Connector Configuration from the Global Elements view:
 
-image:/docs/download/attachments/131467593/image2015-6-25+21%3A7%3A49.png?version=1&modificationDate=1435344041079[image]
+image:image2015-6-25+21%3A7%3A49.png[image2015-6-25+21%3A7%3A49]
 
 ==== Step 9
 
 Type “receive-as2-http-endpoint” in the attribute Global HTTP Endpoint Reference to bind the AS2 connector to the previously created global HTTP endpoint. Press OK.
 
-image:/docs/download/attachments/131467593/image2015-6-25+21%3A10%3A5.png?version=1&modificationDate=1435344041048[image]
+image:image2015-6-25+21%3A10%3A5.png[image2015-6-25+21%3A10%3A5]
 
 ==== Step 10
 
 After completing the previous steps, you should have the following in the Global Elements view:
 
-image:/docs/download/attachments/131467593/image2015-6-25+21%3A11%3A5.png?version=1&modificationDate=1435344041054[image]
+image:image2015-6-25+21%3A11%3A5.png[image2015-6-25+21%3A11%3A5]
 
 Back to the Message Flow view, on the AS2 message source, select “AS2” from the Connector Configuration drop-down list and select “Receive” from the Operation drop-down list:
 
-image:/docs/download/attachments/131467593/image2015-6-25+21%3A13%3A1.png?version=1&modificationDate=1435344041060[image]
+image:image2015-6-25+21%3A13%3A1.png[image2015-6-25+21%3A13%3A1]
 
 ==== Step 11
 
 * The connector’s Key Store Path attribute must be configured in either of the following scenarios:
 
-. Connector receives a signed request +
-. Connector receives an encrypted request +
+. Connector receives a signed request 
+. Connector receives an encrypted request 
 . Sender requests a signed receipt
 
 For scenario 1, the key store has to contain the certificate used by the AS2 connector to verify the request’s authenticity. +
@@ -169,41 +170,41 @@ For the sake of keeping the example simple, no key store is set so no security i
 
 Add a File outbound endpoint to save the sender’s AS2 message content. Drag a File outbound endpoint from the palette next to the AS2 Connector. Set the Path attribute to “inbox” and Output Pattern to “data.txt”:
 
-image:/docs/download/attachments/131467593/image2015-6-25+21%3A15%3A36.png?version=1&modificationDate=1435344041067[image]
+image:image2015-6-25+21%3A15%3A36.png[image2015-6-25+21%3A15%3A36]
 
 ==== Step 13
 
 Finally, run the example as a Mule application:
 
-image:/docs/download/attachments/131467593/image2015-6-25+21%3A16%3A12.png?version=1&modificationDate=1435344041073[image]
+image:image2015-6-25+21%3A16%3A12.png[image2015-6-25+21%3A16%3A12]
 
-The connector will save the content of valid AS2 messages in the file “data.txt” inside the project root directory “inbox”.
+The connector saves the content of valid AS2 messages in the file “data.txt” inside the project root directory “inbox”.
 
-=== Send a clear and unsigned AS2 message over HTTP
+=== Send a Clear and Unsigned AS2 Message Over HTTP
 
 ==== Step 1
 
 Create a new Mule Project with Mule Server 3.6.0 EE as runtime:
 
-image:/docs/download/attachments/131467593/image2015-6-26+9%3A7%3A18.png?version=1&modificationDate=1435344041204[image]
+image:image2015-6-26+9%3A7%3A18.png[image2015-6-26+9%3A7%3A18]
 
 ==== Step 2
 
 Drag a File inbound endpoint to the canvas to create a message source for a flow. Set the Path attribute to “outbox”:
 
-image:/docs/download/attachments/131467593/image2015-6-26+9%3A18%3A1.png?version=1&modificationDate=1435344041104[image]
+image:image2015-6-26+9%3A18%3A1.png[image2015-6-26+9%3A18%3A1]
 
 ==== Step 3
 
 Locate the AS2 Connector on the right hand-side palette:
 
-image:/docs/download/attachments/131467593/image2015-6-26+9%3A19%3A48.png?version=1&modificationDate=1435344041111[image]
+image:image2015-6-26+9%3A19%3A48.png[image2015-6-26+9%3A19%3A48]
 
 ==== Step 4
 
 Drag the connector over to the canvas next to the File message source:
 
-image:/docs/download/attachments/131467593/image2015-6-26+9%3A21%3A35.png?version=1&modificationDate=1435344041117[image]
+image:image2015-6-26+9%3A21%3A35.png[image2015-6-26+9%3A21%3A35]
 
 ==== Step 5
 
@@ -213,55 +214,55 @@ HTTP transport to receive and send AS2 messages.
 
 Click on the Global Elements tab and create an HTTP endpoint:
 
-image:/docs/download/attachments/131467593/image2015-6-26+9%3A23%3A54.png?version=1&modificationDate=1435344041124[image]
+image:image2015-6-26+9%3A23%3A54.png[image2015-6-26+9%3A23%3A54]
 
 ==== Step 6
 
-Give the HTTP endpoint a more descriptive name like “send-as2-http-endpoint”. Set the host, port and path +
+Give the endpoint HTTP connector a more descriptive name like “send-as2-http-endpoint”. Set the host, port and path +
 attributes to point to an AS2 receiver. Click on the Connector Configuration add symbol to bring up the HTTP connector +
 configuration dialog:
 
-image:/docs/download/attachments/131467593/image2015-6-26+9%3A25%3A58.png?version=1&modificationDate=1435344041130[image]
+image:image2015-6-26+9%3A25%3A58.png[image2015-6-26+9%3A25%3A58]
 
 ==== Step 7
 
 Give the HTTP connector a more descriptive name like “as2-http-connector” and press OK to go back to the global HTTP endpoint dialog box:
 
-image:/docs/download/attachments/131467593/image2015-6-26+9%3A36%3A29.png?version=1&modificationDate=1435344041171[image]
+image:image2015-6-26+9%3A36%3A29.png[image2015-6-26+9%3A36%3A29]
 
 ==== Step 8
 
 Press OK to close the global HTTP endpoint dialog box:
 
-image:/docs/download/attachments/131467593/image2015-6-26+9%3A28%3A33.png?version=1&modificationDate=1435344041144[image]
+image:image2015-6-26+9%3A28%3A33.png[image2015-6-26+9%3A28%3A33]
 
 ==== Step 9
 
-In this step, you will make an AS2 connector configuration and bind it to the global HTTP endpoint. From the Global Elements view, create an AS2 Connector Configuration:
+In this step, you make an AS2 connector configuration and bind it to the global HTTP connector. From the Global Elements view, create an AS2 Connector Configuration:
 
-image:/docs/download/attachments/131467593/image2015-6-26+9%3A30%3A2.png?version=1&modificationDate=1435344041151[image]
+image:image2015-6-26+9%3A30%3A2.png[image2015-6-26+9%3A30%3A2]
 
 ==== Step 10
 
-Type “send-as2-http-endpoint” in the attribute Global HTTP Endpoint Reference to bind the AS2 connector to the previously created global HTTP endpoint. Press OK.
+Type “send-as2-http-endpoint” in the attribute Global HTTP Endpoint Reference to bind the AS2 connector to the previously created global HTTP connector. Press OK.
 
-image:/docs/download/attachments/131467593/image2015-6-26+9%3A31%3A14.png?version=1&modificationDate=1435344041157[image]
+image:image2015-6-26+9%3A31%3A14.png[image2015-6-26+9%3A31%3A14]
 
 ==== Step 11
 
 After completing the previous steps, you should have the following in the Global Elements view:
 
-image:/docs/download/attachments/131467593/image2015-6-26+9%3A32%3A54.png?version=1&modificationDate=1435344041164[image]
+image:image2015-6-26+9%3A32%3A54.png[image2015-6-26+9%3A32%3A54]
 
 Back to the Message Flow view, on the AS2 processor, select “AS2” from the Connector Configuration drop-down list and select “Send” from the Operation drop-down list:
 
-image:/docs/download/attachments/131467593/image2015-6-26+9%3A37%3A25.png?version=1&modificationDate=1435344041177[image]
+image:image2015-6-26+9%3A37%3A25.png[image2015-6-26+9%3A37%3A25]
 
 ==== Step 12
 
 Populate the AS2-From and AS2-To attributes. The AS2 -To identifier is typically provided out-of-band by the AS2 receiver.
 
-image:/docs/download/attachments/131467593/image2015-6-26+9%3A38%3A57.png?version=1&modificationDate=1435344041184[image]
+image:image2015-6-26+9%3A38%3A57.png[image2015-6-26+9%3A38%3A57]
 
 ==== Step 13
 
@@ -283,15 +284,15 @@ For the sake of keeping the example simple, no key store is set so no security i
 
 Viewing the receipt returned by the AS2 receiver is optional but useful for testing. Append to the flow a Byte Array to String transformer followed by a Logger processor to print the receipt's content to console.
 
-image:/docs/download/attachments/131467593/image2015-6-26+9%3A41%3A2.png?version=1&modificationDate=1435344041190[image]
+image:image2015-6-26+9%3A41%3A2.png[image2015-6-26+9%3A41%3A2]
 
 Note that the Logger in the screenshot has its Message attribute set to "#[payload]"
 
 ==== Step 15
 
 Finally, run the example as a Mule application:
 
-image:/docs/download/attachments/131467593/image2015-6-26+9%3A41%3A51.png?version=1&modificationDate=1435344041197[image]
+image:image2015-6-26+9%3A41%3A51.png[image2015-6-26+9%3A41%3A51]
 
 Drop a file in the "outbox" directory to send it to the receiver over AS2. If you have followed step 14, you should see the receiver's receipt in the console.
 

anypoint-b2b/_images/B2B_AS2EDI_02.png

@@ -97,10 +97,10 @@ You can define your endpoints 2 different ways:
 
 . Non-prefixed URI:
 +
-[source, xml<multicast:connector name="multicastConnector"/>]
+[source, xml]
 ----
+<multicast:connector name="multicastConnector"/>
 <inbound-endpoint address="multicast://localhost:65433"/>
-
 ----
 
 See the sections below for more information.

anypoint-b2b/_images/B2B_AS2EDI_03.png

@@ -97,10 +97,10 @@ You can define your endpoints 2 different ways:
 
 . Non-prefixed URI:
 +
-[source, xml<multicast:connector name="multicastConnector"/>]
+[source, xml]
 ----
+<multicast:connector name="multicastConnector"/>
 <inbound-endpoint address="multicast://localhost:65433"/>
-
 ----
 
 See the sections below for more information.