cancel
Showing results for 
Search instead for 
Did you mean: 

How to approve virtual server in STMS

former_member1326975
Participant
0 Kudos

I already created the virtual system for the current development server. Since this system already exist, I tried to go to SAP Systems -> Approve, this option is disable. How should I proceed?

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

If DEV already exists then why would you create 'virtual' system for it in STMS ?

What is the Domain Controller in your STMS landscape ? Is it DEV box or something else ?

Not sure, what you are trying to do, but as far as I understand - if you 'had' created a virtual system for an SAP system and now if that SAP system exists in real then first you have to delete the virtual system from the STMS and then you register new Real SAP system into STMS.

Thanks

former_member1326975
Participant
0 Kudos

This means that I cannot create a virtual system for testing if the system already exist.

Then, if my existing test server have the same transport route and configuration of the development system, will it be able to transport the request successfully into production without any error?

Former Member
0 Kudos

This means that I cannot create a virtual system for testing if the system already exist.

Not like that. You can still create the virtual system but in that case you should make that real already existing system invisible to the domain controller or STMS. TRANS DIR should not be shared for that already existing system. That particular SID should not be visible to the STMS landscape I think.

For your second query I would say first you need to decide which system is the domain controller, in which system we can do the 'developments'. Then the system where we can do the 'developments' needs to be connected to PRD (either via two system STMS setup or via three system STMS setup etc. ) and obviously transports will go into PRD successfully then. TRANS DIR should be shared in all those system which are in STMS along with proper transport routes.

Thanks

former_member1326975
Participant
0 Kudos

Actually I want the test server is an upgrade version of the current development server. This test server will be the development server in the future. So, if all the STMS configuration and transport route is the same, it should be no problem, rite?

Former Member
0 Kudos

Right.

You remove the old DEV from STMS and configure the STMS with new DEV. All should work fine.

But what about current 'developments/transports' being carried out in current DEV ? If you don't need them then find to remove the current/old dev from STMS.

If future DEV is upgraded rom the current DEV itself, then it is okay. In this case, you should plan carefully 'when to stop' the developments in old DEV and when to start all the developments in upgraded DEV.

Thanks

former_member1326975
Participant
0 Kudos

Actually it is in different server. I install the test server using the system copy of the current development server. If I still need those transport request, how to put them into the test server in a proper way? This is because I can get the transport request of the current development server and I add it into the test server. However, when I tried to transport, it will show me the lorry icon instead of the transport successfully icon. I tried to check whether it is transported successfully or not, no changes is made.

Former Member
0 Kudos

Actually it is in different server. I install the test server using the system copy of the current development server. If I still need those transport request, how to put them into the test server in a proper way? This is because I can get the transport request of the current development server and I add it into the test server. However, when I tried to transport, it will show me the lorry icon instead of the transport successfully icon. I tried to check whether it is transported successfully or not, no changes is made.

If new server is created using system copy then I think all the transport requests are already there now. Changes are already there so transports are also already released. I don't think you should move any transports from old dev to new copy of dev.

It means, the new server is not the 'upgraded' version but just the 'copy' of old server ? In that case, you can stop 'development' on old dev and start 'development' on new dev. But after removing old dev from stms and including new dev into stms.

Thanks

former_member1326975
Participant
0 Kudos

1. The upgrade i mean is on OS and database. It is upgraded from Windows 2005 to 2008 and MSSQL 2005 to 2008, so need to install in new server.

2. This means that I need to make sure that all the released transport request must be transported to production before I migrate the system copy to the new server?

3. Is there any problem if the SID is different from the old server? Any impact?

4. If no impact, all the STMS configuration follow the current development server, should be no problem, rite?

Former Member
0 Kudos

1. The upgrade i mean is on OS and database. It is upgraded from Windows 2005 to 2008 and MSSQL 2005 to 2008, so need to install in new server.

That's OK, I got it now.

2. This means that I need to make sure that all the released transport request must be transported to production before I migrate the system copy to the new server?

No, nothing like that. You just start using new server/new DEV by configuring STMS for it and start moving the transports from new DEV --> current QAS --> current PRD.

3. Is there any problem if the SID is different from the old server? Any impact?

I don't think so. See below.

4. If no impact, all the STMS configuration follow the current development server, should be no problem, rite?

Right I think. You try one thing - this is for already existing transports --- Since new DEV is ready and if you have changed the SID then you first test a single transport test - to move a single transport from this new DEV (the transport number which contains old SID) to current QAS. Verify the results.

And as far as new generated transports are concerned (after you start development in new DEV) those will be created with new SID naming in any case.

Thanks

former_member1326975
Participant
0 Kudos

Actually I don't have a QAS system. The current configuration is DEV --> PRD. So, how can I test whether the transport is working? If I need to move the transport request, does it mean that copy the files in cofiles and data folder of the old DEV to the new one? Then, I will add the request one by one in the STMS rite?

Former Member
0 Kudos

If I need to move the transport request, does it mean that copy the files in cofiles and data folder of the old DEV to the new one? Then, I will add the request one by one in the STMS rite?

You need to test the transports from DEV --> PRD.

After system copy you must be having the already existing transports from old DEV into new DEV. But yes, the datafiles/cofiles need to be copied to DEV's trans folder (new DEV's trans folders should be shared with PRD as well) i.e. to new STMS as you don't want to use old DEV now

You just remove old DEV from STMS (it includes detaching it's TRANS from the other systems) and add new DEV as was your old DEV.

Thanks

former_member1326975
Participant
0 Kudos

If I don't remove the old DEV because I need to monitor and make sure everything is working before the old server is shut down, will the testing result still the same? I mean if I set the STMS configuration same as the current development server in PRD.

Former Member
0 Kudos

If I don't remove the old DEV because I need to monitor and make sure everything is working before the old server is shut down, will the testing result still the same? I mean if I set the STMS configuration same as the current development server in PRD.

No need to shutdown the old DEV yet. You just go ahead to do everything with NEW DEV and current PRD.

Thanks