Development moving to QA and Production domain

[Former Member]

Hi,

We are working on NW2004s support.We have implemented CRM5.0(ABAPJAVA),BIEP7.0 ,PI on MSSQL2005,WIndows 2003 enterprise.

Since we were working offshore and onsite model , due to that as per client security restriction have installed development environment on BCTLD.COM domain,

QA and Production environment EURENK.COM domain.All we have installed on domain installations .Till now all working fine .

Now client decided to stop offshore support , from now only onsite support due to that , they have decided to move all the server development environment into QA and Production domain(EURENK.COM)

I know , it will not be much complicated at OS level to move one domain to another domain.Just need to remove the servers from one domain and re connect to another doamin.

Now my concern is SAP end ? Can my all SAP development servers can work when they reconnect to another domain with out any issues , which includes database SQL?

Is SAP supports this environment , one domain to another domain?

IF yes, what are the parameters need to change at SAP end?

What about environment variables , if they change one domain to another domain?

What are the pre-reqisites do i need to take care before moving this systems to another domain?

What are the challengs will i need to face , from OS end as well as SAP and Database end?

Please share if you have any thoughts .

Thanks,

Bo

[Former Member]

Hi,

DNS entries and hostnames would take care of network team.export R3LOAD and reinstallation would it be huge job.

Is there a another solution.

Thanks

Bo

[Former Member]

Lisa,

It should not really make a difference here, unless you've hardcoded servernames in the SAP system. Some of the items I'd check are:

1) The DEV os users - DEVADM and SAPServiceDEV are registered correctly in the ADS if you are not doing installations as local domain admins.

2) Force replication in your network to avoid resolution problems of your 'new' server since the IP address of the DEV box will have a new domain.

3) Check RZ10 for profile settings that use the FQDN stored in a non-IP form - "development.BCLTD.COM" and change them over.

4) Check SM54, SM55, and SMLG for any additional hardcoded servernames.

5) If SQL Server should also be able to pick up this change without issue as again, the IP address won't change (?), just the alias of the server.

SAP and SQL should look to the OS for it's network functions, not re-create them. However, there is still the possibility that someone's hardcoded the FQDN around the system.

Another option for you if you are still concerned about hidden items is to export the systems using SAPINST and R3LOAD, and use these exports to re-install the systems into the new domain. You'll be assured of a 'clean' installation this way.

Let me know how you make out. Hope the information was helpful.

-Tim