ClearPath OS 2200 Series Release 13.2 Software Planning and ...
ClearPath OS 2200 Series Release 13.2 Software Planning and ...
ClearPath OS 2200 Series Release 13.2 Software Planning and ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
5.55. Web Transaction Server (WEBTS)<br />
General Considerations<br />
Web Transaction Server (WEBTS)<br />
• The first time Web Transaction Server is started, it automatically updates<br />
configuration files to the new format if their format differs. It is strongly<br />
recommended that you make a backup copy of the configuration file <strong>and</strong> any other<br />
WebTS associated files prior to installation.<br />
Note: Refer to the Web Transaction Server for <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration<br />
Guide for complete information <strong>and</strong> procedures for migrating from previous levels of<br />
Web Transaction Server to the current level of Web Transaction Server.<br />
• The Web Transaction Server is included in the Integrated Operating Environment<br />
(IOE).<br />
• Refer to the Web Transaction Server for <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Administration Guide for<br />
information on Web Transaction Server dependencies on <strong>OS</strong> <strong>2200</strong> software levels.<br />
5.56. WebSphere® MQ Version 7 for <strong>ClearPath</strong><br />
<strong>OS</strong> <strong>2200</strong> (WMQ<strong>2200</strong>)<br />
General Considerations<br />
Migrating from MQS<strong>2200</strong> to WMQ<strong>2200</strong><br />
Migration is no longer done with the *mqs$run.init/run addstream. Several migration<br />
scenarios exist for upgrading from MQS<strong>2200</strong> to WMQ<strong>2200</strong>. Existing MQS<strong>2200</strong> users<br />
have the following options:<br />
• Replacement – Remove all existing queue manager data by uninstalling the existing<br />
MQS<strong>2200</strong> product <strong>and</strong> then installing WMQ<strong>2200</strong>.<br />
• Co-install – Retain your existing MQS<strong>2200</strong> installation alongside your new<br />
WMQ<strong>2200</strong> installation by generating <strong>and</strong> installing an alternate BDI version of<br />
WMQ<strong>2200</strong>.<br />
• Migration – Retain your existing queue manager data by following the migration<br />
procedure.<br />
Refer to the WebSphere® MQ Version 7 for <strong>ClearPath</strong> <strong>OS</strong> <strong>2200</strong> Installation,<br />
Administration, <strong>and</strong> Programming Guide for more information on these options.<br />
Upgrading from a Previous Level of WMQ<strong>2200</strong><br />
Installing a new level of WMQ<strong>2200</strong> first removes the MQS subsystem as well as the<br />
previously installed WebSphere MQ RPM on the <strong>OS</strong> <strong>2200</strong> QProcessor. Installing a new<br />
level of WMQ<strong>2200</strong> does not affect your queue manager objects or queue data. In other<br />
words, the content of /var/mqm is not removed.<br />
You can choose one of the two procedures depending upon whether you are upgrading<br />
a High Availability environment. Refer to the WebSphere® MQ Version 7 for <strong>ClearPath</strong><br />
<strong>OS</strong> <strong>2200</strong> Installation, Administration, <strong>and</strong> Programming Guide for more information.<br />
7831 0349–043 5–61
Change language