Transport Mechanism in Portal

Folks,
How do we transport content from Dev to QA to Production in 2004s SYstem , Do we need to have NWDI for this or any other option is available ?

Hi Manish,
I will give you the starting points but you have to go into details for each subject :
SAP NetWeaver Development Infrastructure (NWDI)
https://www.sdn.sap.com/irj/sdn/was?rid=/webcontent/uuid/f6eb8e9e-0901-0010-8abb-cba5279db9b6
Transport of Portal Objects
http://help.sap.com/saphelp_nw04s/helpdata/en/c5/56599164d0c04cb566ba0e2d7ed55c/frameset.htm
XML Content and Actions
http://help.sap.com/saphelp_nw04s/helpdata/en/93/28f999daa6434a845da6bf9ab5072c/frameset.htm
Information and Content Exchange (ICE)
Information and Content Exchange (ICE)
Regards
Abdul.

Similar Messages

  • WPC Transport Mechanism

    We have currently 40 users to add content in the Web Page Composer (WPC) tool, but we are preparing for 100+ users when we start converting our existing Intranet content. We are interested in what your experience has been and what may be some lessons learned while using the WPC.
    What kind of transport mechanism do you have in place (CTS u2013 manual or automated, ICE)? We would like to allow our users to push their content to PRD when they completed development and testing.
    Any ideas or pointers would be greatly appreciated. Thanks!

    Simone-
    As from our experience. It is best to have content admin for the intranet sites to create there content in production. Make sure they are given permissions only to create and modify content on WPC sites.
    Its just content in production. That means they dont break any thing else.  Creating content in Dev and transporting is not advisable. Because users create content every now and then. and they want it to show up immediatetly. It not worth the time spending on transport to.
    EG. If user changes one link. You have to actually transport in all system. Which is more easier to change in prod.
    Just control the permissions for users and give content admin for that website.
    Please follow the link for more info on transporting.
    http://help.sap.com/saphelp_nw70/helpdata/en/47/276706548a2deae10000000a1553f7/frameset.htm
    Raj

  • Transport Mechanism in XI

    What is the transport mechanism in XI??
    How to transport from Development system to Production syatem.
    Is there anyway other than Import or Export??
    Thanks in advance,
    Jeevan.

    When you migrate the Integration Server and the Integration Builder, you install a new IS/IB
    3.0 on additional hardware. After completing the Customizing on IS 3.0, you use XI tools to
    migrate XI configuration and runtime data from the IS 2.0 to the IS 3.0 system. Finally, you
    have to switch the addressing for all application systems, adapters, and SLD parts from IS
    2.0 to IS 3.0.
    You can prepare most steps in setting up Release 3.0 without interrupting the operative use
    of Release 2.0. Therefore, the XI downtime is kept to a minimum.
    The basics of the migration procedure are as follows:
    1. Installation and Customizing of Integration Server and Integration Builder (XI 3.0) on a
    standby host machine (all-in-one)
    2. Migration of SLD data from Release 2.0 to 3.0.
    3. Migration of XI Integration Builder data from Release 2.0 to 3.0.
    4. Cache refresh.
    5. XI downtime starts, which disables the input stream into IS 2.0 / IS 3.0.
    6. Migration of essential runtime data.
    7. XI downtime ends, which enables the input stream into IS 3.0 again.
    8. Address switching of adapters and application systems from IS 2.0 to IS 3.0.
    Migration starts with the upgrade of the DEV landscape (including the DEV SLD) to Release
    3.0
    After upgrading the DEV landscape, there is no way to transport configuration data
    from the DEV 3.0 landscape to the QA 2.0 or PRD 2.0 landscapes.
    We recommend that you perform all required transports from DEV to QA or
    PRD before the migration procedure is started for the whole landscape.
    • If you need to make configuration changes after the DEV landscape migration to DEV
    3.0, for example, for emergency corrections, you need to make the configuration
    changes separately and in parallel for DEV 3.0 as well as for QA 2.0 and PRD 2.0.
    The transport mechanisms for the SLD and Integration Builder are described in the Online
    Help.
    All application systems in the DEV landscape must switch their addressing to the new
    Integration Server 3.0 of the DEV landscape. For more information, see the relevant sections
    below.
    you could detaild information from this link
    http://help.sap.com/bp_bpmv130/Documentation/Upgrade/XI_Upgrade_Guide.pdf
    reward the points if it helps
    Regards
    Naim

  • Transport Mechanism in MDM

    Hi,
    Can you please tell me how transport mechanism works for MDM from development to Testing to Production?
    (Scenario is that all the three repositories are on  different boxes and three MDM systems are maintained in SLD)

    Hi Jaydeep,
               Are you using SP03 or SP04? As per my knowledge SP03 is not build for this kind of scenario.
    For SP04 it is possible to use transport utility. Please go thru the following link for your reference<a href="/people/savitri.sharma/blog/2006/08/03/increased-functionality-and-ease-of-use-the-ins-outs-of-mdm146s-new-transport-utility Utility</a>
    Thanks & Regards,
    Ronak Gajjar
    <b>Please mark helpful answer</b>

  • Data transport mechanism

    A customer has asked if I can describe our "data transport mechanism(s)" to move data between their databases. I have not been able to get more detail on what they are looking for, other than TCP is too low level.
    We connect from one Oracle database to remote databases using database links for Oracle databases and Heterogeneous Services (ODBC or OLEDB) for other databases.
    Can anybody help with a reference to Oracle's mechanism, or even some other "data transport mechanisms" so I can search for something at the correct level?
    Thanks in advance,
    David

    I would think a brief description of Oranet and ODBC would do the job along with a diagram of the Oranet (database link) database to server/database and ODBC connections.
    Oracle has white papers on Heterogeneous Services (also called generic connectivity) available on metalink.
    HTH -- Mark D Powell --

  • Error while trying to open Transport Object in portal

    Hi,
    I want to move some pcd objects from my DEV server to PROD server.
    I created a transport object in the pcd but when I try to open it for editing, I get the following exception:
    Date : 06/18/2008
    Time : 20:01:49:094
    Message : Exception ID:05:01_18/06/08_0066_222946050
    [EXCEPTION]
    com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
    Component : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.export
    Component class : com.sapportals.portal.pcd.admintools.export.ExportMain
    User : MAYAS
         at java.lang.Throwable.<init>(Throwable.java:194)
         at java.lang.Exception.<init>(Exception.java:41)
         at java.lang.RuntimeException.<init>(RuntimeException.java:43)
         at com.sapportals.portal.prt.runtime.PortalRuntimeException.<init>(PortalRuntimeException.java:81)
         at com.sapportals.portal.prt.component.PortalComponentException.<init>(PortalComponentException.java:54)
         at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:200)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:115)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:177)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:201)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:633)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:200)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:115)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:177)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:561)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:107)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:438)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:404)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:79)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at com.sapportals.appdesigner.appdesignerfw.TabContentComponent.doOnNodeReady(TabContentComponent.java:110)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:386)
         at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:155)
         at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:306)
         at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:292)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:561)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:107)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:438)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:404)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:79)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:332)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:0)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:335)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:963)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:249)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:0)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:92)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:30)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:35)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:101)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/pcd/admintools/export/ExportGeneric
         at java.lang.Throwable.<init>(Throwable.java:194)
         at java.lang.Error.<init>(Error.java:49)
         at java.lang.LinkageError.<init>(LinkageError.java:36)
         at java.lang.NoClassDefFoundError.<init>(NoClassDefFoundError.java:40)
         at com.sapportals.portal.pcd.admintools.export.ExportJndi.getSemanticObject(ExportJndi.java:92)
         at com.sapportals.portal.pcd.admintools.export.ExportCompContext.isUnitAvailable(ExportCompContext.java:414)
         at com.sapportals.portal.pcd.admintools.export.ExportCompContext.setIntialContext(ExportCompContext.java:43)
         at com.sapportals.portal.pcd.admintools.export.ExportMain.doContent(ExportMain.java:27)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:166)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:111)
         ... 42 more
    Severity : Error
    Category : /System/Server
    Location : com.sap.portal.portal
    Application : sap.com/irj
    Thread : SAPEngine_Application_Thread[impl:3]_10
    Datasource : 222946050:/usr/sap/YED/JC22/j2ee/cluster/server0/log/defaultTrace.trc
    Message ID : 00145EC6C66B005E00000CED0000997600044FF3D1028EED
    Source Name : com.sap.portal.portal
    Argument Objs : com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
    Component : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.export
    Component class : com.sapportals.portal.pcd.admintools.export.ExportMain
    User : MAYAS
         at java.lang.Throwable.<init>(Throwable.java:194)
         at java.lang.Exception.<init>(Exception.java:41)
         at java.lang.RuntimeException.<init>(RuntimeException.java:43)
         at com.sapportals.portal.prt.runtime.PortalRuntimeException.<init>(PortalRuntimeException.java:81)
         at com.sapportals.portal.prt.component.PortalComponentException.<init>(PortalComponentException.java:54)
         at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:200)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:115)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:177)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:201)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:633)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:200)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:115)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:177)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:561)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:107)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:438)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:404)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:79)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at com.sapportals.appdesigner.appdesignerfw.TabContentComponent.doOnNodeReady(TabContentComponent.java:110)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:386)
         at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:155)
         at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:306)
         at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:292)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:561)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:107)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:438)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:404)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:79)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:332)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:0)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:335)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:963)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:249)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:0)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:92)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:30)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:35)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:101)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/pcd/admintools/export/ExportGeneric
         at java.lang.Throwable.<init>(Throwable.java:194)
         at java.lang.Error.<init>(Error.java:49)
         at java.lang.LinkageError.<init>(LinkageError.java:36)
         at java.lang.NoClassDefFoundError.<init>(NoClassDefFoundError.java:40)
         at com.sapportals.portal.pcd.admintools.export.ExportJndi.getSemanticObject(ExportJndi.java:92)
         at com.sapportals.portal.pcd.admintools.export.ExportCompContext.isUnitAvailable(ExportCompContext.java:414)
         at com.sapportals.portal.pcd.admintools.export.ExportCompContext.setIntialContext(ExportCompContext.java:43)
         at com.sapportals.portal.pcd.admintools.export.ExportMain.doContent(ExportMain.java:27)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:166)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:111)
         ... 42 more
    Arguments : com.sapportals.portal.prt.component.PortalComponentException: Error in service call of Portal Component
    Component : pcd:portal_content/com.sap.pct/admin.templates/iviews/editors/com.sap.portal.export
    Component class : com.sapportals.portal.pcd.admintools.export.ExportMain
    User : MAYAS
         at java.lang.Throwable.<init>(Throwable.java:194)
         at java.lang.Exception.<init>(Exception.java:41)
         at java.lang.RuntimeException.<init>(RuntimeException.java:43)
         at com.sapportals.portal.prt.runtime.PortalRuntimeException.<init>(PortalRuntimeException.java:81)
         at com.sapportals.portal.prt.component.PortalComponentException.<init>(PortalComponentException.java:54)
         at com.sapportals.portal.prt.core.PortalRequestManager.handlePortalComponentException(PortalRequestManager.java:973)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:200)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:115)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:177)
         at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:201)
         at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:633)
         at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:200)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:115)
         at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:177)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:561)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:107)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:438)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:404)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:79)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.doWork(RequestDispatcherImpl.java:321)
         at com.sap.engine.services.servlets_jsp.server.runtime.RequestDispatcherImpl.forward(RequestDispatcherImpl.java:377)
         at com.sapportals.appdesigner.appdesignerfw.TabContentComponent.doOnNodeReady(TabContentComponent.java:110)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.handleEvent(AbstractPortalComponent.java:386)
         at com.sapportals.portal.prt.pom.ComponentNode.handleEvent(ComponentNode.java:155)
         at com.sapportals.portal.prt.pom.PortalNode.fireEventOnNode(PortalNode.java:306)
         at com.sapportals.portal.prt.pom.AbstractNode.addChildNode(AbstractNode.java:292)
         at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:561)
         at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:107)
         at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:438)
         at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:404)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
         at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:79)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:332)
         at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:0)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:335)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:963)
         at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:249)
         at com.sap.engine.services.httpserver.server.Client.handle(Client.java:0)
         at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:92)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:30)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:35)
         at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
         at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:101)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
    Caused by: java.lang.NoClassDefFoundError: com/sapportals/portal/pcd/admintools/export/ExportGeneric
         at java.lang.Throwable.<init>(Throwable.java:194)
         at java.lang.Error.<init>(Error.java:49)
         at java.lang.LinkageError.<init>(LinkageError.java:36)
         at java.lang.NoClassDefFoundError.<init>(NoClassDefFoundError.java:40)
         at com.sapportals.portal.pcd.admintools.export.ExportJndi.getSemanticObject(ExportJndi.java:92)
         at com.sapportals.portal.pcd.admintools.export.ExportCompContext.isUnitAvailable(ExportCompContext.java:414)
         at com.sapportals.portal.pcd.admintools.export.ExportCompContext.setIntialContext(ExportCompContext.java:43)
         at com.sapportals.portal.pcd.admintools.export.ExportMain.doContent(ExportMain.java:27)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:166)
         at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:111)
         ... 42 more
    Dsr Component : DEVQA.YAFORA_YED_222946050
    Dsr Transaction : 144e38f03d5811ddb67400145ec6c66b
    Dsr User : MAYAS
    Indent : 0
    Level : 0
    Message Code :
    Message Type : 1
    Relatives : /System/Server
    Resource Bundlename :
    Session : 8815
    Source : com.sap.portal.portal
    ThreadObject : SAPEngine_Application_Thread[impl:3]_10
    Transaction :
    User : MAYAS
    The error occurs only on the DEV server.
    My Portal is EP7 SP15.
    How do I solve this?
    Thanks,
    Omri

    Solved it on my own by restarting the portal.

  • Unable to upload Transport Package in portal

    Hi
    Previously i have transported .epa file(Trnasport Package) from dev to acc, it worked fine there.now when iam trying to upload the same in qas portal its getting error like "could not upload file" .can any one assist me with the solution

    Sekhar,
    Please check the transport_logger trace (logs/transport.log) to troubleshoot transport problems.
    Set the loglevels to analyze the transport problems debug in the pcdstartup.properties file for the categories pcd.tracelevel.basictransport and pcd.tracelevel.GI.Transport
    Please check Note 679516: Central Note for the Transport Package Editor
    Please check Note 743857: Upload issues in cluster scenarios
    Please examine this file for pure UI problems like the editor does not load or an object cannot be added to a transport package. pcd_admin_tools_logger (logs/pcdadmintools.log)
    Hope it helps.
    Regards,
    Mona

  • How to Transport iViews from Portal Dev system to Prod system?

    Hello friends,
    This is an urgent request and it would be of great help if you can give me a solution to this.
    We have a Development Portal and a Production Portal. There is no QAS Portal. We are on EP 5.0 and BW is 3.5. Coming to my question, I have created an iView on a Web Application Designer template and assigned it to a role on the Development Portal. The report displays well on the Portal. Now I want to move this newly created iView to Production Portal. I absolutely have no idea how to do this as it is generally a Portal person's work and I have been asked to do this as the Portal person is currently on leave. I need to move the iView to Production as quickly as possible and I would really appreciate if any of you can send me detailed steps on how to do this.
    The best way to say thanks in SDN is to assign points to helpful answers and I will not forget that.
    Thanks,
    Deepthi.

    Hi Deepthi,
    observe these links:
    Here is some material:
    How to Transport Models Within SAP Analytics
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/035be5d4-0a01-0010-b48a-d4c8c9b020b5
    Actually, those pieces are also included in my book "SAP NetWeaver Visual Composer" which is already available from SAP-Press ( http://www.sap-press.com/product.cfm?account=&product=H1932 )
    If Usefull Asain the points.
    Thanks,
    kiran.
    Message was edited by:
            kiran manyam

  • How transport works in Portal..

    Hi,
    Suppose in Development I have a folder (F1) containing 2 objects (O1 and O2). The same folder(F1) with same content(O1 and O2) I have in Quality system.
    Now I have deleted the objects O1 and O2 from F1 in Development and added O3 and O4. Now I have trasported F1 to Quality.
    What would be the output in Quality?
    here are the options:
    1) F1 with objects O1, O2, O3 and O4
    2) F1 with objects O3 and O4 only.
    Thanks,
    Abhi

    Hi,
    the Portal 7.0x EPA transport is doing transport by adding files. There is an alternative available: XML transport. There you can also select the option: delete content first.
    In 7.3 portal objects can be transported by the mean of a synchronized folders that [allow you to transport the delta|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/wlg/23708]
    br,
    Tobias

  • Can portal role assignment be transported to another portal?

    Hi, Gurus:
    i need to transport portent, role, uses, etc from one portal (EP6 on NW04 )to another (EP7 on NW04s).
    can you tell me that if portal role assignment can also be transported?
    same question to ume role.
    very confused at this area.
    hope i can get your advice
    Thank you
    Br,
    Nikko

    Strictly speaking the user/group/role assignment is not part of the normal transport process in that it will not make those mappings when you transport the content to the next system in your architecture.
    However - you can export users / groups which includes the mappings details.  This can be used in your downstream systems.
    Subsequent transports of objects do not "break" existing mappings.
    Haydn

  • Can any one explain How transport mechanism happens

    explain the concept of Transporting objects or packages from dev to production

    Follow this steps in Development server
    First login into development server
    1)Try to keep all the objects in one folder(say myfolder) under portal content.
    2)Now come to system administrator->tranport-> tansport package->export->portal content-> create a new folder
    3)Select this new folder right click new transport package-> give the name and id->finish ->and close the transport package.
    4)Now open the transport package which u have created just now.(make sure that u r transprt package is opend at right in content area)
    5)Now select your folder which contains actual content(i.e iviews,pages,worksets,roles,etc ,, in this case my folder) right click add all objects to tansport package
    6)Click on export button
    7)Click on start export button
    8)Download the export file using downlaod export file link
    9)Save on your desktop
    Now login into production server or quality server
    Now importing the object inot quality server.
    1)Go to system administartor->tansport->transport package-> import
    2)Source for package file as client. click on browse and and select the .epa file which u have saved on to desktop (i.e from 9 step from above)
    3)Click on upload
    4)Select content to be overwritten as all and click on import
    5)You get a message a import successful.
    To check the object are present in your quality server or productin server
    Go to the content administartor->portal content and check u r folder
    try out this thread .
    transfering objects from Prod to Dev
    rewards point.

  • About transport mechanism

    In my company, If i developed a program, I have to transport to QAS environment to perform UAT, after the program satisfy, then transport to PRD. The program is when i create a complexity program, will will involved create add-on table, dialog program and so on, then transport QAS to perform UAT, if the program has somethings wrong, I need to modify it in DEV environment. After long long time, many transport requests are created. Then the UAT pass, transport to PRD, since there are many transport request are there, some time, I will forget which transport request should be transported, finally, the program caused runtime error after transport to PRD, because one the request forget transport. I would like how to prevent this issue. Any mechanism should i do or any policy should i use. Thanks!

    Hi,
    Go to se09, create "Transport of copies".
    click on Transport Request and click on button "Include Object".
    Click on Radio button "Object list from multiple Request".
    Select all request pertaining to your object changes.
    Press Merge.
    All objects in all request you have mentioned will be merged in one request.
    Now, Right click on Transport Request and "Sort and Compress". This will merge all similar object and remove redundant entries. Also this will take care of keeping latest version.
    Regards,
    Mohaiyuddin

  • Transport mechanism?

    hi,
    can any one send me step-by-step method to transport mech in xi using file level and cms level

    Hi,
    Check below links,
    http://help.sap.com/saphelp_nw2004s/helpdata/en/93/a3a74046033913e10000000a155106/frameset.htm
    http://help.sap.com/saphelp_nw2004s/helpdata/en/a8/5e56006c17e748a68bb3843ed5aab8/frameset.htm
    How to handle SLD for Tranporting Dev to Quality ser
    https://service.sap.com/~sapdownload/011000358700001684302005E/HowToSLDandXI.pdf
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/0fa2c490-0201-0010-61b4-df12869c4753
    Transporting XI from DEV to QA
    Transporting XI from DEV to QA
    using CMS system. in XI
    1. /people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation
    2. /people/sap.india5/blog/2005/11/09/xi-software-logistics-ii-overview
    3. /people/sap.india5/blog/2005/11/28/xi-software-logistics-solution-iii-cms
    4. /people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi --> Overview of Transition from Dev to QA in XI
    5. /people/sravya.talanki2/blog/2005/12/20/inconsistencies-while-transporting-rfc-objects-from-dev-to-qa-150-sp12
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/9e76e511-0d01-0010-5c9d-9f768d644808
    http://help.sap.com/saphelp_nw2004s/helpdata/en/93/a3a74046033913e10000000a155106/content.htm --> Transporting XI Objects
    http://help.sap.com/saphelp_nw04/helpdata/en/ef/a21e3e0987760be10000000a114084/content  .htm --> Configuring Groups and Transport Targets
    Look into this blog for how to export / improt IR and ID objects,
    /people/sap.india5/blog/2005/11/09/xi-software-logistics-ii-overview
    /people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation
    Please go through these links which actualy show you how to configure CMS and also gives you all information regarding it.
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/43f5d790-0201-0010-2984-ff72d822b109
    http://help.sap.com/saphelp_nw04/helpdata/en/de/a4214174abef23e10000000a155106/content.htm
    /people/daniel.wirbser/blog/2005/10/27/tcsfilecreateexception--error-while-assembly-of-software-components-in-nwdi
    http://help.sap.com/saphelp_nw04/helpdata/en/f6/719a2172f74b67b150612a7cd3b7df/content.htm
    http://www.sap-hefte.de/download/dateien/964/074_lesesprobe.pdf
    Here are some blogs.
    /people/sravya.talanki2/blog/2005/11/02/overview-of-transition-from-dev-to-qa-in-xi
    /people/sap.india5/blog/2005/11/03/xi-software-logistics-1-sld-preparation
    Re: Moving project from Dev to QA
    Error while exporting/transporting the Business system from Dev to Quality
    Transporting the scenario frm Dev Server to PRD Server
    transporting data from Dev to quality  using CMS
    Regards,
    phani
    Reward points if Helpful

  • Automatic Transport Mechanism to four systems in same landscape

    Hi,
    We have come across a requirement where we need to transport a request to four systems instead of traditional three.
    The systems involved are - DEV (Development), QAS (Quality), PRD (Production) and TRG Training).
    Currently the transport route is setup for three systems and we need to add the fourth one - Training system. The solution we are looking for is once the request is imported in Production it should be imported automatically in Training system, without any manual intervention.
    The version being used in ERP 5.0.
    Any input in this reagrd is much appreciated.
    Regards,
    Rajeev

    Hi,
    You can configure the transport route accordingly
    Then Click on the system where you want to schedule the auto import job (Training System ). Once you are in the import queue of that system (Tranining ), click on import all request (Big truck). After choose option - at start time and give a period say from today 7 AM and then choose the period option like (every 15 mins) and save this. It will release a periodic job running every 15 mins in your system with the name TMS_00000000XXTMS_TP_IMPORT.

  • What is the transport mechanism in OWB?

    Dear all,
    We will be using OWB to control the Transportable tablespace process from a "Reporting Mirror" of the E-Business Suite to a Data Warehouse.
    The underlying partitions we will be moving are stored on ASM.
    Am I correct in thinking that OWB, behind the scenes, will be using the DBMS_FILE_TRANSFER utility to copy the partitions from source to target?
    (ftp does appear to be a clear option within OWB but we don't want to use this)
    Many thanks,
    Barry
    Barry Andersen | Technical Architect | +44.7917.265217
    Oracle Technical Architecture Consulting
    Oracle Parkway, Thames Valley Park, Reading. RG6 1RA

    You have an oldschool options aswell:
    Connect as SYS DBA with CONNECT / AS SYSDBA command.
    Shutdown the database instance with SHUTDOWN command.
    Rename or/and move the datafiles at operating system level.
    Start Oracle database in mount state with STARTUP MOUNT command.
    Modify the name or location of datafiles in Oracle data dictionary using following command syntax:
    ALTER DATABASE RENAME FILE ‘<fully qualified path to original data file name>’ TO ‘<new or original fully qualified path to new or original data file name>’;
    Open Oracle database instance completely with ALTER DATABASE OPEN command.
    If the datafiles that need to be changed or moved do not belong to SYSTEM tablespaces, and do not contain active rollback segments or temporary segments, there is another workaround that does not require database instance to be shutdown. Instead, only the particular tablespace that contains the date files is taken offline.
    Login to SQLPlus.
    Connect as SYS DBA with CONNECT / AS SYSDBA command.
    Make offline the affected tablespace with ALTER TABLESPACE <tablespace name> OFFLINE; command.
    Modify the name or location of datafiles in Oracle data dictionary using following command syntax:
    ALTER TABLESPACE <tablespace name> RENAME DATAFILE ‘<fully qualified path to original data file name>’ TO ‘<new or original fully qualified path to new or original data file name>’;
    Bring the tablespace online again with ALTER TABLESPACE alter tablespace <tablespace name> ONLINE; command.

Maybe you are looking for