Service Pack Install Questions 2

[clk430]

We're going to install the service pack to go from 6.7 to 6.7.1. Finally.

Questions:

1:Is there a SOP or rough guidline for installing the service pack?

2:We've had one patch ( a few dll's changed) so far, so would the service pack overwrite these?

3oes Unit testing have to be completed when doing the SP?

 

[BocaBurger]

Just install it, after backing up any patches.
Yes, you may meed a new patch or it might be included in 6.7.1
Depends on your company's requirements. I would.





BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!

 

[clk430]

We are migrating our current 6.7 to new servers right now. As we are doing this, we are unit testing each map and system before we turn on the new servers. Would you recommend killing two birds with one stone and installing the service pack as well during the intial load of the new server? Or do it seperatly, later on?

 

[clk430]

...basically, installing 6.7, CMGR 7.0, then the service pack, then moving over the maps...

 

[JEMIAZ]

clk430
We are a few weeks ahead of you on this 6.7 to 6.7.1 upgrade. We installed 6.7 and the service pack (with backup option) plus doubled checked any bespoke patches. Where the new dll was a higher release it is installed otherwise patch dll's are kept. Where the new dll was installed we specifically tested for the error that caused the initial dll a problem.

We did do a test mass recompile of maps to ensure that all features did not cause a problem and identified problems with some IF..ELSE statements that made us change some maps. This is detailed in the Readme.txt.

We deployed all the original maps apart from those that had had to be changed and performed some end to end tests on key components and systems.

No problems so far.

Tim

 

[clk430]

ManchesterTim,

That's cool! I'll probably check in with you from time to time to share if we came up with any problems or if you came up with any more. Also, I'd be interested to see what value the service pack bought you.

btw, Manchester isn't refering to NH, is it? I grew up there, that's why I ask.

 

[BocaBurger]

Anyone using any version prior to 7.5.1 should think about upgrading to 8.0.1 when it is released this year.

Get 8.0 now so you can use the new features to tune your maps, (use copies, and put the results in your older maps).

The OSs that older versions run on are being sunsetted by the publishers, and the older versions of DS TX are not supported on the latest versions. This is also true of many database versions and other 3rd party products.





BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!

 

[clk430]

Boca, how many companies would you estimate actually use 8.0 in their production environment?

 

[JEMIAZ]

Clk430 - its Manchester in the UK not US.

We primarily upgraded to 6.7.1 because we wanted some features of the MQ adapter that weren't in 6.7 (segmented rollback of messages in particular).

Why not go to 8.0?
1. Previous experience has shown management here that it does not pay to be on the latest release of TX products. Too many memory leaks and quirks have shown up prior to the service packs. I don't necessarily agree.
2. Upgrading is not an easy process in a validated environment where the FDA is breathing down your neck. To upgrade to 8.0 is a 1 year project(!) (documentation, documentation, more documentation following by testing, testing, testing) even though the install guide looks a breeze and our collection of .msl's is not that extensive.
3. The new features don't apply to us at present so there is no ROI

Having said that I do use 8.0 to debug maps. Fantastic enhancement.
We are juggling to stay within support of all our main products - TX, MQ and Oracle. We plan to do a bigger upgrade next year but have to get the funding to move to 8.x, MQ 6.x (if supported then) and Oracle 10...

Some really nice business features that come bundled and not cost extra should do the trick (SOA edition springs to mind)!
Tim

 

[BocaBurger]

By next year there should be another version of DS TX, and the 8.0.1 release should be out too.

_Great_ idea to use 8.0 to debug and performance tune maps, no matter what version you run on. Just make a copy of the maps and trees, tune it up and put the results into your 6.x or 7.x systems.
If you are on Windows, 8.0 has the multi-process Event Server. This will be a big help for Windows users. UNIX users could alway do multiple installs (if they have enough resources).



BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!

 

[janhes]

So should we wait for the release after 8.0.1? Or do you mean 2007 for the next release.

 

[BocaBurger]

Depends on what your time frame is. 8.0.1 should meet most business requirements, has great new features, and would be supported for a fairly long time.



BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!

 

[eyetry]

Perhaps I missed it but are you upgrading in a Windows 2000/XP environment?

 

[clk430]

eyetry, who ya talkin' to?

If me, yes, a windows 2000 OS.

 

[eyetry]

Why, you, of course

I didn't have any problems converting mapts/trees/etc.. from 6.1 to 6.5.2 but did have some problems going from 6.5.2 to 6.7.1. Those issues revolved around chnages to the Health Care Pakage type trees. And, the problems only occurred in one mapset of 30 or so.

Ascential - DataStage TX 6.7.1 Installation Instructions

Below is the install order for DataStage TX 6.7.1 (aka Mercator 6.7.1). Software is located at ...... Based Version is subfolder ‘67’, Service packs in ‘671’.

This application requires Client 8.7.1 for Oracle but the server is running the 9i Client. Client should be installed first if not already installed. All other applications for version 6.5 can/should be left on machine at this time.

During the installation, when asked, make 6.7.1 the default version. Making it the ‘default’ application will not affect 6.5.2 users developing and deploying 6.5.2 maps from other machines.

Installation order:

1.Design Studio 6.7
2.Integration Broker 6.7
3.Management Tools 6.7 (optional install as its components are already included in Design Studio and Integration Broker)
4.Healthcare Integration Pack V3.1version for 6.7
5.Commerce Manager
6.Service Patch 17340 for Commerce Management V7.0 Windows NT_2000_XP for Integration Broker
7.Service Pack 1 for Integration Broker Products v6.7.1

Once installation is complete open, ‘Event Server Administration’, ‘Start\Programs\Mercator 6.7\Integration Broker\Event Server Administration’, and change the following settings:

8.‘General’
9.Deselect ‘Automatic Startup’
10.Listening Ports 2002-2003
11.Port Range 8000-9000
12.Resource Configuration File ‘path\resource.mrc’
13.‘Access’
14.Setup user
15.Grant Access Rights
16.Create additional user
17.‘Deployment Directories’
18.Set to ‘path\systems’
19.‘Advanced’ (do not perform this step)
20.Properties ‘java.rmi.server.hostname’
21.Value ‘localhost’
22.‘Options’ (no change)


Configure ‘Event Server Monitor’, ‘Start\Programs\Mercator 6.7\Design Studio\Event Server Monitor’, and change the following settings:

23.From the ‘Menu’ choose ‘Options\select EventServer…’
24.In the popup choose ‘Add’
25.Name ‘localhost’
26.login and password
27.Server ‘localhost’
28.Port ‘2003’
29.Click ‘OK’
30.From the ‘Menu’ choose ‘Options\select EventServer…’ and confirm that there is an Event Server named ‘localhost’


Configure ‘Management Console’, ‘Start\Programs\Mercator 6.7\Design Studio\ Management Console’, and change the following settings:

31.From the 'Menu' choose 'Event Server\New'
32.Name 'localhost'
33.Connection Host name 'localhost'
34.Port '2002'
35.Login and Password
36.Click 'OK'
37.If performed correctly there should be a tab labeled 'localhost' in the lower left corner of the Management Console window.

Change the ‘Mercator6.7 Event Server’ properties. Open Windows ‘Services’, ‘Start\Settings\Administrative Tools\Services’

38.Right click on ‘Mercator6.7 Event Server’ and select ‘Properties’
39.General\Startup Type = ‘Manual’
40.‘Logon\This account’; User = ‘?’, Password = …..
41.Click ‘OK’

Unzip ‘Mercator_671.zip’ to ‘d:\’. Zip file contains a folder named ‘Mercator6.7’. That folder contains all of the files and setting to make the installation a success. When asked if you want to replace existing files choose ‘Yes’.


Configure ‘Commerce Manager’ by opening ‘Start\Programs\Mercator 6.7\Commerce Manager\Partner Manager’

From ‘Menu’ choose ‘Utilites’
Select ‘Database Settings’
42.DB Vender = Oracle
43.DSN = sid
44.User ID = ?
45.PW = ?
Click ‘Test Connection’
Click ‘OK’ (this will close Partner Manager)
Re-open Partner Manager
From ‘Menu’ choose ‘Utilites’
For the following selections change the drive letter to ‘D’ from ‘C’ and click ‘Test Configuration’ then ‘Save’.
46.Archive Configuration (both paths, should display ‘D’ already)
Choose ‘Message Manager Configuration’. Make sure Maximum Reject File Size is set to ‘0’.

(the zip file contained some original maps with custom Ascental Patches that carried over to 6.7.1 plus we renamed some of the oracle dlls as recommended in the readme docs because the defaults were for 8.7.1 not 9i. Most people didn't seem to have an issue running the dlls as installed but I wanted to make the change up front so I didn't forget about it later should we encounter DB issues later and not remember the change at that time.)

 

[eyetry]

Oh, BTW had problems on the first install on my test machine.... on reinstall we installed CMGR 7.0 SP 17340 before installing 6.7.1. After that things worked pretty good.

 

[clk430]

Awesome! Thanks eyetry, we'll follow your instructions to the T.

When you say you had trouble on your first intall, by installing CMGR first instead of 5th worked?

 

[eyetry]

The first time I installed CMGR it was after the 6.7.1 service pack but before the CMGR SP.

BYW keep your 6.5.2 ini settings as they should be transferable to 6.7.1. 7.5 and beyond that isn't always the case.

 

[BocaBurger]

BIG change in 6.7.x from any previous version: Event Server will pre-allocate memory based on page size and count settings. So, if you have huge settings like 1024 X 999, you will run out of RAM before you start.

Get the 8.0 Design Studio and test copies of your maps with the dstxpage.exe.



BocaBurger
<===========================||////////////////|0
The pen is mightier than the sword, but the sword hurts more!

 

[clk430]

eyetry - we're actually going from 6.7 to 6.7.1, just on a new, bigger server. I'll keep the .ini settings, but will adjust for the extra hardware.

BocaBurger - does this apply if it's just 6.7 to 6.7.1?