| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Http Proxy servlet in IIB9 |
« View previous topic :: View next topic » |
| Author |
Message
|
| Ashok Kumar |
 Posted: Mon Mar 03, 2014 4:38 am Post subject: Http Proxy servlet in IIB9 |
 |
|
Acolyte
Joined: 01 Jul 2013
Posts: 53
|
Hello WMB Developers,
I am working on Http Proxy servlet in IIB9.I have configured proxyservlet .war .I am processing the message flow but i got reply as Error 500: java.lang.NullPointerException.
I have configured proxyservlet.war like this
| Code: |
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN" "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
<web-app id="WebApp">
<!-- Proxy servlet for WBIMB HTTP input nodes -->
<display-name>WBIMB Proxy Servlet - Message Broker 8.0.0.1 </display-name>
<servlet>
<servlet-name>WBIMBServlet</servlet-name>
<display-name>WBIMBServletV8001</display-name>
<servlet-class>
com.ibm.broker.httpproxy.WBIMBServlet
</servlet-class>
<init-param>
<param-name>brokerName</param-name>
<!-- Set the message broker name here -->
<param-value>*</param-value>
<description>
Set the message broker name here.
May be * if multiple brokers will be connected
</description>
</init-param>
<init-param>
<param-name>configFilePath</param-name>
<param-value>
C:\\Program Data\\IBM\\MQSI\\components\\IIB9\\config\\wsplugin6.conf
</param-value>
<description>
This would be
/var/mqsi/components/[broker_name]/config/wsplugin6.conf
on UNIX or C:\\Program Data\\IBM\\MQSI\\components\\[broker_name]\\config\\wsplugin6.conf
on Windows
</description>
</init-param>
<init-param>
<param-name>traceFileName</param-name>
<!-- C:\\temp\\httpproxy-trace.txt -->
<!-- /tmp/httpproxy-trace.txt -->
<param-value></param-value>
<description>
Trace file location
</description>
</init-param>
<init-param>
<param-name>turnTraceOn</param-name>
<!-- Set 0 for no trace, 1 for normal or 2 for debug -->
<param-value>0</param-value>
<description>
Set 0 for no trace, 1 for normal or 2 for debug
</description>
</init-param>
<init-param>
<param-name>useClientMode</param-name>
<param-value>true</param-value>
<description>
Use MQ client (true) or bindings connection (false).
Normally, useQueueManagerDataInsteadOfConfigFile would
also be set to the broker queue manager if this parameter
is set to true.
</description>
</init-param>
<init-param>
<param-name>clientModeHostname</param-name>
<param-value>localhost</param-value>
<description>
Hostname or IP for the Queue Manager
</description>
</init-param>
<init-param>
<param-name>clientModeChannelName</param-name>
<param-value>SYSTEM.DEF.SVRCONN</param-value>
<description>MQ SVRCONN channel name</description>
</init-param>
<init-param>
<param-name>clientModePortNumber</param-name>
<param-value>1250</param-value>
<description>MQ Listener port number</description>
</init-param>
<init-param>
<param-name>clientModeConnectRetryCount</param-name>
<param-value>1</param-value>
<description>
Number of times to retry the MQ connect call. This is useful in
cases where a network dispatcher or load balancer is fronting a
set of queue managers and one fails; a new connect may fail the
first time but succeed the second, and the retry count should be
set to a high-enough number to provide the greatest chance of success.
</description>
</init-param>
<init-param>
<param-name>
useQueueManagerDataInsteadOfConfigFile
</param-name>
<!--Queue manager name or blank for none -->
<param-value>IIB9QMGR</param-value>
<description>
Queue manager name (remote proxy) or blank for none
(local proxy). Supported on WMB6 Fix Pack 1 or later.
</description>
</init-param>
<init-param>
<param-name>sleepBeforeGet</param-name>
<param-value>0</param-value>
<description>Sleep time in seconds</description>
</init-param>
<init-param>
<param-name>disconnectBeforeSleep</param-name>
<param-value>false</param-value>
<description>
To release MQ handle while sleeping
</description>
</init-param>
<init-param>
<param-name>useFastpathBindingsConnection</param-name>
<param-value>true</param-value>
<description>
Used when useClientMode is false. Be careful with this
option it can compromise the integrity of the queue
manager
</description>
</init-param>
<init-param>
<param-name>reconnectActiveLinksAge</param-name>
<param-value>-1</param-value>
<description>
If set to a number greater than zero, this causes MQ connections
to be disconnected and reconnected if they have been inactive (owing
to low traffic volumes) for more than the specified number of
seconds.
Setting this to -1 prevents this reconnection; setting it to 0
causes all connections to be used once only.
This parameter is of most use if the connection to MQ goes through
a firewall that closes connections after a period of inactivity.
Setting this parameter to a value less than the firewall timeout
may prevent clients from getting MQ 2009 (connection broken) errors.
</description>
</init-param>
<init-param>
<param-name>maximumConnectionAge</param-name>
<param-value>-1</param-value>
<description>
If set to a number greater than zero, this causes MQ
connections to be disconnected and reconnected once they
have reached the specified age in seconds. This parameter
in contrast to 'reconnectActiveLinksAge' will reconnect even
if the connection has not been idle (although the current
operation will always be completed first).
Setting this to -1 prevents this reconnection; setting it to 0
causes all connections to be used once only.
This parameter is most useful for setting a maximum interval at
which configuration information stored on a queue manager takes
effect when using the 'useQueueManagerDataInsteadOfConfigFile'
parameter.
</description>
</init-param>
<init-param>
<param-name>testConnectionBeforeReuse</param-name>
<param-value>true</param-value>
<description>
If set to true, the servlet will attempt an MQINQ before doing the
MQPUT of the HTTP data message; any problems with a cached MQ
client connection will be detected at that point, and a new connection
will be established for the MQPUT of the actual data (and MQGET of the
response).
This parameter causes significant extra network traffic, and should
be used only if problems have been seen with dropped connections
(usually seen as MQ 2009 errors, indicating connection broken).
</description>
</init-param>
<!-- ssl options -->
<init-param>
<param-name>useSecuredChannel</param-name>
<param-value>false</param-value>
<description>
Only set the value of "useSecuredChannel" to "true" if SSL is configured
on MQ Channel
If set to true, the servlet will try to establish a secured connection
to the MQ Channel by using the keyStore, keyStorePassword, trustStore,
trustStorePassword and cipherSuite parameter values.
</description>
</init-param>
<init-param>
<param-name>keyStore</param-name>
<param-value></param-value>
<description>
Fully Qualified path to the KeyStore file.
The keyStore file should be of type "JKS"
for example,
/var/mqsi/keystore.jks on UNIX or
C:\\Program Files\\IBM\\MQSI\\keystore.jks
on Windows
</description>
</init-param>
<init-param>
<param-name>keyStorePassword</param-name>
<param-value></param-value>
<description>
KeyStore Password.
</description>
</init-param>
<init-param>
<param-name>trustStore</param-name>
<param-value></param-value>
<description>
Mandatory Field if useSecuredChannel set to "true"
Fully Qualified path to the KeyStore file.
The trustStore file should be of type "JKS".
ie,
/var/mqsi/truststore.jks on UNIX or
C:\\Program Files\\IBM\\MQSI\\truststore.jks
on Windows
</description>
</init-param>
<init-param>
<param-name>trustStorePassword</param-name>
<param-value></param-value>
<description>
TrustStore Password.
</description>
</init-param>
<init-param>
<param-name>cipherSuite</param-name>
<param-value></param-value>
<description>
Encryption details as configured in the MQ Channel
Ex: SSL_RSA_WITH_NULL_MD5
Mandatory Field if useSecuredChannel set to "true".
</description>
</init-param>
<!-- end ssl options -->
<!-- clustering options -->
<init-param>
<param-name>useClusterMode</param-name>
<param-value>true</param-value>
<description>
Set to true if the servlet should put reply-to queue and
queue manager information in the MQMD of sent messages to
enable the broker to respond to the correct queue manager
in a cluster.
clusterModeQueueManagerName and clusterModeReplyToQ should
be set to appropriate values; they default to the broker
queue manager and SYSTEM.BROKER.WS.REPLY if unset.
</description>
</init-param>
<init-param>
<param-name>clusterModeQueueManagerName</param-name>
<param-value>IIB9QMGR</param-value>
<description>Queue manager name for initial MQCONN and ReplyToQMgr</description>
</init-param>
<init-param>
<param-name>clusterModeReplyToQ</param-name>
<param-value>SYSTEM.BROKER.WS.REPLY</param-value>
<description>Queue name on which to listen</description>
</init-param>
<!-- end clustering options -->
<!-- info options -->
<init-param>
<param-name>enableStatusPage</param-name>
<param-value>false</param-value>
<description>
Switches display of the status page. When true, the page is visible at
(context root)/messagebroker/httpproxy/statuspage
</description>
</init-param>
<init-param>
<param-name>enableInfoHeaders</param-name>
<param-value>false</param-value>
<description>
Causes the servlet to add extra headers in the response, describing
the broker name used, queue manager name, etc.
</description>
</init-param>
<!-- end info options -->
</servlet>
<servlet-mapping>
<servlet-name>WBIMBServlet</servlet-name>
<url-pattern>/*</url-pattern>
</servlet-mapping>
<welcome-file-list>
<welcome-file>index.html</welcome-file>
</welcome-file-list>
</web-app> |
please any body help me.
Thans in advance. |
|
| Back to top |
|
 |
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
