Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Central User Administration Retention of Change Logs

former_member49142
Explorer

‎03-11-2016 4:00 PM

0 Kudos

Hello,

Our BASIS team will be spinning up a new box for Solution Manager and will be decommisionning the old one which was used for CUA.  Please advise on what the recommended approach is to retain the user change logs from the old central system to the new one which will be used as the new CUA system.  We will need to retain the change logs for reference.  Trusted RFC's were not used in the old setup. We have two child system(s) and need to be able to retain the change logs for them.  IdM may be in the future but not for awhile.

Thanks,


Todd

3 REPLIES 3

Bernhard_SAP
Employee
Employee

‎03-14-2016 7:22 AM

0 Kudos

Hello Todd,

why setting up the new CUa on a solution manager system? Take the opportunity not to use a Solution Manager system to get rid of its limitations....

Set up the new CUA client by client copy (profile SAP_RECO - IMO thats the only profile which takes the change documents to the new client).

Then rename the new client (bdls). Update the RFC connections. Update the CUA landscape.

An alternate approach can be to archive the change documents in the old central system. Then reload the archived change docs into the new central system (SAP note 419933, point 3.3)

b.rgds, Bernhard

plaban_sahoo6
Contributor
In response to Bernhard_SAP

‎03-15-2016 10:04 AM

0 Kudos

Hi,

i think the database copy by Basis will ensure the change logs are available in new system.And could you share the limitations of Solman for CUA

Regards

Plaban

Bernhard_SAP
Employee
Employee
In response to Bernhard_SAP

‎03-16-2016 8:23 AM

0 Kudos

Hello Plaban,

asked already some times...

etc.

summary:

- Solman is bound on certain basis releases (702, actually 740) - no chance to upgrade seperately (the CUA central ssystem should reside on a system with the highest basis release of systems connected to the CUA)

- Solman is bound on SP stacks. No possibility just to upgrade the basis SP.

- Solman is no HA (high availability) system in general (just mind the time you spend for applying the SP stacks and post SP activities....)

- Licensing question for productive use of the Solman system (other tasks than Solman core tasks, i.e. CUA)

Bernhard