Enterprise Portal System Refresh Document Part-2
Enterprise Portal System Refresh Part -2
Portal Refresh can be devided into 4 parts.
2. Export Phase
3. Import Phase
Once you are finish with Pre refresh and post refresh work then you can start all the activity in Target system.
To start with import of SAP system in Target system, make sure you have logged on to Taget system with administrator user.
Start SAPINST from SWPM folder.
Software Life-Cycle — System Copy — DB –Target system Installation– Distributed system (if your DB and CI in different host) –Based on AS Java — SCS instance
Provide target system SID
Provide Password for SAPADM user. (User ID sapadm to Run the SAP Host Agent)
Create (Or provide) SCS Instance No.
SCS Message Server Port will be created automatically
Just press NEXT …..
You have successfully installed SAP SCS Instance in the system.
Now we need to import Database portion
If you are working on Distributed system then you will have to log on to Database host to perform this activity.
If you are working on Central type of system then you can do this on CI host itself.
Start SAPINST.exe to start activity:
You will have to download Kernel of SAP system
Select the path of Profile Directory:
Choose MASTER Password for your system
Here you have to select whether you are working on DOMAIN of Local Computer
As we are doing EXPORT/IMPORT, select 1st option.
Here you will have to provide DB host name.
Provide path of your DB home
DB server Version
DB Client Version
and select the passwrod for JAVA DB schema
You need to provide the DB EXPORTED file, this has been exported in Export Section.
Select the LABELIDX.ASC file.
Specify the location of SAPDATA directory where your Datafiles resides.
Provide password for SYS and SYSTEM user
Provide the Listerner Entry and select both (KEEP) Lister.ora and tnsnames.ora. System will create new entry for these 2 files and will create 2 new files with same name.
After that you can replace the old files with new files. (Once you finish with all work)
Below selection will improve the system performance 100%.
Here we have select the Java Component, that we can download from markate place
Here we have to provide the Database Client because SAP Installation always requires the client configuration during installation phase this will override your old DB Client.
For sure you will have to download from Markate place.
Here you will find the summary of all your selection in earlier scrrens.
Import of DB will be finished here once it reach to last Phase.
Till Now you have imported SCS and DB. It your turn to import Central Instance of of your system.
There will be many screens, which are common to DB import hence you can see discription there.
Perform these action in CI system host.
Go to folder SWPM and start SAPINST.EXE,
Reach to Below Location and select Central Instance
Selecting custom so that we can put value manually
Select (Or Create) the CI Instance No.
Provide the Transport Host server name
Here you have to select the LABELIDX.ASC from the export folder of CI. This was exported in Export phase.
Password for ADMINISTRATOR user
Password for SDM user
Below Screen may differ to you … select as per your environment.. (Optionally you can select all)
Summary of CI import.. review it and press NEXT.. (You can make changes, if there were some mistake during selection)
Once you finish with last phase “Recover Enterprise Portal Runtime Data”, CI import will be completed. You will get message the you have successfully completed this task.
1. Restart your SAP & DB.
2. Import Backend systems transport Packages in Target system
3. Cross verify that portal system is added in SLD.
4. Configure all JCO in the target portal system, you can refer Export phase for all screenshot taken during export phase.
5. Check the settings of Config tool (Cross verify with Export phase)
6. Check the settings of Visual Admin tool (Cross verify with Esport phase)
7. Check SLD Data Supplier entries from Visual Administrator. That is important for SLD to be working.
7. Configure SSO for Backend system.