Migrating uPerform to Enable Now

[former_member731490]

Has anyone found a document for migrating uPerform to Enable Now simulations? I have found several questions on this board for this topic seeking best practices, constraints/dependencies, or procedures but no answers. I have heard anecdotally that there are a couple of things to watch out for, but nothing really documented. I know it involves writing and executing a script and I'm not asking how to write a script, just what the best practices and constraints/dependencies to be aware of.

Thanks in avance.

[DirkManuel]

There's no easy import/convert feature in SAP Enable Now. Yes, you could write a script to do it, but unless you're an actual programmer with decent programming skills I wouldn't even attempt it yourself. There are a few companies that have built a conversion utility (I've used Abreon / Insight in the past; I think Eagle Consulting does the same thing; there may be others) - it'll cost you, but at least you'll get your content converted, and it's cheaper than re-recording everything. The conversions probably won't be as good as new recordings (typically you won't get the full object-level context you would from a 'native' SEN recording), but again, at least you'll have something. The conversion company can tell you about the things to watch out for / what you need to do to prep the content for conversion (typically branches/decisions, embedded content, hyperlinks...).

But all that said, welcome in to the light!

[Anton_Mavrin]

Absolutely agree with Dirk. Also, instead of conversion you can do mappings to the existing uPerform recordings from SAP Enable Now content tree, so uPerform content could be opened from i.e. SAP Enable Now library view. Could save you some budget on conversion (especially, when uPerform recordings are somewhat outdated).

[former_member731490]

Thank you, Dirk and Anton, for your responses and insight. I do have a resource that can do the programming but trying to put together a "best practices" type of guide that can be used on other projects. So not so much "how to create a script" but "things to watch out for/do in this order" when creating the scripts.

I do like the idea of mapping. This customer is planning an upgrade in the next few months that may be a quicker win for a short term need.

[DirkManuel]

Ultimately, what the conversion does is takes the XML (or other - been a while since I dug into its bowels) file from uPerform, runs through this, identifying the screens/actions etc., and rewrites these out as a .dpr (still technically XML) file for SEN. So best practices are really down to what can be mapped or transformed (XSLT) (screenshots, actions, for sure) versus what cannot (i.e. features in Uperform that don't exist in SEN, or vice versa) - like if uPerform supports multiple simultaneous actions on a single screen. I don't think you'll get one of the existing service providers to give up their list so you can write your own replacement, so yo may find it easier to just draw up a list of the capabilities SEN provides and a list of the capabilities uPerform provides, and then write the code to convert the common ones. But I'll tell you for free that conversion from UPK takes the published player package not the .odarc...