Configure the HTTP proxy servlet with the details of the
integration node environment to which the HTTP proxy servlet connects.
The HTTP proxy servlet must be configured before you deploy the
HTTP proxy servlet to a servlet container.
About this task
The HTTP proxy servlet proxyservlet.war file
is part of the runtime environment, and can be found in the following
directory:
install_dir/server/tools
where install_dir specifies the name
of your runtime installation directory.
Complete the following
steps to configure the web deployment descriptor (web.xml)
for the HTTP proxy servlet by using the IBM® Integration Toolkit.
Procedure
- To import and configure a .war file,
you must have the Eclipse Java™ EE
developer Tools feature installed in the IBM Integration Toolkit. This feature is not included
in the IBM Integration Toolkit by default but
can be installed by completing the following instructions:
- From the IBM Integration Toolkit menu,
click .
- Enter the following URL in the "Work with" field:
http://download.eclipse.org/releases/juno
- Click and enter a name for the site.
For example, Eclipse
Juno downloads.
- Click OK and wait until the available
features are listed.
- Expand the Web, XML, Java EE and OSGi Enterprise
Development category, select the Eclipse
Java EE Developer Tools feature and click Next.
The Install Details dialog is displayed.
- Click Next, accept the license,
and then click Finish.
The
feature is installed.
- Click Yes when you are prompted
to restart the IBM Integration Toolkit.
The Eclipse Java EE Developer Tools feature
is now available in the IBM Integration Toolkit.
- From the IBM Integration Toolkit menu,
switch to the Java EE perspective
by clicking and
clicking Java EE.
- Click , expand the Web section, select WAR
file in the list, and click Next.
- Click Browse to find the proxyservlet.war file
in install_dir\server\tools,
where install_dir specifies
the name of your IBM Integration Bus installation
directory (for example, C:\Program Files\IBM\IIB\10.1.0.2\server\tools\proxyservlet.war),
and click Open.
- Set the name of the Web project to proxyservlet and
click Finish.
The HTTP proxy
servlet is now ready for configuring by using the Java EE perspective.
- In the Project Explorer view, expand
proxyservlet and double-click Deployment
Descriptor to view the web deployment descriptor.
- Find the Servlets and JSPs section
in the Web Deployment Descriptor, and click the servlet link
called WBIMBServlet to display the servlet
web address mappings and initialization parameters.
The same parameters in the
web.xml file
can be configured through JNDI in
WebSphere® Application
Server. This alternative method
means that you set up at the application server side only once
for any future deployment of the proxy servlet. This operation is
possible because the JNDI configuration parameters take precedence
over the initialization parameters in the
web.xml file.
For more information about setting up the JNDI interface for
the proxy servlet, see
Setting up the JNDI interface for the proxy servlet
- Click the Source tab, which is found
at the bottom of the Deployment Descriptor view.
The source of the web deployment descriptor (web.xml)
displays the HTTP proxy servlet parameters.
- Edit the HTTP proxy servlet parameters as required; see HTTP proxy servlet configuration parameters.
- When the configuration is complete, save the changes to
the web.xml file by pressing Ctrl+S.
- Export the configured HTTP proxy servlet ready for deployment
to a servlet container by completing the following steps:
- In the Project Explorer view, right-click
the Deployment Descriptor for the proxyservlet
Web project, and click .
The WAR
Export dialog window is displayed.
- Click Browse and specify a location
and a name for the configured WAR file.
For example, myproxyserlet.war.
- Click Save and then click Finish.
Results
You have now configured the HTTP proxy servlet with the
initialization parameters.
What to do next
Deploy and configure the HTTP proxy servlet
on the web application server that will host the JavaScript application, see Deploying the HTTP proxy servlet on a servlet container.