How to insert a row into DB2 using Websphere Cast Iron.
Step 1: Create an DB2 Endpoint by specifying the following information:
- DB2 Database Name
- DB2 Host Name
- DB2 Port Number
- DB2 Username
- DB2 Password
Please make sure that the Cast Iron appliance or Virtual image has rights to insert a row onto DB2. This can be done by specifying the Privileges in the DB2 Control Centre.
Step 2: Test the connection to verify all information is correct.
Step 3: Create your integration flow
Step 4: Specify the DB2 Endpoint created in Step 1 and select the table and row you want the data to be inserted into
Step 5: Create the input and output maps for both activities
Step 6: Verify and test the flow.
This flow will update a website that is located in a cloud environment (like Amazon EC2) and updated an on-premise DB2 instance.
How to integrate file transfer with Cast Iron
Step 1: Create or start your ftp server (in this case I just use FileZilla Server)
Step 2: In your file server create a user or role and specify the permissions of the user and some username and password
Step 3: Create an FTP endpoint by specifying:
- FTP Host Name
- FTP Port Number
- FTP Username
- FTP Password
Step 4: Test the connection by clicking on the ‘Test Connection’ button.
Step 5: Create your FTP integration flow
In this flow we will be moving Files from a Cloud Server to a local user machine
Step 6: Specify the folder of the file from origin to destination
Step 7. Test the integration flow by dropping a file into the origin folder and see if it has been move to the destination folder.
This is my first of many integration flows in Websphere Cast Iron. See the steps below to create a Cast Iron Integration Flow.
Step 1; Open Cast Iron Studio and create a new project (My project was called Project 1)
Step 2: An orchestration will be created for you automatically which you can rename. The following step is to create an endpoint, in this instance we will create an HTTP endpoint that listens on port 80.
Step 3: Below is all the setting for the HTTP Endpoint that you can set:
Step 4: Drag the following 2 activities into your editor: Receive Request and Post Request and connect your HTTP endpoint. It must look like the following:
Step 5: Click on the Send Response Activity and click on Map Inputs, then right click on the Body field and select ‘Define Default Value’. Enter in ‘Hello World!’ or any other default value.
Step 6: Validate the project by clicking on the Validate Project button in the IDE, the following message is expected.
Step 7: Publish the flow to my virtual appliance by specifying the IP address of my Web Interface by clicking on Publish Project and completing the relevant information.
Step 8: Verify that the project has been published successfully.
Step 9: Log into your Virtual Appliance to see the project (Project1) being published. See project in Red Box.
Step 10: Start the Project by clicking on the green play button.
Step 11: Open Cast Iron HTTP Post Utility and the Data IP address followed by the URI that was specified in the Receive Request activity and click Submit.
Last Step: Enjoy the success of your first Cast Iron flow.
Cast Iron must be one of the easiest and most user friendly integration tools that I have used. This whole exercise was done in less than 5 min…just show that their motto “Integration in days” is definitely true.
So where does Cast Iron fit into the IBM Websphere stack?Cast Iron primary used for Cloud to on-premise integration. Where you can create a message flow diagram using the Cast Iron Studio and deploy that flow to the following environments:
1. Cast Iron Appliance (which is now the Datapower XH35 Cast Iron V5.1)
2. The virtual Cast Iron appliance which can be installed in VMWare.
3. Amazon EC2
So how can you integrate Cast Iron with current IBM ESB’s:
1. Datapower XI50
2. Websphere Message Broker
3. WESB (Websphere ESB)
The simple answer is:
1. Websphere MQ
2. Web Services
Cast Iron integrates natively to Websphere MQ and any Web Services call can be made. This is a great addition to the IBM Stack and will be a great solution for customers that want to do any cloud integration.
This means that by using the web browser of any computer or mobile telephone, you can edit or display your files (photos, music, movies, documents, presentations, etc.) and see them just as you left them the last time you accessed the system, regardless of whether you are at home or in an Internet café abroad. In short, your data are stored on the network rather than in a specific location.
The main difference between EyeOs and the majority of cloud computing services is that they ask for your data and they give you the service in exchange for it. Because EyeOs is free software, you can decide where you keep your server and, more importantly, your data. We do not ask you to send us your data and you can install EyeOs in an environment that is completely under your control
The Smart Business Storage Cloud is based on IBM’s Scale-out File Services (SOFS) and is a variation on the WebSphere CloudBurst Appliance package IBM launched in June. Customers can run SOFS on either IBM System x or BladeCenter servers. SOFS is a management “wrapper” around IBM’s General Parallel File System (GPFS). On its own, GPFS is intended for specialized high-performance computing (HPC) environments and is administered using a command-line interface (CLI), according to Tom Clark, an IBM distinguished engineer. SOFS adds reporting and a Web-based user interface. SOFS has been offered before as an IBM Global Technology Services (GTS) engagement, but the Smart Business Storage Cloud is a pre-configured package sent whole from the factory and deployed with services as an option.