Asim Saddal

The purpose of this article is to describe the steps involved in configuring Datapower services for the browser-based HTTP type requests. The commonly used methods for such requests are either the POST or GET HTTP method. Datapower Configurations 1. For the testing purpose create a loopback pass-through XML Firewall. 2. Create a new Multi-Protocol Gateway with the following values Input Values Name HTTPBrowserMPGW Type static-backend Response Type Non-XML Request Type Non-XML Backend URL   3. Create a HTTP Front side handler with the following values Input Values Name HTTPBrowserFSH Local IP Address Port 81 Allow Methods and Version GET (and all the other default values) 4. At the Multi-Protocol Gateway screen, click on the "Advance" tab menu and click on "Process Messages Whose Bod... (more)

General Best Practices for WebSphere Application Environments

This article provides a list of general best practices to apply to any WebSphere Application Server V7 and V8 environment. However, some of the recommendations only apply to specific conditions and scenarios. These recommendations could be used to set up any WebSphere environment. General Best Practices for WebSphere Application Environments 1. All WebSphere Application processes should be running as non-admin/root user. It's not a good practice to run a process as an admin/root user. For obvious reasons, you don't want more folks to know about the admin/root password and general... (more)

Enterprise Framework Service for WebSphere Datapower

All services running inside the Datapower need to be installed on the appliance IP address and on the port. As the number of services increase on the appliance, it does create complexity and following underline issues to any environment: Exposure of internal ports (and IP address in some cases) to outside their hosting network. Firewall configuration to allow traffic on different ports (and IP addresses) of Datapower Maintaining IP addresses and ports as the number of services increases on the appliance There may be other solutions to handle the above mentioned issues but one of ... (more)

WebSphere Datapower FTP Polling Functionality Use Cases

The Datapower appliances support the use of the FTP protocols for message transport. The purpose of this article is to present number of common use case scenarios for FTP polling, illustrating correct configurations of the device to support the use case. The use case scenarios are as follows: 1- FTP Poller - polling files in one directory and transfer them to another directory 2- FTP Poller – polling files from FTP SERVER and forward them to another service 3- FTP Poller (sFTP – FTP over SSL) - polling files from FTP SERVER and forward them to another service 4- FTP Poller (sF... (more)

Inter-Portlet Communications

This article demonstrates the steps performed to implement JSR 168 compliant cooperative portlets using IBM Rational Application Developer V6.0 and WebSphere Portal Server V5.1. The article illustrates passing multiple values from source portlet to target portlet without defining complex data type inside WSDL file. The term cooperative portlets refers to the capability of portlets on a page to interact with each other by sharing information. One or more cooperative portlets on a portal page can automatically react to changes from a source portlet triggered by an action or event ... (more)