Moving DS Server Jobs to PX
Posted: Tue Mar 02, 2004 7:40 am
Hi All,
this is really just 'thinking aloud' and asking am I thinking correctly.
1. We have completed development of an ODS using Server jobs. (60 or so that are important to this conversation. 140 will never be PX.) We have just got our 12K dev machine available and started production volume testing this week.
2. We have also sold the customer PX. (We are a reseller of ASCL products.)
3. We are new to PX (like most I guess). This is our first PX site.
4. We did not develop in PX because we were assured we could develop in Server and deploy in PX. (Technically true by wrapping a server job in a container and running it in PX)
5. We have (of course) now found out a re-write is required to get full advantage of PX.
6. It seems the best advice is 'complete our current development on Server' and just start re-writing the jobs that take a long time on PX.
My questions would be:
1. We are looking for the 'best' way of moving our most time consuming jobs to PX. For example, it would be extremely handy to retain the transformer icons etc. But it looks like there is no way to 'move' a job to retain some of the coding. We have looked at exporting the XML and manipulating it so we can import it into PX but that does not look possible. Any advice other than start with a blank canvas?
2. As pointed out here, PX is completely different in the back end. So we will need a 'learning curve' on PX. Given we are unlikely to get to a class what's the fastest way up the learning curve? Any hints? (Do we just RTM and learn as we go? Surely we will have plenty of 'gotchas'.)
3. Is there any source of example PX jobs anyone knows about? If it is inside ASCL we may also be able to get it as a reseller. Some good sample jobs may help us up the learning curve.
I guess I am still a little 'surprised' that there is no way to go from server to PX......perhaps I am 'grasping at straws' a little.
Any better advice than our current thoughts on how to best move to PX would be very much appreciated.
Thanks
this is really just 'thinking aloud' and asking am I thinking correctly.
1. We have completed development of an ODS using Server jobs. (60 or so that are important to this conversation. 140 will never be PX.) We have just got our 12K dev machine available and started production volume testing this week.
2. We have also sold the customer PX. (We are a reseller of ASCL products.)
3. We are new to PX (like most I guess). This is our first PX site.
4. We did not develop in PX because we were assured we could develop in Server and deploy in PX. (Technically true by wrapping a server job in a container and running it in PX)
5. We have (of course) now found out a re-write is required to get full advantage of PX.
6. It seems the best advice is 'complete our current development on Server' and just start re-writing the jobs that take a long time on PX.
My questions would be:
1. We are looking for the 'best' way of moving our most time consuming jobs to PX. For example, it would be extremely handy to retain the transformer icons etc. But it looks like there is no way to 'move' a job to retain some of the coding. We have looked at exporting the XML and manipulating it so we can import it into PX but that does not look possible. Any advice other than start with a blank canvas?
2. As pointed out here, PX is completely different in the back end. So we will need a 'learning curve' on PX. Given we are unlikely to get to a class what's the fastest way up the learning curve? Any hints? (Do we just RTM and learn as we go? Surely we will have plenty of 'gotchas'.)
3. Is there any source of example PX jobs anyone knows about? If it is inside ASCL we may also be able to get it as a reseller. Some good sample jobs may help us up the learning curve.
I guess I am still a little 'surprised' that there is no way to go from server to PX......perhaps I am 'grasping at straws' a little.
Any better advice than our current thoughts on how to best move to PX would be very much appreciated.
Thanks