APAR status
Closed as program error.
Error description
When migrating from a WSRR instance that uses a profile that has a customized lifecycle prefix to a WSRR instance that uses a profile generated by WSRR the lifecycle classifications will not match and the migration will fail.
Local fix
Problem summary
When migrating from a WSRR instance that uses a customized lifecycle prefix it is not possible to use WSRR Studio to create an equivalent profile with the same customized lifecycle prefix. Prior to WSRR 6.3, when Studio was introduced, lifecycles had to be created by hand. Therefore existing content and profiles where a customized lifecycle prefix was used cannot be migrated to environments where the profile has been generated by Studio.
Problem conclusion
Studio was modified to allow lifecycle prefixes to be customized. This is intended to allow profiles to be generated to match existing profiles on older systems. Profiles for new systems should use the default lifecycle prefix.
Temporary fix
Comments
APAR Information
APAR number
IV08219
Reported component name
SERV REG STUDIO
Reported component ID
5724N7202
Reported release
750
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-09-26
Closed date
2011-11-16
Last modified date
2011-11-16
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
SERV REG STUDIO
Fixed component ID
5724N7202
Applicable component levels
R750 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSWLGF","label":"WebSphere Service Registry and Repository"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.5","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
16 November 2011