| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Beta testers needed for MQ Channel Auto Creation Manager |
View previous topic :: View next topic |
| Author |
Message
|
| RogerLacroix |
 Posted: Wed Jun 09, 2010 1:42 pm Post subject: Beta testers needed for MQ Channel Auto Creation Manager |
 |
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
All,
Capitalware is ready for beta testers for a new program called: MQ Channel Auto Creation Manager.
MQ Channel Auto Creation Manager (MQCACM) is an MQ Channel Auto-Definition (MQ CHAD) exit that allows a company to control and restrict incoming connection requests to auto-create a channel. MQCACM is invoked when a request is received to start an undefined Receiver, Server-Connection, Cluster-Receiver or Cluster-Sender channel. MQCACM can modify or clear the supplied default channel definition values for an instance of the channel, so that there is no exit incompatibility (cross-platform or otherwise).
Features:
======
1) MQCACM has the ability to allow or restrict the incoming IP address from auto-creating a channel. MQCACM compares the incoming IP address against a regular expression pattern using a regular expression parser. If a match is found, the channel auto-creation is allowed; otherwise, the connection request is denied.
2) MQCACM has the ability to allow or restrict the incoming auto-create channel request based on the company's naming standard. MQCACM compares the incoming channel name against a regular expression pattern (Naming Standard) using a regular expression parser. If a match is found, the channel auto-creation is allowed; otherwise, the connection request is denied.
3) MQCACM has the ability to define, override or clear the supplied default channel definition values related to Message, Security, Receive and Send Exits. Hence, the appropriate platform specific values can be set for the given exit.
4) Cluster-Sender and Cluster-Receiver channels do not require the queue manager's CHAD parameter to be enabled for the channel auto-creation to happen. For 3rd party security exits to work with MQ clustering, an MQ CHAD exit is required to override the supplied default channel definition values. Hence, MQCACM can be used with 3rd party security exits to explicitly set or clear the supplied default channel definition values.
5) MQCACM can be used to prevent a 'Denial-Of-Service' (DOS) attack against a queue manager by setting all 4 'Allow” keywords (AllowClusRcvr, AllowClusSdr, AllowRcvr and AllowSvrConn) to 'N'.
I plan on building MQCACM for AIX, HP-UX (RISC & IA64), Solaris (SPARC & x86_64), Linux (x86, x86_64 & POWER), Windows and IBM i (OS/400). MQCACM will support WMQ v5.3, v6.0 and v7.0.
Note: There will also be a z/OS version called: MQ Channel Auto Creation Manager for z/OS.
Beta testing MQCACM is absolutely free including support (no strings attached).
You can view the MQCACM manual from the following link:
http://www.capitalware.biz/dl/docs/MQCACM_Installation_and_Operation.pdf
I will be creating a manual specifically for using MQCACM with MQ clustering and 3rd party security exits.
Please let me know if you are interested in testing MQCACM (i.e. support _AT_ capitalware _dot_ biz).
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| Back to top |
|
 |
| RogerLacroix |
| Posted: Thu Jun 10, 2010 11:16 am Post subject: Re: Beta testers needed for MQ Channel Auto Creation Manager |
|
|
Jedi Knight
Joined: 15 May 2001
Posts: 3264
Location: London, ON Canada
|
| RogerLacroix wrote: |
| I will be creating a manual specifically for using MQCACM with MQ clustering and 3rd party security exits. |
Ok. I have create a manual specifically for configuring MQCACM (CHAD exit) and any 3rd party server-side security exit. You can view the MQCACM Cluster Configuration manual from the following link:
http://www.capitalware.biz/dl/docs/MQCACM_Cluster_Configuration.pdf
If an MQAdmin exactly follows chapters 3 and 4 of the new manual, they can secure their MQ clustering with a 3rd party server-side security exit in minutes. Yes, using security exits with an MQ cluster is complex but if you follow my instructions then it is relatively painless. The manual covers Linux, Unix, IBM i (OS/400), Windows and z/OS implementation of MQCACM and 3rd party server-side security exits.
Note: In section 4.4 (Configuring a Cluster-Receiver Channel), I specifically used BlockIP2 as the sample 3rd party server-side security exit. The MQAdmin can easily replace the SCYEXIT and SCYDATA information with the information for a different 3rd party server-side security exit. If there are other popular 3rd party server-side security exits that people use then send me the information and I will add it to the manual for everyone to use.
Please let me know if you are interested in testing MQCACM (i.e. support _AT_ capitalware _dot_ biz).
Regards,
Roger Lacroix
Capitalware Inc.
_________________
Capitalware: Transforming tomorrow into today.
Connected to MQ!
Twitter |
|
| 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
|
|
|
|
