Error in the post installation steps of SLD .

Hi
We are working on EP7.0 2004s.We are using local sld.Right now I am doing the post installation steps for SLD.I added the J2EE and UME roles.In the next step I went into the administration tab of SLD for configuring.It is throwing this error.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
This is detailed exception I got.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:516)
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:462)
at com.sap.sld.wd.main.wdp.InternalMainInterfaceView.wdFirePlugToOldUI(InternalMainInterfaceView.java:154)
at com.sap.sld.wd.main.Head.onActionAdministration(Head.java:277)
at com.sap.sld.wd.main.wdp.InternalHead.wdInvokeEventHandler(InternalHead.java:227)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Please help me.
Thanx & Regards,
Naresh

Hi Naresh,
Can you let me know the service pack for the portal.
Also try login in using administrator using the http://<localhost><port>/sld
thanks
Pankaj

Similar Messages

Error in the post installation of SLD .

Hi
 We are working on EP7.0 2004s.We are using local sld.Right now I am doing the post installation steps for SLD.I added the J2EE and UME roles.In the next step I went into the administration tab of SLD for configuring.It is throwing this error.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
This is detailed exception I got.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
 at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:516)
 at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:462)
 at com.sap.sld.wd.main.wdp.InternalMainInterfaceView.wdFirePlugToOldUI(InternalMainInterfaceView.java:154)
 at com.sap.sld.wd.main.Head.onActionAdministration(Head.java:277)
 at com.sap.sld.wd.main.wdp.InternalHead.wdInvokeEventHandler(InternalHead.java:227)
 at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
 at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
 at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
 at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
 at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
 at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
 at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
 at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
 at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
 at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
 at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
 at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
 at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
 at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
 at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
 at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)

Please help me.
T
hanx & Regards,
Naresh

Hi Naresh
Try logging off from the current window.
and login again as "Administrator" .
use http://portalhostname:50000/sld
hope this helps
Cheers !!!
Satish Kumar.

Webdynpro error in Post installation steps of SLD

Hi
We are working on EP7.0 2004s.We are using local sld.Right now I am doing the post installation steps for SLD.I added the J2EE and UME roles.In the next step I went into the administration tab of SLD for configuring.It is throwing this error.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
This is detailed exception I got.
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Exit-Plug must no be triggered with an URL when running in portal. Use portal navigation instead to navigate to another application!
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:516)
at com.sap.tc.webdynpro.progmodel.view.View.navigate(View.java:462)
at com.sap.sld.wd.main.wdp.InternalMainInterfaceView.wdFirePlugToOldUI(InternalMainInterfaceView.java:154)
at com.sap.sld.wd.main.Head.onActionAdministration(Head.java:277)
at com.sap.sld.wd.main.wdp.InternalHead.wdInvokeEventHandler(InternalHead.java:227)
at com.sap.tc.webdynpro.progmodel.generation.DelegatingView.invokeEventHandler(DelegatingView.java:87)
at com.sap.tc.webdynpro.progmodel.controller.Action.fire(Action.java:67)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.doHandleActionEvent(WindowPhaseModel.java:420)
at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:132)
at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:335)
at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:299)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:711)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:665)
at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:232)
at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:152)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:62)
at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:53)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)
at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)
at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)
at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)
at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)
at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)
at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)
at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
at java.security.AccessController.doPrivileged(Native Method)
at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Please help me.
Thanx & Regards,
Naresh

Hey Aviad,
Yes I did, in my case I've installed PDK SP 9 over SP2 which is prohibited. If this is your case as well do the following:
1) From the Undeployment tab of the SDM select the com.sap.pct.pdk..
components.
2) Using the Archive remover tool which can be accessed from
System Administration > Support > Portal Runtime > Administration
Console > Archive Remover --> Remove the portal applications with prefixcom.sap.pct.pdk...
3) Navigate to Content Administration > Portal content > Content
Provided by SAP > Platform Add-Ons > Developer Content
and remove all the contents below this folder.
4) Restart the server
After this you can deploy the SP9 business package using the SDM.
Hope it helps,
Roy

What are the post installation steps for sap 4.7ee

what are the post installation steps for sap 4.7ee

Hi,
Post installation steps are as follows.
1.SICK to be run first to checkt the errors while installation.
2. Install SAP GUI
3. Set up the TMS. Configuration the domain controller through SE06 and then set up the transport system through TMS.
4. Change the default password of SP* and DDIC.
5. Set up the operations mode using RZ04 and SM63.
6. Apply patches through SPAM.
7 Schedule default background jobs through SM36.
8 Import default profiles through RZ10.
9. Schedule backup calender through DB13.
10. Create clients using SSC4
11. Install lisence
12. Schedule SGEN

Need help in post-installation steps of the PDK

Hello,
I have installed Java PDK 6.9 instead of 6.2.
At the post-installation steps I need to:
The example iViews in the Portal Development Kit connect to a SAP System with the system alias PDK_R3_BACKEND.
To run these examples you must define a system object for a test SAP System in your system landscape and assign the following aliases:
1. PDK_R3_BACKEND Reference to a R/3 system of your custom landscape.
2. PDKDummySystem Reference to provided system OBN-3. PDKDummySystem.
WebDynpro Reference to provided system WebDynpro.
My question is: When I create this System, which type template should it be and which configuration besides the above aliases should it have?
Roy

Hey Aviad,
Yes I did, in my case I've installed PDK SP 9 over SP2 which is prohibited. If this is your case as well do the following:
1) From the Undeployment tab of the SDM select the com.sap.pct.pdk..
components.
2) Using the Archive remover tool which can be accessed from
System Administration > Support > Portal Runtime > Administration
Console > Archive Remover --> Remove the portal applications with prefixcom.sap.pct.pdk...
3) Navigate to Content Administration > Portal content > Content
Provided by SAP > Platform Add-Ons > Developer Content
and remove all the contents below this folder.
4) Restart the server
After this you can deploy the SP9 business package using the SDM.
Hope it helps,
Roy

POST Installation steps for SAP XI 7.0 SP06

Hi Experts ,
We are trying to install XI 7.0 SP06.We are suppose to carry out post installation
steps but we are not able to locate a proper post installation guide for the same.
We have succesfully installed XI 3.0 earlier .However XI 7.0 post installation steps in the guide that we have "SAP NetWeaver 2004s SR1 ABAP+Java on Windows: Oracle" , are relatively less...
Nevertheless, we have carried out the following steps
5.21.1 Performing PI-Specific Steps for SLD Configuration
Local and Central System Landscape Directory (SLD)
Mapping Security Role to User
1. Log on to the Visual Administrator of the J2EE engine of the SLD host.
2. Choose Cluster® Server® Services® Security Provider.
3. In the Runtime tab, choose Policy Configurations and then the column Components, and select the component
sap.com/com.sap.lcr*sld.
4. Switch to the Security Roles tab to display the assigned roles.
5. Select role LcrInstanceWriterLD.
The user SLDAPIUSER already exists with its security role LcrInstanceWriterLD.
6. Switch to edit mode and add user PIAPPLUSER with the same role LcrInstanceWriterLD.
Note
For a central SLD, the user PIAPPLUSER must be created in the central SLD ABAP system first and be
assigned to ABAP role SAP_XI_APPL_SERV_USER. The password must be same as in the XI Exchange
Profile on the XI Integration Server.
Note
For information on the UME actions, see the Post-Installation Guide - SLD of SAP NetWeaver 2004s, section
Configuring SLD Security, at service.sap.com/sld® Media Library.
Maintaining SLD Connection Parameters (ABAP API)
1. Log on to the SAP XI Integration Server System as user DDIC and call transaction SLDAPICUST. The screen
Maintain SLD Access Data is displayed.
2. Choose Display <-> Change and proceed as follows:
a) Replace the existing SLDAPIUSER with PIAPPLUSER user.
Note
For a central SLD, make sure you use the user with security role LcrInstanceWriterLD.
b) Make sure your entry is marked as Primary.
Note
Only the entry marked as Primary is active.
c) Save your settings.
April 10, 2006 PUBLIC 97
Now we don't know wether the sld configuration is over or not ...or for that matter in RWB we see only J2se based adapter engine and not J2ee based adapter engine...
Kindly help

Hi..
Instaed doing this,please try out template based configuration which has been mentioned in the installation guide or else do as follows
1.Login into NWA (netweaver administrator)
as
http://<host.<domain>.<com>:<port>/nwa
2.Use J2ee_admin user id and password
3.go to deploy and change
4.select template based configuration for PI
5.execute the template
6.install it
you can find the list of other templates which are clear and easy to do the post installation step..i found it useful ..
Apart from these, as per sandro, you can check the data transfer in visual administrator or go the abap engine, transaction RZ70, press accept proposal button
then execute button , check the data supply without any error
Thanks
Gopal
(Avoid points if useful)

Post installation steps for PI 7.0

Hi,
Can anybody send me the Post installation steps for PI 7.0?
Thanks in advance..
~Kumar

Hello,
 
We did PI Installation recently and version is 7.1
 
Steps are as under...
 
 1. Basic PI installation
 2. System checks after basic installation
 a. SM50
 b. SM21
 c. ST22
 d. SM12
 e. SM13
 f. SM37
 3. Unlock the 001 client for cross-client changes temporarily and set system timezone (STZAC)
 4. Change 001 client settings back to no changes allowed.
 5. Create BASIS team member accounts in ABAP Stack and assign SAP_ALL.
 6. Set directory permission for \usr\sap\trans directory on Transport Domain Controller system.
 7. Import profiles (RZ10)
 8. Add the 4 following entries in to the instance profile and restart instance(RZ10)
 a. DIR_TRANS =
hostname.domain.ext\sapmnt\trans
 b. icm/host_name_full = hostname.domain.ext
 c. login/system_client = 100
 d. icm/server_port_0 = PROT=HTTP,PORT=5<sysno>00,TIMEOUT=1800,PROCTTIMEOUT=1800 {SAP Note 1107808}
 9. Configure TMS in transport domain controller{PI DEV} (STMS)
 a. Add virtual system
 b. STMS in newly installed system and configure proper transport domain
 c. In domain controller approve the new system (STMS -> SAP system -> Approve)
 10. Get maintenance certificate and SAP license from service marketplace and apply in to the new system {ABAP and JAVA} (slicense and NWA)
 11. Kernel Update JSPM
 a. JSPM update
 b. Kernel update
 c. BC-FES-IGS update
 12. Support pack installation ABAP
 a. SPAM update
 b. Support packs update
 13. Support pack installation JAVA
 a. Apply support pack stack
 b. Apply support pack patches
 i. After JVM installation Error occurs apply MS windows KB973544 {SAP Note 1367498}
 c. Restart JSPM and continue patch installation
 14. Client copy from client 001 to X00 using profile SAP_ALL
 15. Create logical system and assign it to new client (SALE)
 16. Change UME target in JAVA to client X00.
 a. Enter URL as http://hostname.domain.ext:port/nwa
 b. Management -> Infrastructure -> Destination
 c. Logon data TAB change client to X00
 d. Restart JAVA Instance
 17. Create following users
 a. PIAFUSER, PIRWBUSER, PIISUSER, PIDIRUSER, PIREPUSER and PIAPPLUSER on the target SLD and new system manually and assign role/group SAP_SLD_CONFIGURATOR to them. {SAP Note 1309239}
 b. PISUPER in new system and assign appropriate roles in ABAP and JAVA
 c. SLD_DS_<SID> and SLD_CL_<SID> on target SLD {Use source system master password}
 d. JCoRFC_<SID> in new system
 e. Sapadm user in new system
 18. Assign roles and groups to BASIS team on JAVA Stack
 19. Create PUBLIC logon group (SMLG)
 20. Configure SLD collector job as sapadm (RZ70)
 21. Run Configuration Wizard
 a. Enter URL as http://hostname.domain.ext:port/nwa
 b. Configuration management -> Scenarios -> Configuration Wizard
 c. Select Initial Configuration and click Start.
 22. Create the JCoRFC connection.
 a. Enter URL as http://hostname.domain.ext:port
 b. Web Dynpro -> Content administrator -> Maintain JCo destination
 c. Fill in information for the following 4 entries using client X00 and JCoRFC_<SID> as the user {Make sure you note the distinction between Metadata and Model destinations when you are creating the destination}
 i. WD_ALV_METADATA_DEST
 ii. WD_ALV_MODELDATA_DEST
 iii. WD_MODELDATA_DEST
 iv. WD_RFC_METADATA_DEST
(Use dictionary Meta Data for the Metadata connections, use Application Data for the Model Data connections.)
(Use the master password for EXQ)
 23. Repeat for the remaining 3 JCo RFC destinations.
 24. Run PI Full Qualified Host Name Wizard {SAP Note: 1320707}{Make sure you check the host names for integration server and SLD}
 25. Create RFC destination in to ERP target system (SM59)
 a. Give Name PI_INTEGRATIONSERVER
 b. Connection type H
 c. In Technical settings TAB provide
 i. Target host = hostname.domain.ext
 ii. Path Prefix = /sap/xi/engine/?type=entry
 iii. User information is blank
 26. Setting SXMB_ADM ERP target system
 a. Open Integration engine configuration
 b. Goto -> Change Global Configuration Data
 c. Role of Business system = Application System {This is optional}
 d. Provide RFC destination name in Corresponding Integ. Server = dest://PI_INTEGRATIONSERVER
 27. Schedule Standard Jobs as SAPADM in client X00.
 28. SICF service to activate
 a. /default_host/sap/public/bc/pictograms
 b. /default_host/sap/public/bc/webicons
 c. /default_host/sap/public/bc/its/designs
 d. /default_host/sap/public/bc/workflow
 e. /default_host/sap/bc/ccms
 f. /default_host/sap/bc/webdynpro/sap/CTS_BROWSER
 g. /default_host/sap/bc/webflow
 h. /default_host/sap/bc/workflow
 i. /default_host/sap/bc/workflow_xml
 j. /default_host/sap/bc/xmb
 k. /default_host/sap/bc/ping
 l. /default_host/sap/xi/wsdl_sr
 m. /default_host/sap/xi/wsdl_url
 n. /sap/bc/webdynpro/sap/appl_soap_management
 29. Adjusting JNLP Heap size
 a. Open the Exchange profile through the link u201Cadministrationu201D from the web page of the Process Integration tools.
 b. Under the folder u201CIntegration Builderu201D click on the variable u201Ccom.sap.aii.ib.clientjnlp.j2se.maxheapsizeu201D
 c. Value = 1024
 d. Save the change and restart the J2EE instance of PI so that the new value can take effect.
 30. Create RFC destination for Advanced Adaptor Engine in sender ERP system(SM59)
 a. RFC Destination = AAE_<SID>
 b. Connection type = G
 c. Target Host = Host Name of AAE Server {PI Server}
 d. Service No. u2013 HTTP port number of AAE Server
 e. Path Prefix = /XISOAPAdepter/MessageServlet?ximessage=true
 f. Under Logon & Security use PIAPPLUSER with PI target systemsu2019 master password.
 31. Create RFC destination <SID>_ALE in ERP Source system with user ERQALEUSER {Make sure you have this user created in new installed system}
 32. Install External Driver Configuration in Process Integration 7.1 Using JSPM {SAP NOTE: 1138877}
 
Please let me know if I am missing anything there...
 
Cheers,
 
Yogesh

XI Post installation steps

Hi,
I'm trying to get XI going at a project. The basis guys have installed the server but I have an idea none of the 'post installation steps' have been completed.
The symptoms are that when I start the Integration Builder (SXMB_IFR) the Windows 'File Explorer' is started and not IE. The Integration Web page is not displayed.
I quickly looked at the Configuration guide and I see none of the RFC destinations mentioned in the guide.
Is this the reason for the problem ?. I need to know exactly what totell the basis people to look at. They have never done an XI installation before so I'm almost sure they have not done these configuration steps.
Thanks
Andre

Hi Andre,
They should look at the intallation/configuration guides that SAP provides. These guides can be found at the service.sap.com and/or help.sap.com
In a nutshell you have to make sure they have configured:
SLD settings, these involves configuring RFC destinations, Maintain the SLD parameters in SLDAPICUST.
Register, Starting up the queues. Configure the role of the integration server in trx SXMB_ADM or SXMB_ADMIN.
Hope this helps.
Cheers,
Roberto
Message was edited by: Roberto Viana

What are post installation steps for SOA 10.1.3.5 patchset on Windows

Hi all ,
what are the post installation steps in windows after applying SOA patchset 10.1.3.5 on 10.1.3.1
Thanks,
Durga

Hi 924979,
may I ask cause I have same exactly this issue on solaris 10 and what do you mean with :
edit the (two) opmnctl scripts to change "tr" to "/usr/xpg4/bin/tr" ?
Need your suggestion since I change PATH environment variable but still error and The installer cannot find the system application ascontrol ("opmnctl status -app") in the OC4J instance. All system applications should be present even if they are in a stopped or non-routable state. This is generally due to a situation where OPMN has been shutdown ... bla bla bla .. (stop in 83%)
need advise
Regards,
Thanks

What are the post instalation steps?

hi,
i am fresher in SAP.anybody plz send me postinstalation steps.
regards,
jana

Hi All,
Rewards if useful.
Post Installation Steps For ECC 5.0
What are the post installation steps after I have installed the Central Instance and Database instance?
Initial Consistency Check
SM28
1. Logon to the newly refreshed SAP system and run transaction SM28
2. Ensure that no errors are reported. Otherwise, take the necessary steps to correct the problems.
Edit Batch Jobs
1. Set the fields as follows
Job name: RDDIMPDP*
User name: *
Job Status: Released and Ready checked off, all others unchecked
Fr: 01/01/0001
To: 12/31/9999
Or after event: *
2. Press <F8> to execute the query
3. Highlight the first job in the list and press the <CTRL>+<F11> to change the job.
4. Examine the Exec Target field.
a. If the box is empty, press <F3> to exit
b. If the box is not empty, then clear out the contents so the field is blank and press <CTRL>+<S> to save
5. Repeat Steps 3 and 4 for each additonal job listed.
Workbench Organizer Reconfiguration
1. Logon on to client 000 of the newly refreshed system with DDIC.
SE06
1. Select the Database Copy or migration option
2. Press the Post-installation Processing button.
3. When prompted Do you want to re-install the CTS?, press the Yes button
4. When prompted for the Source System of Database Copy?, make sure that the <SID> of the production system is selected. Press the checkmark button to continue.
5. When prompted Change originals from PRD to QUA?, press the Yes button
6. When prompted Delete TMS Configuration?, press the Yes button
7. When prompted Delete old TMS configuration?, press the Yes button
8. When prompted Delete Old Versions of transport routes?, press the No button
TMS Configuration
1. Logon on to client 000 of the newly refreshed system.
STMS
1. Upon starting STMS, a windows with the title TMS: Include System in Transport Domain should be displayed
2. The information on this screen is automatically filled out from information provided during the SAP installation and should be correct. If it correct, then enter a description for the system and press <CTRL>+S to save. Otherwise, press the Other configuration button and manually configure.
3. From the Overview menu, select Transport Routes
4. From the Configuration menu, select Adjust with Controller
5. Press the Yes button when prompted if you want copy the transport routes from the controller.
Import Printers
1. Logon on to the production client of the newly refreshed system.
STMS
2. Press <F5> to go to the import Overview.
3. Double click on the <SID> of the newly refresh system
4. From the Extras menu select Other Requests, then Add.
5. In the Transp. Request box, enter the transport number containing the printer definitions that was exported. Press <Enter> to save.
6. Select the transport that was just added to the queue and press <CTRL>+<F11> to start the import.
7. In the Target client box, enter the productive client of the newly created system. Press <Enter> to save.
8. Press the <Yes> button to start the transport.
Client Configuration
SCC4
1. From the Table view menu, select Display -> Change
2. When warned that the table is cross-client, press the checkmark button.
3. Double click on one of the non-system clients (i.e. not client 000, 001 or 066)
4. Define client as follows:
Client role: Test
Changes and transports for client-specific object: Changes without automatic recording
Client-independent object changes: Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
5. Press <CTRL>+S to save.
6. Repeat steps 4 through 6 for any additional clients
Set System Change Option
SE06
1. Press the System Change Option button.
2. Set the global setting to Modifiable
3. From the Edit menu, select Software Components Modifiable
4. From the Edit menu, select Namespaces Modifiable
5. Press <CTRL>+S to save.
Import Users
STMS
1. Press <F5> to go to the Import overview
2. Double click on the <SID> of the newly refreshed system.
3. Press <F5> to refresh the list of transports
4. Locate the transport in the list containing the user exports done before the start of the refresh.
If the transport is NOT in the list, then from the Extras menu, select Other requests then Add. Enter the transport number and press <Enter>. Then press the Yes button to add the transport.
5. Highlight the transport and press the Import request icon .
6. At the client import screen, enter the target client and then press the Import button
7. Press <Enter> to confirm that the import will proceed
SCC7
1. Run the Post Client Import Processing
2. The transport number should be the same as that of the transport started in STMS
3. Schedule the job to run in the background. Do NOT schedule it to run immediately. We need to modify the job before it can be released.
4. Press <CTRL>+S to save.
SM37
1. Set the fields as follows
Job name: CLIENTIMPORT*
User name: *
Job Status: All options checked
Fr: 01/01/0001
To: 12/31/9999
Or after event: *
2. Highlight the job that was created by SCC7 and press <CTRL>+<F11> to modify the job.
3. Press the Step button.
4. Select the RSCLXCOP line and press <CTRL><SHIFT><F7> to modify that step.
5. In the User box, enter the background user for that particular system (i.e BGDUSER, SAPBATCH, BATCHSAP).
6. Press <CTRL>+S to save the changes
7. Press <F3> to go back to the main job screen.
8. Press the Start condition button.
9. Press the Immediate button.
10. Press <CTRL>+S to save the changes
11. Press <CTRL>+S again to save all the changes to the job.
12. Job will start immediately once saved. Press <F8> to refresh the list of jobs
13. Continue to press <F8> every once in a while to update the status of the job. Do not continue until the job is completed sucessfully.
SCC4
1. From the Table view menu, select Display -> Change
2. When warned that the table is cross-client, press the checkmark button.
3. Double click on one of the non-system clients (i.e. not client 000, 001 or 066)
4. Set the Protection to Protection level 1
5. Press <CTRL>+S to save.
6. Repeat steps 3 through 5 for any additional clients
Deleting Source System Profiles
RZ10
1. From the Utilities menu, select Import Profiles then Of Active Servers.
(Note: All application servers of the target system must be started)
2. If the Display Profile Check Log screen is displayed, press <F3> to leave this screen.
3. Select the Profile field and press <F4> to bring up a list of profiles.
4. From the list select one of the profiles associated with the source production system.
5. From the Profile menu, select Delete, then All versions, then of a profile.
6. When prompted, press the Yes button to delete all version of the profile
7. When prompted to delete the file at the operating system level, press the No button.
8. Repeat steps 3 through 7 for all additional profiles associated with the source system
Reconfigure Operation Modes
RZ04
1. From the Operation Mode menu, select Timetable
2. Select Normal Operation and press the Change button.
3. Highlight 00:00 in the left hand column and press the Delete Assignment button
4. If all the assignments are not deleted, then highlight the start time of the outstanding assignment and press the Delete Assignment button.
5. Once all the assignments are deleted, press <CTRL>+S to save.
6. If warned about an empty timetable, press the checkmark button and then press Yes to save the empty timetable.
7. Press <F3> to go back to the main RZ04 screen.
8. Right click on one of the listed Operation modes and select Delete
9. Press the Yes button to confirm the deletion.
10. Repeat steps 8 through 9 for any additional operation modes
11. Press <F5> to create a new operation mode.
12. Enter a name and short description for the operation mode
13. Press <CTRL>+S to save.
14. Press <F6> to create a new Instance
15. From the Settings menu, select Based on current settings, then New Instances, then Set
16. Press <F3> to go back to the main RZ04 screen.
17. Press the Yes button to save
18. From the Operation Mode menu, select Timetable
19. Select Normal Operation and press the Change button.
20. Highlight the 00:00 at the top and press <F2>
21. Highlight the 00:00 at the bottom and press <F2>
22. Press the Assign button.
23. Press <F4> to select the operation mode created above.
24. Press <CTRL>+S to save.
Delete Update Failures
SM13
1. Set the fields as follows
Client: *
User: *
From data: 01/01/0001
From time: 00:00:00
2. Press <Enter> to display the list of outstanding update requests
3. If ALL the outstanding update requests have a status of ERR, then it is safe to delete these requests by pressing <F5> to select all records, then selecting the Update Records menu, then Delete.
4. Press the Continue button to confirm the deletion.
Delete Batch Input Sessions
SM35
1. From the Edit menu, select Select All
2. Press <Shift>+<F2> to delete all the batch input sessions.
3. Press the checkmark button to confirm
4. Press the Yes button to start the delete.
Reorganize Spool
SPAD
1. From the Administration menu select Clean-up Spool
2. Check all check boxes and enter 0 for minimum age
3. Press the Execute button
4. Once complete, press <F3> twice to get back to the main SPAD screen
5. From the Administration menu select Check Consistency
6. Press the Delete All button.
SP12
1. From the TemSe database menu, select Consistency check
2. When the check is complete, press the Delete All button.
Delete Invalid Background Control Objects
SM61
1. Press <F8> to switch in to change mode
2. Press the Cleanup List button.
Restrict Outgoing Email and Faxes
SCOT
1. Double click on the green Fax entry
2. From the Supported Address Types area, press the Set button that is beside Fax
3. In the Address area, ADJUST AS NECESSARY
4. Double click on the green SMTP entry
5. From the Supported Address Types area, press the Set button that is beside Internet
6. In the Address area, ADJUST AS NECESSARY
Adjust RFC connections.
SM59
1. Expand the TCP/IP connections section
2. Double click on the first entry listed
3. Check the gateway host and gateway server to make sure it points to the appropriate NON-PRODUCTION system.
Make changes as necessary.
4. Press the Test Connection button to test the connection
5. Press Press <CTRL>+S and then <F3> to save and return to the list of RFCs.
6. Repeat steps 1 through 5 for each additional RFC connection
Convert Logical Systems
Under no circumstances perform this procedure on a Production system
BDLS
1. When warned to read the documentation, press the checkmark button.
2. In the Old logical system name box, press <F4>.
3. Select one of the production Logical System names that needs be changed (i.e. WIIPRD400)
4. In the New logical system name, enter what that logical system name should be called on this newly refreshed system (i.e.WIITRN400) Note: Ignore Error/Warning about duplicate system by clicking on the check mark.
5. De-select the Test Run and Existence check on new names in tables options
6. From the Program menu, select Execute in background
7. Press the checkmark button when asked to select a spool device
8. Press the Immediate button when asked for the schedule
9. Press <Ctrl>+S to save
10. Use SM37 to monitor the job
11. When job is complete, repeat steps 2 through 10 for any additional logical system names that need to be changed.
Adjust Logical Systems names
SALE
1. Expand Sending and Receiving Systems, then Logical Systems
2. Click on the execute icon beside Define Logical System
3. Press the checkmark button to confirm that the change is cross client
4.
Allow Certains Settings to be modifiable
(Refer to Note 356483 for more Details)
SM54
1. Enter V_T001B in the Table/View box.
2. Select the Generated Objects option.
3. Press the Create/Change button.
4. Enter any access keys if requested
5. Change the Recording routine to no, or user, recording routine.
6. Press <Ctrl>+S to save
7. Press <Enter> if warned that you are changing a function group that doesn't belong to you.
8. You are prompted for transport. Create a new local transport.
9. Repeat steps 1 through 8 for the following objects. You can specify the same transport you created above.
V_T001B_GL
V_T093B_01
V_T093B_02
BSI Configuration (R3 HR Systems only)
SM59
1. Expand TCP/IP Connections
2. Highlight BSI70-US-TAX and press the Change button
3. Change the program field to
<hostname>\sapmnt\<SID>\SYS\EXE\RUN\TF60SERVER.EXE
4. Double check the target host and gateway point to the correct server
5. Press <CTRL>+S to save
6. Press the Test connection button to test. If the connect is not successful, take the necessary steps to resolve the issue.
SE38
1. In the Program field, enter RPUBTCU0
2. Press <F8> to execute
3. Select option BSI version 7.0
4. Press <F8> to execute
5. BSI should return tax calculations. If there are errors, take the necessary steps to resolve.
Reconfigure DB13 schedule
DB13
1. Using the print out created before the refresh, recreate the DB13 calendar.
Client Configuration
SCC4
1. From the Table view menu, select Display -> Change
2. When warned that the table is cross-client, press the checkmark button.
3. Double click on one of the non-system clients (i.e. not client 000, 001 or 066)
4. Define clients as follows depending on client role
Development
Client role: Customizing
Changes and transports for client-specific object: Automatic recording of changes
Client-independent object changes: Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
Quality Assurance
Client role: Test
Changes and transports for client-specific object: No changes allowed
Client-independent object changes: No Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
Training
Client role: Education
Changes and transports for client-specific object: No changes allowed
Client-independent object changes: No Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
Sandbox
Client role: Test
Changes and transports for client-specific object: Changes without automatic recording
Client-independent object changes: Changes to repository and cross-client customizing allowed
Protection: Client copier and comparison tool: Protection level 0
Restrictions when starting CATT and eCATT: eCATT and CATT allowed
5. Press <CTRL>+S to save.
6. Repeat steps 4 through 6 for any additional clients
Set System Change Option
Skip this section of the system is a Development or Sandbox System.
SE06
1. Press the System Change Option button.
2. Set the global setting to Not Modifiable
3. Press <CTRL>+S to save.
Release Background Jobs
Currently, all background jobs, except for system standard jobs have been placed on hold (status scheduled).
Rewards if useful.
Regards,
Pherasath

Post installation steps for SAP PI, scenarios for SAP ERP 6.0 EhP 3.0 BAIO

Hi!
I installed SAP NetWeaver 2004S with PI component.
I also have a demo SAP ERP 6.0 EhP 3.0 BAIO system with several clients:
(100: demo client, 200: BW, 300: demo client (copy of 100)).
Questions:
what are the post installation steps to configure SAP PI?
Which scenarios can be used in such landscape?
(eg. exchange (IDOC, RFC, etc.) from client ERP:100 to ERP:200)
Thank you very much indeed!
regards
Holger

Hi Holger:
what are the post installation steps to configure SAP PI?
http://help.sap.com/saphelp_nw70/helpdata/en/a0/40084136b5f423e10000000a155106/content.htm
Which scenarios can be used in such landscape?
(eg. exchange (IDOC, RFC, etc.) from client ERP:100 to ERP:200)
I recommend you to use proxys in your landscape as you want to interchange messages between
different clients in the same system.
Hope this helps you.
Carlos

Post Installation Steps for ERP add-on Inventory Manager 4.0

Hi,
I need to confirm what are the post-installation activities we must to perfom for ERP Add-on (Inventory Manager 4.0), besides de BC Activation. I did not find any information regarding the post installation steps for the ERP Add-on of Inventory Manager 4.0 (the installation guide for IM 4.0 on service marketplace does not remark the steps only explain the theorical part of the installation)... And we need to confirm if the steps are the same of Inventory Manager 3.2 Add-on or we must do an additional step?
Best Regards,
MC
Stephen Streeter Manju Venkatesha

Yeah...of course...
I forgot to specify it.
I install the first ERP 2005 SR2 on Oracle 10.2.0.2 and the other have to be installed on the same version of DB.
All installation are not MCOD.
This mean every installation has its own DB with different SID for every installation.
And of course I have at least doubled the space required by installer. Taken from sap notes the required space for ERP 2005 SR2 is about 90 GB.
The total space of mount point is about 500 GB....
Thanks
Dan

Post installation steps for EP 7.0

Hi All,
I have installed EP 7.0 SR1 on windows with Oracle and its successful. (I have selected usage types Java and EP during installation).
As per the installation guide its said to login as below:
http://<hostname>:50100/irj --> but when i open it, it says The requested resource does not exist. But i am able to open normal NW page: http://<hostname>:50100 and access UME, SAP NW Administrator>..
I have applied permanent license in Visual Administrator. but didnt do any of the post installation steps. I didnt see any of the post installation step in guide also, could you please guide me in completing this?
Thanks,
Subbu

Hi All,
Thanks for ur response, i am able to open the portal by giving the address as u mentioned..thank u..But i am facing problem as i couldnt see some options: I read the following in help.sap.com
When you install a portal, you also install predefined system templates for all the connectors that the portal provides. These templates are contained in the System Landscape Templates folder, under
System Administration--> System Configuration --> Portal Content --> Templates
, and can be edited in the Property Editor. Editing a template affects any systems that you create based on this template
I am able to navigate System Administration--> System Configuration but not able to see the option
Portal Content --> Templates
The other point mentioned is:
The system administrator can disable logon by means of the IP address as follows:
Navigate to System Administration --> System Configuration -->
Service Configuration
. i m not able to find the option Service Configuration here??
I have installed NW 2004s SR1, in help.sap.com they didnt mention anything specific abt. release. Could you please guide me why i am missing those options??
Thanks,
Subbu

Post Installation steps for Messages archiving from Adapter engine

Hi,
Can any let me know the post installation steps for Archiving messages from AE.
We are archiving the messages from Integration Engine (BC_XMB).
This note refers to the Post installation steps... But i could not find them anywhere.
Note 790226 - Messages in AdapterEngine/PCK database do not get archived
Thanks,
Tanuj
Message was edited by:
Tanuj Kumar Bolisetty

Hi Tanuj,
have a look at note 872388
"2) For messages in the Adapter Framework: note 816022, question 8
(deletion) and
http://help.sap.com/saphelp_nw04/helpdata/en/cf/b2fc3f48ecc742e10000000a
1550b0/content.htm (archiving)"
Additionally consult the troubleshooting guide,page 110
Set the adapter service properties (note 791379)
Hope it helps
Jaime

Post Installation steps for Solution Manager 4.0 SP10

Hi,
Can any one of you help me out to do the post installation steps to be done after installing solution manager.
Thanks in advance.
Thanks
Venu

Hi Dolores,
I am not able to find iTutor anywhere in service.sap.com/rkt-solman.
Could you please give us the perfect path for that?
Regards
Pranav

Error in the post installation steps of SLD .

Similar Messages

Maybe you are looking for