The developerWorks Connections platform will be sunset on December 31, 2019. On January 1, 2020, this blog will no longer be available. More details available on our FAQ.

Enterprise Portal Information

Matching: acev11

Message Flow Statistics in ACEv11

Adi H Tags: acev11 ace v11 iib ‎ 1,962 Views

Below blog entry provides details about viewing Message Flow Statistics in ACEv11. ACE Toolkit provides detailed tutorial and content is taken from the tutorial that has the same application for deployment.

Step 1: Import the project given as part of Toolkit to monitor the message flow statistics

This simple application contains a message flow which receives HTTP data and echoes it back to the requesting client. This flow will enable us to respond to some small load on the integration server as we view the server's performance statistics in the Web UI.

Step 2: Create Integration Server and start the WebUI

1. Open an App Connect Enterprise Command Console and run the following command to create a working directory which will be used to store the files which the runtime integration server needs:
mqsicreateworkdir C:\IBM\ACE\StatsServer
where C:\IBM\ACE\StatsServer will be the working directory for integration server.

2. Navigate to your server's working directory and locate the file server.conf.yaml. Open it using your preferred text editor, locate the Statistics section and edit the settings (the comments in the sample help with allowed values, and you will need to remove some # comment characters):
Statistics:
Snapshot:
    accountingOrigin: 'basic'
    nodeDataLevel: 'advanced'
    outputFormat: 'json'
    publicationOn: 'active'
    threadDataLevel: 'basic'
Save and close the file.

3. Back in the App Connect Enterprise Command Console window, start the server with the command:

IntegrationServer --work-dir C:\IBM\ACE\StatsServer --name StatsServer --admin-rest-api 7608 --http-port-number 7808 --console-log

4. In the App Connect Enterprise Toolkit, locate the Integration Explorer view (by default this is located in the bottom left corner), right click on the Integration Servers label and select Connect to an Integration Server. Enter the Host Name as localhost and the port as 7608 and click Finish.

5. Locate the Broker Archive file named StatsBar.bar inside the Application project which you imported earlier named StatsApp, then drag and drop it onto your server named StatsServer.

6. Right click on the server in the Toolkit and launch the WebUI.

Step 3: Execute below command to check the stats in WebUI

Send some messages to the message flow and view statistics in the Web User Interface
1. Navigate to a Command Prompt and run this command a handful of times: (I have run it around 18 times)

curl -X POST http://localhost:7808/request -d HelloWorld

Each execution should receive the same fixed reply message: {"OutputMessage":"This is a fixed reply message!"}

2. Return to the administrative WebUI for the server which you opened in the Prepare stage.

3. When you first open the WebUI you will be looking at information at the Server level. Select the Statistics tab on the navigation bar at the top.

4. After a brief pause you should see a tabular Message flow statistics view which summarises activity at the flow level. Notice that the value in the Total input messages column corresponds to the number of curl requests you made to the server.

5. To get a more detailed view of how data is passing through your flows, change to the Flow node statistics view to see a breakdown for each node in the flow. Click on StatsFlow.

6. In both views, the message flow name links you to another page with information about the message flow. This also has a Statistics tab which includes some graphs which you may like to explore.

Below screenshots for reference,

Modified on by Adi H

ACEv11 Policy Projects and Policies with Overrides

Adi H Tags: iib v11 acev11 ace ‎ 2,373 Views

ACEv11 Policy Projects and Policies with Overrides View Details listed below which is provided as a tutorial in ACE v11 toolkit. Please make sure that you have a proper SMTP connection before working on this scneario. Most of the content below is taken from Toolkit tutorial.

Step 1: Import an application and create a policy project with an SMTP policy

1. Click Import and the HTTPInputEmailOutput application will be imported into your workspace.

2. Open the HTTPInputEmailOutput message flow and look at the EmailOutput node's properties. Note that the Basic property tab has a property named SMTP Server and Port which addresses {MyPolicyProject}:MySMTPPolicy

3. On the Email property tab, note that the property named To Addresses specifies a value of <email id>. This is the email address to which an email will be sent (from your SMTP email provider)

4. On the Email property tab, change the property named From Address to be your email address from which you intend the email to be sent (when ACE connects to your SMTP server)

5. Create a Policy project named MyPolicyProject using the New link in the top right corner of the Application Development view.

6. Create a Policy named MySMTPPolicy of type SMTP (click the New link which appeared inside the empty project you just created). Set the SMTP server name to be your SMTP server. For example, <smtp IP or smtp hostname>:25 Set the Security identity to be the hardcoded string SMTPIdentity (we will map to actual identity using the mqsisetdbparms command in step 2)

Step 2: Create and Configure an Integration Server

1. Open an App Connect Enterprise Command Console, and run the mqsicreateworkdir command to prepare a work directory for an integration server:
mqsicreateworkdir C:\IBM\ACE\PolicyOServer

2. Run the mqsisetdbparms command to define the identity which ACE will use when communicating with your SMTP server:
mqsisetdbparms -w C:\IBM\ACE\PolicyOServer -n smtp::SMTPIdentity -u none -p none (I don't have any user id and password set for my SMTP server)
where C:\IBM\ACE\PolicyOServer is a folder on your file system that the server will use for its working directory.

3. Now, start the integration server using the following command:
IntegrationServer --work-dir C:\IBM\ACE\PolicyOServer --name PolicyOServer --admin-rest-api 7607 --http-port-number 7907 --console-log
where C:\IBM\ACE\PolicyOServer is the same folder on your file system that you used in the last command.

4. After a few seconds the server should report that it has finished initialization and that its HTTP Listener has started listening for connections.

Step 3: Run below URL to demonstrate policy identification and overrides

1. In the App Connect Enterprise Toolkit, connect to your Integration Server PolicyOServer on localhost:7607. Create a Broker Archive file, for example named HTTPInputEmailOutput.bar inside the HTTPInputEmailOutput application project which you imported earlier. Once you have created the BAR file, you need to add to it both the HTTPInputEmailOutput application and the MyPolicyProject policy project. Remember to click the Build and Save button on the BAR editor's prepare tab.

2. Drag and drop deploy the HTTPInputEmailOutput.bar BAR file onto PolicyOServer.

3. Test the message flow by sending HTTP data to it using a client such as cURL:
curl -X POST http://localhost:7907/HTTPInputEmailOutput -d HelloWorld

4. The message flow should echo back the same message to the HTTP client, but you should find that the flow's email Output node has successfully found the SMTP policy you deployed, which in turn used the abstracted userid and password which was defined using mqsisetdbparms, and an email will have been successfully sent.

Below screenshots for reference,

ACEv11 Policy Projects and Policies

Adi H Tags: ace acev11 v11 iib ‎ 1,886 Views

As part of ACEv11 tutorials, below blog entry give details about configuring ACE behavior using Policies. Make sure that the project is imported correctly using applications mentioned in the Tutorials from toolkit.

Step 1: Import the project as part of the tutorials

Step 2:
Create an Integration Server and deploy the file

1. Open an App Connect Enterprise Command Console and run the following command to create a Integration Server,
mqsicreateworkdir C:\IBM\ACE\PolicyServer
where C:\IBM\ACE\PolicyServer will the working directory for PolicyServer Integration Server.

2. Open the policy named MyActivityLogPolicy.policyxml inside the SimplePolicyProject as part of imported project in Step 1

3. Locate the File name property, set the value to C:\IBM\ACE\PolicyServer\ActivityLog.txt and save the policy.

4. Create a Broker Archive file inside SimplePolicyProject named SimpleDeploy.bar

5. Build the application and policy projects into the BAR file:
   - Select the Applications radio button and select the SimpleApp application
   - Select the Policies radio button and select the SimplePolicyProject
   - Click the 'Build and Save' button to generate the contents in the BAR file.

6. Start an Integration Server by typing the following command into the ACE Command Console:

IntegrationServer --name PolicyServer --work-dir C:\IBM\ACE\PolicyServer --admin-rest-api 7606 --http-port-number 7906 --console-log

7. Connect to the Integration Server from the Integration Explorer view in the Toolkit, then drag and drop deploy the SimpleDeploy.bar

Step 3: Follow the following steps to verify the Policy configuration

1. Test the message flow by sending HTTP data to it using a client such as cURL:
   curl -X POST http://localhost:7906/HTTPEcho -d PolicyServerMessage
   The message flow should echo back the same HelloWorld message to the HTTP client. Repeat this test a few times.

   Note: I already have the Echo app deployed onto Integration server that was used earlier and mentioned in this link here, https://www.ibm.com/developerworks/community/blogs/e66e1296-2be2-44a3-bd8f-f94eb69b07e0/entry/ACEv11_Creating_an_Integration_Server?lang=en
   https://www.ibm.com/developerworks/community/blogs/e66e1296-2be2-44a3-bd8f-f94eb69b07e0/entry/ACEv11_Deployment_using_Toolkit?lang=en
   Make sure that this app is started so that we can echo the messages.

2. Navigate to the directory location which was specified when editting the Activity Log policy:
C:\IBM\ACE\PolicyServer and you should see a text file with the name ActivityLog.txt

3. Open this file in your preferred text editor and you should see log entries formatted as comma separated data. Each log line corresponds to one of the curl requests which you just made.

Screenshots given below for reference,

ACEv11 Exploring Admin REST API using Interation Server

Adi H Tags: v11 acev11 ace iib ‎ 2,268 Views

As part of ACE v11 tutorials from ACE v11 Toolkit Product, below blog entry provides details about exploring the Admin REST API with an Integration Server. Content taken from Tutorials of ACEv11 Toolkit.

Step 1: Create and deploy the application

1. Create an Integration Server using below command
IntegrationServer --name RestServer --work-dir C:\IBM\ACE\RestServer --admin-rest-api 7605 --http-port-number 7905 --console-log

2. We will deploy using the following cURL command:

curl -X POST http://localhost:7605/apiv2/deploy --data-binary @C:\IBM\ACE\ACET11\blogworkspace\ExampleApp\ExampleDeploy.bar -H "Content-Type: application/octet-stream"

Where C:\IBM\ACE\ACET11\blogworkspace\ExampleApp\ is the directory location of App Connect Enterprise Toolkit's workspace.

3. Hit the URL, http://localhost:7605/apidocs
You will be presented a page containing comprehensive documentation on the administrative REST API, which can be used to control your Integration Server.

Step 2: Interact with the Integration Server

1. In the web browser tab for your Integration Server (http://localhost:7605/apidocs), on the left side you will see all the available actions in the API.

2. Click on the GET / tab in the list of actions. The body of the docs should change to present you with all the details on this particular action. You'll be presented with the description of the action, its parameters (and their structure), example requests from different languages (curl, python etc.) and examples of the standard responses. At the top of the web page, select the 'Try it' tab.

3. Here you can run the action against your server as an example. Don't change anything from the defaults, and just click 'Send' in the bottom right. You will see the real request to your server and its response.

4. Scroll down and inspect the JSON response, and you will see a few sections:
- The name and type of your server at the very top
- A section called 'actions' which shows you all the valid actions which can be conducted on the server
- Further sections showing content which has been deployed to the server, such as 'applications', 'restApis', 'services' and 'policies', with details on whether they contain any further children.

5. Run a GET /applications to view the currently deployed applications. You will see the application which you deployed earlier, named 'ExampleApp'

6. Run a GET /applications/{application} (changing the Application parameter to be 'ExampleApp') to view details about a particular deployed application.

7. Run a POST /applications/{application}/stop (changing the Application parameter to be 'ExampleApp') to stop the ExampleApp application.

8. Run a POST /applications/{application}/start (changing the Application parameter to be 'ExampleApp') to start the ExampleApp application.

Below screenshots for reference,

Modified on by Adi H

Explore the ACE v11 Web UI

Adi H Tags: iib v11 ace acev11 ‎ 2,216 Views

Below blog entry will be used for exploring the Web UI in ACE v11.

Step 1: Prepare an ACE Web UI for administering multiple servers and nodes

1. Open a ACE Command Console, which we will use to support another Integration Server whose only purpose is to support a variant of the ACE Web UI which allows you to administer multiple Integration Nodes and Servers in your network. This server is not intended to be used to host deployed integrations, so do not attempt to connect to it from a Toolkit (or interact with it via the standard REST administration API). This special server behavior is configured by setting an environment variable named ACE_DASHBOARD. Given that the role of the web UI which will be served by this Integration server is to provide information about multiple servers and nodes running in your network, you will most likely want to configure this form of the web UI to be served using HTTPS. In the example below, we will demonstrate using a keystore which has been populated with a self-signed certificate.

2. In Command Console, create a working directory by running the mqsicreateworkdir command:
mqsicreateworkdir C:\IBM\ACE\Blog\MyDashboardServer

3. Edit the server.conf.yaml file which the above command will have created in the directory C:\IBM\ACE\Blog\MyDashboardServer, with the following details in order to secure the ACE Web UI. Create MyDashboardServerKeyStore directory inside C:\IBM\ACE\Blog\MyDashboardServer directory.
RestAdminListener:
port: 7644
sslCertificate: C:\IBM\ACE\Blog\MyDashboardServer\MyDashboardServerKeyStore\keystore.pfx
sslPassword: adminRestApi::sslpwd
Remember to save the server.conf.yaml file.

4. Create the directory C:\MyDashboardServerKeyStore and then use keytool to create a keystore file containing your self-signed certificate:
keytool -genkey -alias ACE_alias -keystore C:\IBM\ACE\Blog\MyDashboardServer\MyDashboardServerKeyStore\keystore.pfx -storepass change1t -storetype pkcs12 -keyalg RSA
When prompted, provide suitable values for your self-signed certificate's values.

5. Use the mqsisetdbparms command to specify the password for the keystore to the Integration Server:
mqsisetdbparms -w C:\IBM\ACE\Blog\MyDashboardServer -n adminRestApi::sslpwd -u ignore -p change1t

6. Set the environment variable ACE_DASHBOARD=true by typing:
set ACE_DASHBOARD=true

7. Finally, start a new integration server by typing the command:
IntegrationServer --name MyDashboardServer --work-dir C:\IBM\ACE\Blog\MyDashboardServer --console-log

Step 2: Access WebUI and add the connections

In your web browser connect to the URL https://localhost:7644. Your browser will ask you if you are happy to connect based upon the information which is in the self-signed certificate which you created earlier. Once connected, in the top right corner of this web UI you should see a button which allows you to toggle your view between Integrations, Servers and Nodes. To the left of this you will see the option to Edit Connections:
- Click on 'Edit Connections'
- Under the Connections tab, click 'Add'
- Select 'Integration Server', use the name 'MyServer2' (or any name you like to uniquely identify the standalone server), set the address to 'http://localhost:7611', the Username to 'webuser' and the Password to 'password123'
- Click 'Save' in the bottom right of the window and the Servers view should show your standalone integration server.
Repeat the process to Edit Connections and add the Integration Node:
- Click on 'Edit Connections'
- Under the Connections tab, click 'Add'
- Select 'Integration Node', use the name 'MyNode2' (or any name you like to uniquely identify the node which you created earlier), set the address to 'http://localhost:4420' (for this connection you don't need a Username and Password)
- Click 'Save' in the bottom right of the window and in the Servers view, you should now be able to see tiles representing both the standalone server, and the servers which are owned by the Integration Node all together in the same Web UI.

Screenshots given below for reference,

Modified on by Adi H

ACEv11 Exploring the Web UI to administer Integration Node

Adi H Tags: acev11 iib ace v11 ‎ 1,645 Views

Below blog entry will be used for exploring the Web UI and then using the web user interface to start administering an Integration Node in ACE v11.

Step 1: Prepare an ACE Web UI for administering an Integration Node
Create an Integration Node and create three integration servers which will be owned by it. Open a new ACE Command Console and type below commands,

mqsicreatebroker MyNode2 -P 4420
mqsistart MyNode2
mqsicreateexecutiongroup MyNode2 -e MyNodeIntServer21
mqsicreateexecutiongroup MyNode2 -e MyNodeIntServer22
mqsicreateexecutiongroup MyNode2 -e MyNodeIntServer23

Step 2: Use WebUI to see the Integration servers in the Integration Node and create a new Integration Server,

In web browser connect to the URL http://localhost:4420. This will show you information about the Integration Node named MyNode2, and its three servers MyNodeIntServer21, MyNodeIntServer22 and MyNodeIntServer23 as created in step 1. You should see a tile representing each server, which you can click into to display their content, which will be empty to start with until you deploy something.

Step 3: Create a new Integration Server from WebUI
In the server view of the Integration Node Web UI, on the right you will find a button labelled 'Create a Server'. You can use this option to create another integration server which is owned by the node.

Screenshots below for reference,

Modified on by Adi H

ACEv11 Exploring the Web UI to administer Integration Server

Adi H Tags: ace v11 iib acev11 ‎ 2,299 Views

Below blog entry will be used for exploring the Web UI and then using the web user interface to start administering an Integration Server in ACE v11.

Step 1: Open Getting started tutorials and then click on ACEv11 - Exploring the Web UI View Details.

When you click Import, the following projects will be created in your workspace:
• The Application Transformation_Map provides a simple HTTP driven message flow which transforms an XML message.
• The Integration Service TemperatureConverter provides an HTTP web service (based on a WSDL definition) which offers two operations for converting temperatures in celsius to fahrenheit and vice versa.
• The REST API CustomerDatabaseV1 provides a REST interface for managing a set of customer records.

These three types of project provide examples of the main kinds of integration which users deploy to the ACE runtime. Later in the tutorial we will deploy them and view them in the Web UI. The import process also provides a Broker Archive file named Everything.bar inside the project named BARfiles

Step 2: Prepare an ACE Web UI for administering an Integration Server
1. Assuming you are using a Windows platform, open an App Connect Enterprise Command Console and create a working directory by running the mqsicreateworkdir command:
mqsicreateworkdir C:\IBM\ACE\Blog\MyServer2
2. Edit the server.conf.yaml file which the above command will have created in the directory C:\IBM\ACE\Blog\MyServer2. To turn on Basic Authentication for users logging in to the ACE Web UI, find the line #basicAuth: true and uncomment the line by removing the leading # symbol. Save the server.conf.yaml file.
3. Use the mqsiwebuseradmin command to specify a web userid and password which will be used to login to the Web UI:
mqsiwebuseradmin -w C:\IBM\ACE\Blog\MyServer2 -c -u webuser -a password123
4. Start an integration server using the following command:
IntegrationServer --name MyServer2 --work-dir C:\IBM\ACE\Blog\MyServer2 --admin-rest-api 7611 --http-port-number 7911 --console-log

Step 3: Open WebUI and perform a deployment using the UI by clicking on Deploy button

Screenshots below for reference

We have used webuser and password123 to set the parameter. Login with these details,

Click on Deploy present at right hand side of the page,

Everything.bar file will be present in Workspace of the toolkit (from where imported in step 1). below screenshot after clicking on the Deploy button and Command prompt showing the log messages during the deployment of the bar file.

Modified on by Adi H

ACEv11 Deployment using Toolkit

Adi H Tags: iib ace acev11 ‎ 1,707 Views

In Continuation to previous blog entry, we will perform a deployment on the integration server using Toolkit.

Step 1: Open toolkit and deploy the bar file that got imported using the tutorials. SimpleDeploy.bar will be deployed on to the Integration Server.

Drag the bar file on to the Integration server MyServer1 to complete the deployment.

Step 2: Open comand prompt to check the log messages and then verify the deployed application lised as per the tutorial. Open another command prompt to check the application result by hitting the URL listed below,

http://localhost:7910/Echo -d HelloWorld

A mesage HelloWorld will appear by running the URL through curl.

Modified on by Adi H

ACEv11 Creating an Integration Node

Adi H Tags: v11 ace acev11 ‎ 1,996 Views

In continuation with previous blog entry, below steps contain details about creating an Integration Node in ACE v11.

Step 1: Create a Integration Server which is owned by an Integration Node
1. Open a new App Connect Enterprise Command Console and create an integration node using the following command:
mqsicreatebroker MyNode1

2. Start the Integration Node using the following command:
mqsistart MyNode1

3. Create an Integration Server which is owned by the Integration Node using the following command:
mqsicreateexecutiongroup MyNode1 -e MyNodeIntServer1

4. Make a note of the administration port which the Integration Node has opened using the mqsilist command.
MyNode1 http://localhost:4419

Step 2: Connect to the Integration Node MyNode
1. Still in the Integration Explorer view in the ACE Toolkit, right click on the Integration Nodes label and select Connect to an Integration Node

2. Enter the Host Name as localhost and the port number which was reported to you using the mqsilist command which we ran in Step 1.

3. Your node labelled MyNode1, and its server labelled MyNodeIntServer1 should appear with green arrows showing that they are currently running.

Screenshots given below for reference,

Provide localhost and Integration server port that got created in previous step

In the pop up window provide localhost under hostname and port as 4419.

Above list shows the nodes and servers that were created earlier.

Modified on by Adi H

ACEv11 Creating an Integration Server

Adi H Tags: app server connect acev11 ace iib integration v11 ‎ 3,383 Views

As part of ACE v11 product there are guided tutorials that explain how to create Integration server and then perform deployments in App Connect Enterprise v11.

Below details are taken from tutorials mentioned in Toolkit. I have already Installed ACE v11 on my system.

Step 1: Creating an Integration server

1. As I am using a Windows platform, open an App Connect Enterprise Command Console and start an integration server using the following command:
IntegrationServer --work-dir C:\IBM\ACE\Blog\MyServer1 --name MyServer1 --admin-rest-api 7610 --http-port-number 7910 --console-log
where C:\IBM\ACE\Blog\MyServer1 is a folder on your file system that the server will use for its working directory. I have already created IBM/Blog directory before running the command.

2. After a few seconds the server should report that it has finished initialization and that its HTTP Listener has started listening for connections. This completes creating a standalone Integration Server hosted locally on your own machine.

Step 2: Connect to the Integration Server
1. Return to the Integration Explorer view in the ACE Toolkit. By default, this is located directly below the Application Development tab in the bottom left corner.

2. Right click on the Integration Servers label and select Connect to an Integration Server

3. Enter the Host Name as localhost and the port as 7610. Remember this is the '--admin-rest-api' port which was used when starting the server. Click Finish (As part of 2. in Step 1)

4. Your server labelled MyServe1r should appear with a green arrow showing that the server is currently running.

Step by Step Screenshots below for reference.