more

ajax/0.3.9/modules/ROOT/pages/index.adoc

@@ -2,7 +2,7 @@
 :keywords: anypoint, connectors, ajax
 :page-aliases: 3.9@mule-runtime::ajax-connector.adoc
 
-image::ajax-icon-no-caption.png[ajax icon]
+image::ajax-icon-no-caption.png["Ajax icon"]
 
 The Ajax Connector creates a transport channel to send messages asynchronously to and from an Ajax server, which communicates with external Web resources.
 *Ajax* is an acronym for *Asynchronous JavaScript and XML*, a cluster of related technologies that facilitate the creation of asynchronous Web applications.
@@ -32,7 +32,7 @@ Configure the tabs as shown.
 
 == General Tab
 
-image::ajax-connector-general.png[Studio-ajax-gen]
+image::ajax-connector-general.png["General tab in Ajax Connector configuration panel"]
 
 [%header%autowidth.spread]
 |===
@@ -44,7 +44,7 @@ image::ajax-connector-general.png[Studio-ajax-gen]
 
 == Advanced Tab
 
-image::ajax-connector-advanced.png[Studio-ajax-outbound-adv]
+image::ajax-connector-advanced.png["Advanced tab in Ajax Connector configuration panel"]
 
 
 [%header%autowidth.spread]
@@ -63,7 +63,7 @@ image::ajax-connector-advanced.png[Studio-ajax-outbound-adv]
 
 == Transformers Tab
 
-image::ajax-connector-transformers.png[Studio-ajax-trans]
+image::ajax-connector-transformers.png["Transformers tab in Ajax Connector configuration panel"]
 
 [%header%autowidth.spread]
 |===

amazon-dynamodb/1.5/modules/ROOT/pages/amazon-dynamodb-connector-examples.adoc

@@ -17,7 +17,7 @@ This example shows how to use Amazon DynamoDB connector to create an Amazon Dyna
 The following screenshot shows an Anypoint Studio flow for creating an Amazon DynamoDB table:
 
 .Use this sample flow to create an Amazon DynamoDB table.
-image::amazon-dynamodb-create-table-flow.png[Studio flow for creating an Amazon DynamoDB table]
+image::amazon-dynamodb-create-table-flow.png["Studio flow for creating an Amazon DynamoDB table"]
 
 [[preliminary-steps-create]]
 === Preliminary Steps
@@ -46,12 +46,12 @@ Configure `HTTP Listener` to listen for HTTP requests on the `/createtable` path
 . In the *Host* field, select `localhost`:
 +
 .Select `localhost` in the *Host* field to listen for HTTP requests on your local computer.
-image::amazon-dynamodb-http-global-element.png[HTTP Listener global element]
+image::amazon-dynamodb-http-global-element.png["HTTP Listener global element"]
 . Click *OK*.
 . In the *Path* field on the *Listener* tab, enter `/createtable`:
 +
 .Enter `/createtable` in the *Path* field to listen for HTTP requests on the `/createtable` path.
-image::amazon-dynamodb-http-prop.png[HTTP Listener tab]
+image::amazon-dynamodb-http-prop.png["HTTP Listener tab"]
 
 === Configure the Create Table Operation
 
@@ -81,7 +81,7 @@ Configure the `Create Table` operation to create a table named `Issues`:
 The following screenshot shows an example of configuring a global element for Amazon DynamoDB Connector:
 
 .Configure the credentials needed to access Amazon DynamoDB in the *Connection* section of the global element.
-image::amazon-dynamodb-global-element.png[Amazon DynamoDB global element]
+image::amazon-dynamodb-global-element.png["Amazon DynamoDB global element"]
 --
 +
 . Click *Test Connection* to confirm that Mule can connect with the Amazon DynamoDB instance:
@@ -113,7 +113,7 @@ image::amazon-dynamodb-global-element.png[Amazon DynamoDB global element]
 The following screenshot shows an example of configuring the `Create table` operation:
 +
 .Enter values for the `Create table` operation fields.
-image::amazon-dynamodb-create-table-props.png[Create table operation fields]
+image::amazon-dynamodb-create-table-props.png["Create table operation fields"]
 +
 In this screenshot:
 
@@ -274,7 +274,7 @@ Configure a `Logger` component to print to the Mule console the response generat
 . Enter `#[payload]` in the *Message* field on the *Logger* tab.
 +
 .Enter `#[payload]` in the *Message* field to print the operation's response to the Mule console.
-image::amazon-dynamodb-logger-props.png[Logger tab]
+image::amazon-dynamodb-logger-props.png["Logger tab"]
 
 === XML for the Complete Create Table Example
 
@@ -415,7 +415,7 @@ This example shows how to use Amazon DynamoDB connector to delete an Amazon Dyna
 The following screenshot shows an Anypoint Studio flow for deleting an Amazon DynamoDB table:
 
 .Use this sample flow to delete an Amazon DynamoDB table.
-image::amazon-dynamodb-delete-table-flow.png[Studio flow for deleting an Amazon DynamoDB table]
+image::amazon-dynamodb-delete-table-flow.png["Studio flow for deleting an Amazon DynamoDB table"]
 
 === Preliminary Steps
 
@@ -547,7 +547,7 @@ When the operation has returned all pages of data, the `LastEvaluatedKey` value
 The following screenshot shows an Anypoint Studio flow for scanning an Amazon DynamoDB table:
 
 .Use this sample flow to scan an Amazon DynamoDB table.
-image::amazon-dynamodb-scan-flow.png[Studio flow for scanning an Amazon DynamoDB table]
+image::amazon-dynamodb-scan-flow.png["Studio flow for scanning an Amazon DynamoDB table"]
 
 === Preliminary Steps
 

amazon-dynamodb/1.5/modules/ROOT/pages/amazon-dynamodb-connector-studio.adoc

@@ -102,7 +102,7 @@ Enter the following information on the *General* tab of the *Global Element Prop
 The following screenshot shows an example of configuring Basic authentication:
 
 .Basic authentication fields
-image::amazon-dynamodb-basic-authentication.png[To configure authentication, select `Basic` in the *Connection* field and then complete the fields on the *General* tab.]
+image::amazon-dynamodb-basic-authentication.png["Configure authentication by selecting Basic in the Connection field and then complete the fields on the General tab"]
 
 The first item shows where to specify that the connector will use Basic authentication. The second item shows the *General tab*, which contains fields related to Basic authentication.
 
@@ -126,7 +126,7 @@ Enter the following information on the *General* tab of the global element confi
 The following screenshot shows an example of configuring Role authentication:
 
 .Role authentication fields
-image::amazon-dynamodb-role-authentication.png[To configure Role authentication, select `Role` in the *Connection* field and then complete the fields on the *General* tab.]
+image::amazon-dynamodb-role-authentication.png["Configure Role authentication by selecting Role in the Connection field and then complete the fields on the General tab"]
 
 The first item shows where to specify that the connector will use Role authentication. The second item shows the *General tab*, which contains fields related to Role authentication.
 

amazon-ec2/2.5/modules/ROOT/pages/amazon-ec2-connector-examples.adoc

@@ -7,7 +7,7 @@ The example includes configuring global elements for Anypoint Connector for Amaz
 
 The following image shows the Mule flow for this example:
 
-image::amazon-ec2-create-volume-usecase-flow.png[Flow for creating an EBS volume]
+image::amazon-ec2-create-volume-usecase-flow.png["Flow for creating an EBS volume"]
 
 This example uses variables for some field values. You can either:
 
@@ -45,7 +45,7 @@ amazon.sessionToken=<Session Token>
 +
 The following image shows an example of the *HTTP Listener* global element configuration:
 +
-image::http-listener-config.png[Global element configuration for HTTP Listener]
+image::http-listener-config.png["Global element configuration for HTTP Listener"]
 +
 .. Click *OK*.
 . Drag the Amazon EC2 Connector *Create volume* operation next to the *Listener* component.
@@ -67,7 +67,7 @@ Region to select from the drop-down menu for the Amazon EC2 client
 +
 The following image shows an example of what the configuration looks like:
 +
-image::mule-amazon-ec2-global-config.png[EC2 global configuration]
+image::mule-amazon-ec2-global-config.png["EC2 global configuration"]
 +
 The corresponding XML looks like this:
 +
@@ -107,7 +107,7 @@ Size of the volume in gibibytes (GiBs). This example uses `5`.
 +
 The default volume type is *Standard*.
 +
-image::amazon-ec2-create-volume-props.png[publish message connector props]
+image::amazon-ec2-create-volume-props.png["Publish message connector props"]
 +
 . Verify that your XML looks like this:
 +
@@ -130,7 +130,7 @@ This prints the volume ID of the EBS volume.
 +
 The following image shows the *Set Payload* configuration:
 +
-image::amazon-ec2-create-volume-payload.png[EC2 Create Volume payload transformer]
+image::amazon-ec2-create-volume-payload.png["EC2 Create Volume payload transformer"]
 
 == Add and Configure the Logger Component
 
@@ -142,7 +142,7 @@ The *Logger* component displays the volume ID that is transformed by the *Set Pa
 * *Level* +
 `INFO`
 +
-image::amazon-ec2-create-volume-logger-props.png[EC2 create volume logger]
+image::amazon-ec2-create-volume-logger-props.png["EC2 create volume logger"]
 +
 . Save the project.
 

amazon-kinesis/1.0/modules/ROOT/pages/amazon-kinesis-connector-examples.adoc

@@ -10,15 +10,15 @@ The following screenshots show the Anypoint Studio app flows for this example:
 
 * This flow uses the *Put Records* operation to put data into the Amazon Kinesis data stream. In this flow, *HTTP > Listener* receives a query parameter named *data* that sets the payload for the *Put Record* operation. It uses a query parameter named *partitionKey* to set the partition key value for the *Put Record* operation.
 +
-image::amazon-kinesis-example-put-record.png[Put Record operation flow]
+image::amazon-kinesis-example-put-record.png["Put Record operation flow"]
 +
 * This flow uses the *Listener* source to listen for new data records:
 +
-image::amazon-kinesis-example-listener.png[Listener source flow]
+image::amazon-kinesis-example-listener.png["Listener source flow"]
 +
 * This flow uses the *Listener* source to listen for new data records. After receiving the new records, it calls the *Checkpoint* operation to set a manual checkpoint:
 +
-image::amazon-kinesis-example-checkpoint.png[Checkpoint operation flow]
+image::amazon-kinesis-example-checkpoint.png["Checkpoint operation flow"]
 
 == XML Code for This Example
 

amazon-lambda/1.1/modules/ROOT/pages/amazon-lambda-connector-examples.adoc

@@ -34,11 +34,11 @@ Configure an HTTP Listener source to initiate the Amazon Lambda Connector *Invok
 . In *Mule Palette*, select *Amazon Lambda Connector > Invoke*.
 . Drag *Invoke* to the Studio canvas to the right of the *Listener* source:
 +
-image::amazon-lambda-simple-invoke-example.png[Simple invoke example flow in Studio]
+image::amazon-lambda-simple-invoke-example.png["Simple invoke example flow in Studio"]
 +
 . Configure the *Invoke* operation:
 +
-image::amazon-lambda-simple-invoke-example-properties.png[Simple invoke operation General properties configuration]
+image::amazon-lambda-simple-invoke-example-properties.png["Simple invoke operation General properties configuration"]
 +
 In this example, the function name is supplied in the `environment.properties` file as `$config.functionName`.
 +

amazon-rds/1.3/modules/ROOT/pages/index.adoc

@@ -83,12 +83,12 @@ To use Amazon RDS Connector in your Mule application, configure a global Amazon
 . On the Global Configuration Elements screen, click *Create*. +
 The following window displays:
 +
-image::amazon-rds-config-global-wizard.png[Global Configuration Elements Wizard]
+image::amazon-rds-config-global-wizard.png["Global Configuration Elements Wizard"]
 +
 . In the Choose Global Type wizard, expand *Connector Configuration*, select *Amazon RDS Configuration*, and click *Ok*. +
 The following window displays:
 +
-image::amazon-rds-create-db-instance-config.png[Create DB Instance Configure]
+image::amazon-rds-create-db-instance-config.png["Create DB Instance Configure"]
 +
 . Configure the parameters according to instructions below:
 +
@@ -253,7 +253,7 @@ Replace `x.x.x` with the version that corresponds to the connector you are using
 This demo Mule application creates a DB instance.
 
 
-image::amazon-rds-create-db-instance-use-case-flow.png[Creating a DB instance]
+image::amazon-rds-create-db-instance-use-case-flow.png["Creating a DB instance"]
 
 . Create a new Mule Project in Anypoint Studio.
 . Add the following properties to the `mule-artifact.properties` file for your Amazon RDS credentials and place it in the project's `src/main/resources` directory.
@@ -267,7 +267,7 @@ config.region=<Region>
 +
 . Drag an HTTP Listener operation onto the canvas and configure the following parameters:
 +
-image::amazon-rds-http-props.png[rds http config props]
+image::amazon-rds-http-props.png["RDS HTTP config props"]
 +
 [%header,cols="30s,70a"]
 |===
@@ -323,7 +323,7 @@ output application/java
 |===
 .. Your configuration should look like this:
 +
-image::amazon-rds-create-db-instance-config.png[rds use case config]
+image::amazon-rds-create-db-instance-config.png["RDS use case config"]
 +
 .. The corresponding XML configuration should be as follows:
 +
@@ -354,7 +354,7 @@ image::amazon-rds-create-db-instance-config.png[rds use case config]
 |Allocated storage| A number representing the storage in GB.
 |===
 +
-image::amazon-rds-create-db-instance-param-config.png[create db instance parameter props]
+image::amazon-rds-create-db-instance-param-config.png["Create DB instance parameter props"]
 +
 . Verify that your XML looks like this:
 +

amazon-redshift/1.0/modules/ROOT/pages/amazon-redshift-connector-example.adoc

@@ -188,10 +188,10 @@ If this doesn't work, add the Amazon Maven repository to your `pom.xml` file and
 The following images show the Amazon S3 and Amazon Redshift configurations:
 
 .Amazon S3 Configuration
-image::s3-configuration.png[Amazon S3 configuration]
+image::s3-configuration.png["Amazon S3 configuration"]
 
 .Amazon Redshift Configuration
-image::redshift-configuration.png[Amazon Redshift configuration]
+image::redshift-configuration.png["Amazon Redshift configuration"]
 
 [[prepare-data-file]]
 == Prepare the Data File
@@ -217,15 +217,15 @@ The following screenshots show the Anypoint Studio app flows for this example:
 
 * This flow creates the Amazon Redshift table, Amazon S3 bucket and object:
 +
-image::create-flow.png[Create the Redshift table Amazon S3 bucket and Amazon S3 object flow]
+image::create-flow.png["Create the Redshift table Amazon S3 bucket and Amazon S3 object flow"]
 +
 * This flow executes the `COPY` command, which leverages the Amazon Redshift massively parallel processing (MPP) architecture to load data in parallel from a file in an Amazon S3 bucket:
 +
-image::execute-flow.png[Execute the Copy command flow]
+image::execute-flow.png["Execute the Copy command flow"]
 +
 * This flow deletes the Amazon Redshift table and Amazon S3 bucket:
 +
-image:delete-flow.png[Delete the Amazon Redshift table and Amazon S3 bucket flow]
+image:delete-flow.png["Delete the Amazon Redshift table and Amazon S3 bucket flow"]
 
 == Run the Example
 

amazon-s3/6.3/modules/ROOT/pages/amazon-s3-connector-examples.adoc

@@ -35,7 +35,7 @@ image::flow.png["Studio 7 Visual Studio Icon Flow. The flow shows HTTP Listener,
 . Configure the global element properties, and then click *OK*.
 . Configure the connector parameters:
 +
-image::s3_config.png[Connector Properties - General tab]
+image::s3_config.png["Connector Properties General tab"]
 +
 [%header%autowidth.spread]
 |===
@@ -49,7 +49,7 @@ image::s3_config.png[Connector Properties - General tab]
 +
 . Drag the *Create Bucket* operation into the flow.
 +
-image::create_bucket.png[S3 Connector Create Bucket in S3 General Tab]
+image::create_bucket.png["S3 Connector Create Bucket in S3 General Tab"]
 +
 [%header%autowidth.spread]
 |===
@@ -62,7 +62,7 @@ image::create_bucket.png[S3 Connector Create Bucket in S3 General Tab]
 +
 . Add an HTTP > Connector to request the MuleSoft logo from MuleSoft.
 +
-image::request.png[HTTP > Connector - General Tab]
+image::request.png["HTTP Connector General Tab"]
 +
 [%header%autowidth.spread]
 |===
@@ -74,7 +74,7 @@ image::request.png[HTTP > Connector - General Tab]
 +
 . Drag the *Put Object* operation into the flow to create the requested MuleSoft logo in the selected Amazon S3 bucket.
 +
-image::put_object.png[S3 Connector Create Logo Object in S3 Bucket General Tab]
+image::put_object.png["S3 Connector Create Logo Object in S3 Bucket General Tab"]
 +
 [%header%autowidth.spread]
 |===
@@ -89,7 +89,7 @@ image::put_object.png[S3 Connector Create Logo Object in S3 Bucket General Tab]
 +
 . Drag the *Get Object* operation into the flow to get the newly created MuleSoft logo image object from the bucket.
 +
-image::get_object.png[S3 Connector Get Image General Tab]
+image::get_object.png["S3 Connector Get Image General Tab"]
 +
 [%header%autowidth.spread]
 |===
@@ -102,7 +102,7 @@ image::get_object.png[S3 Connector Get Image General Tab]
 +
 . Drag the *Delete Object* operation into the flow to delete the object. Because the *Delete Object* operation’s return type is void, the payload contains the object returned by the *Get Object* operation.
 +
-image::delete_object.png[S3 Connector Delete S3 Bucket General Tab]
+image::delete_object.png["S3 Connector Delete S3 Bucket General Tab"]
 +
 [%header%autowidth.spread]
 |===
@@ -115,7 +115,7 @@ image::delete_object.png[S3 Connector Delete S3 Bucket General Tab]
 +
 . Drag the *Delete Bucket* operation into the flow to delete the bucket. Because the *Delete Bucket* operation’s return type is void, the payload contains the object returned by the *Get Object* operation.
 +
-image::delete_bucket.png[S3 Connector Delete S3 Bucket General Tab]
+image::delete_bucket.png["S3 Connector Delete S3 Bucket General Tab"]
 +
 [%header%autowidth.spread]
 |===

amazon-secrets-manager-properties-provider/1.0/modules/ROOT/pages/amazon-secrets-manager-examples.adoc

@@ -23,7 +23,7 @@ Anypoint Connectors can use Amazon Secrets Manager Properties Provider in their
 |Role ARN a| String | Uniquely identifies a role to gain cross-account access. |  |
 |===
 
-image::amazon-secrets-manager-properties.png[Example of Amazon Secrets Manager Properties Provider in Global Element Properties window of Anypoint Studio]
+image::amazon-secrets-manager-properties.png["Example of Amazon Secrets Manager Properties Provider in Global Element Properties window of Anypoint Studio"]
 
 In the *Configuration XML* editor, the configuration looks like this:
 
@@ -50,7 +50,7 @@ aws secretsmanager create-secret --name aws-credentials   --secret-string '{"acc
 . Set *Access Key* to `${aws-secrets::aws-credentials}.accessKey`.
 . Set *Secret Key* to `${aws-secrets::aws-credentials}.secretKey`.
 
-image::aws-sm-json-1.png[Example of Amazon Secrets Manager Properties Provider configuration for Amazon S3 Connector with JSON expression]
+image::aws-sm-json-1.png["Example of Amazon Secrets Manager Properties Provider configuration for Amazon S3 Connector with JSON expression"]
 
 In the *Configuration XML* editor, the configuration looks like this:
 
@@ -77,7 +77,7 @@ In the *Amazon S3 Configuration* global element properties window:
 . Set *Access Key* to `${aws-secrets::accessKey}`.
 . Set *Secret Key* to `${aws-secrets::secretKey}`.
 
-image::aws-sm-json-2.png[Example of Amazon Secrets Manager Properties Provider configuration for Amazon S3 Connector with a string value]
+image::aws-sm-json-2.png["Example of Amazon Secrets Manager Properties Provider configuration for Amazon S3 Connector with a string value"]
 
 In the *Configuration XML* editor, the configuration looks like this: