NWTHS Axiant conversion update

[Neil Harvey]

Peter

Well done on your successful migration.

I would love to know what prompted the huge investment in time and effort
that you went through.

Can you tell us whether your 20/30 users benefited substantially from the
migrate from Client to Axiant, by way of improved functionality, richer
working environment, and give some indication of enhanced productivity etc.?

Many of us have come under pressure to "migrate" from traditional PowerHouse
interfaces, sometimes to  non-Cognos (shudder) environments, and it's always
good to hear success stories from within the family, so to speak, to bolster
arguments in favour (or otherwise) of undertaking such a "paradigm (ugh)"
shift.

Regards

Neil


-----Original Message-----
From: Peter DOXEY [mailto:peter.doxey@coats-viyella.com]
Sent: 14 July 1999 07:51
To: whl3@nwths.com; powerh-l@lists.swau.edu
Subject: Re:NWTHS Axiant conversion update 


Hello All,

    Sounds a bit of a sorry story, but I can at least give you some hope, we
have now migrated an application from Powerhouse Client into Axiant 2.03
(400 -
450 programs in all, 400 Screens, the rest Qtp/Quiz).  This application went
Live 12th July 1999 and is stable with no real problems as yet (touch wood).


The migration from Powerhouse Client to Axiant caused a few major headaches
and
the project has taken about 200 man days to complete. The system runs on an
Alpha machine with OpenVMS using the relational database Interbase 3.3j3.
Some
of the problems we had while migrating were;

1. Differences between Powerhouse 710F2 and 810C (required for Axiant),
because
Cognos want to create a common powerhouse code base they have removed some
of
the functionality from the OpenVms version.

2. The introduction of a layered product within Powerhouse OpenVMS - called
DMS.

I believe that this has always been in the unix version (not sure), we had
some
real issues with the way this handled database transactions. This sometimes
caused Axiant runtime version to crash the PC !

3. There were differences between powerhouse coding standards in Powerhouse
Client and Axiant which we had to re-code. 

Although some of these caused us some major problems, all credit to Cognos,
they
flew me out to Ottawa with the application and we spent 2 weeks sorting out
some
of the issues.

At the end of the day the application is LIVE and very stable, there are
around
20/30 users using the system on a daily basis and our client is very happy.
We
have found that the Axiant environment allows for quick development,
especially
if you have set your inheritance up correctly, this is a very powerful tool
which allows you to globally include and change system wide standards.

We are now looking at migrating some modules within the application onto NT
with
SqlServer, so if anyone has already had experience using this environment,
are
there any pitfalls to look out for ?

All we can say is don't give up, you will get there !!

    Regards 
        Peter.A.Doxey :>    
        Project Manager
        Syscom PLC (Software Specialists), West Midlands, England.

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.