NWDI import of sca files repository error

Hi,
When I am importing SCA files. I am getting following message.Please help me.
SAP_JTECHS
20081202184915 Info   :Starting Step Repository-import at 2008-12-02 18:49:15.0396 -5:00
20081202184915 Info   :Component:sap.com/SAP_JTECHS
20081202184915 Info   :Version  :SAP AG.20080216073957
20081202184915 Info   :1. propagation request is of type TCSSoftwareComponent
20081202184915 Info   :Sources will not be imported for this SC
20081202184915 Info   :Step Repository-import ended with result 'not needed' at 2008-12-02 18:49:15.0396 -5:00
SAP_BUILDT
20081202184221 Info   :Starting Step Repository-import at 2008-12-02 18:42:21.0146 -5:00
20081202184221 Info   :Component:sap.com/SAP_BUILDT
20081202184221 Info   :Version  :SAP AG.20080216005300
20081202184221 Info   :1. propagation request is of type TCSSoftwareComponent
20081202184221 Info   :Sources will not be imported for this SC
20081202184221 Info   :Step Repository-import ended with result 'not needed' at 2008-12-02 18:42:21.0146 -5:00
SAPPCUI_GP
20081202185133 Info   :Starting Step Repository-import at 2008-12-02 18:51:33.0735 -5:00
20081202185133 Info   :Component:sap.com/SAPPCUI_GP
20081202185133 Info   :Version  :MAIN_ERP53PAT_C.20080709102623
20081202185133 Info   :1. propagation request is of type TCSSoftwareComponent
20081202185133 Info   :Sources will not be imported for this SC
20081202185133 Info   :Step Repository-import ended with result 'not needed' at 2008-12-02 18:51:33.0750 -5:00
SAP_ESS
20081202185713 Info   :Starting Step Repository-import at 2008-12-02 18:57:13.0511 -5:00
20081202185713 Info   :Component:sap.com/SAP_ESS
20081202185713 Info   :Version  :MAIN_ERP53VAL_C.20080605130151
20081202185713 Info   :1. propagation request is of type TCSSoftwareComponent
20081202185825 Info   :Propagatable:<a href="http://SAP-PORTALDEV:50000/dtr/system-tools/reports/ResourceDetails?resourceID=ac445ae8331a11ddbdec0030057116fe&path=&command=Show" target="_blank">ac445ae8331a11ddbdec0030057116fe</a> exists allready in the repository. No import necessary.

Looks OK. This is not the first time you importing these SCs, correct?
Slava

Similar Messages

  • Error while importing ESS.sca file in Development tab.

    Hi,
    we are importing the ESS.sca file development tab. we are getting the below error.
    Fatal   Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: VcmFailureException received: HTTP protocol error [cause: Parsing of the response body failed [reason: XMLParser: > expected to close empty element (:main:, row:1, col:3541811)]]:
    please give your sugesstions.
    Regards,
    srinivas,

    Hi Srinivas,
    Try this out. I had a similar problem and i did this to make the import successful.
    1)     Go to usr/sap/J2E/JTrans/archives and copy the sca file with version shown like the above screen shot.
    2)     Unzip the entire sca file by renaming it. In the META-INF folder open the SAP_MANIFEST.MF file and the replace the 32 character guid for the field “'pr_dtrwspropagationlistid'”
    3)     Change it to a different value and save it.
    4)     There will be four folders when the sca file was unzipped. Select all the 4 folders and then zip it again to the original name of the sca file.
    5)     Copy this file and then place it in the path usr/sap/J2E/JTrans/archives.
    6)     Now try re-importing the file it should work.
    Hope this helps,
    Regards,
    Nagarajan.

  • Sca file dependencies error

    Hi ,
    I have installed the SAP netwaever 7.3 which got installed sucessfully.
    But the portal part did not ahve the "Content Administatrion" stuff.
    So i could not create the PCD roles not could i view the existing ones.
    Then i went to the support package and patches
    SAP NetWeaver and complementary products" SAP NetWeaver" SAP NETWEAVER 7.3 ==>Enterprise portal.
    And downlaoded all the SP0 packages ,but while deployin using the JSPM i go the errors:
    one of them is
    Details message(s): Archive
    Netweaver\sapmnt\trans\EPS\in\LMPORTAL00_0-10008053.SCA for component sap.com/LM-PORTAL was admitted for deployment Deployment of archive
    Netweaver\sapmnt\trans\EPS\in\LMPORTAL00_0-10008053.SCA --> sap.comtclmctcconfscpa.sda for component sap.com/tclmctcconfscpa is rejected because it does not pass the validation check. Detailed message: 1. Unresolved dependencies: sap.com/tckmconfigsrv not found in the admitted batch items and the repository Deployment of archive
    Netweaver\sapmnt\trans\EPS\in\LMPORTAL00_0-10008053.SCA --> sap.comtclmctccpakmc_sda.sda for component sap.com/tclmctccpakmc_sda is rejected because it does not pass the validation check. Detailed message: 1. Unresolved dependencies: sap.com/tckmconfigsrv not found in the admitted batch items and the repository
    How should i go about this.
    How to find the dependencies of particular sca file.
    Best REgards
    Manoj

    Hi Amit,
    If i am not mistaken the thread applies for solution manager.
    Will that work for Netweaver 7.3.
    One more thing which i noticed while downlaoding the SCA files for Enterprise Portal was
    I could download for all components except one i.e the EP Runtime 7.30
    SAP NetWeaver and complementary products" ==>SAP NetWeaver"==> SAP NETWEAVER 7.3==>" Entry by Component" Enterprise Portal
    Download basket request for update has been processed. Total number of objects added to Download Basket and require approval 1 . 
    Why is it coming only for this component .
    How should i resolve it.
    Best Regards
    Manoj

  • OWB import fails with corrupted repository error

    Hi,
    Please anyone can suggest a solution for the below problem. I am trying to import set of changes done in development through a Colllection into acceptance. But it keeps failing due to the 'Corrupted Repository' error.
    The OWB Version is OWB 11.1.0.7 which is upgraded version (from 11.1.0.6). I have also compared the SAP_FTP and Background values which are same (10007) on PROPERTYDEFINITION_V.
    Also we have run the repository clean up scripts which reported no issues. But still the error is reported. Please help.
    Please find the error reported.
    Corrupted repository: property
    CMPPurePhysicalObject@b63f4c/id=1398949/owningFCO=1398829/proxyFor=(CMPPurePhysi
    calObjectGen@f5c621/id=1398949/stname=DataEntityKeys/pname=JOU_JOU_FK/lname=DATA
    ENTITY.KEYS/status=DIRTY_PROP_ONLY/committed=true/persistent=true/propsLoaded=tr
    ue) exists when adding
    CMPPurePhysicalObject@d17ed9/id=1598399/owningFCO=1398829/proxyFor=(CMPPurePhysi
    calObjectGen@1df0a37/id=1598399/stname=null/pname=JOU_JOUM2_FK/lname=DATAENTITY.
    KEYS/status=NEW/committed=false/persistent=true/propsLoaded=false)
    Thanks,
    Lee.

    Good morning,
    When importing MDL file you should have an log file generated. This log file is usually in the same directory as your *.mdl unless specified differently. In the error you posted there is a JOU_JOU_FK and I think this is the corruption. Find the mapping using this table associated to this JOU_JOU_FK and drop the mapping first. Check the log generated from the import it may specify the mapping to drop.
    I import my (collection) mdl's with TCL scripts and I generate errors log or completion log. This way I can track my deployment to other environment and see if all mappings were deployed and compiled properly. The first part of the log mentions if the MDL imported properly then I performs a validate on it. If i received and error during import the log will list the mapping.
    example: Error at line 8,624: MDL1261: Error importing MAPPING .....
    Sometimes if I have many mappings to drop. I may receive an error log and have to include the mapping to be dropped in my TCL script.

  • KM File Repository Error-Canonical Path

    Hi
    We are trying to configure a File repository manager.
    In Component Monitor we are getting Error for That repository  as  Startup Error:  getting mapped math - Canonical path not available for "Folder Name"
    And the Trace log is giving error as follows:
    java.io.IOException: Canonical path not available for "folder Name"
    Any clue>
    Deepti

    Hi Deepti
    Try to double check username and password. And take a look at these threads:
    Startup Error:  folder Root has no canonical
    cm repository error: folder has no canonical file
    Startup Error in CM repository in fsdb mode
    Best regards,
    Martin

  • File Repository Error

    Hi experts,
    I have created a file repository, and i have also mapped the drive but when i check the file repository in System Administrator->content monitoring->repository manager, the status is red.
    Could any one help in solving the problem.
    Thanks and regards
    Sivaprasath

    Hi experts,
    Thank you all for your immediate replay.
    I have checked the port also.
    These are the parameters that I have given
    Description         :   KM Test Repository
    Prefix                 :   /Knowledge Base
    Active                 :   checked
    Lookup Mode      : caseless
    Root Directory     : x/
    Security Manager: AclSecurity Manager
    Thanks and regards
    Sivaprasath

  • JSP import Statement importing a Class File giving ERROR

    Hey guys,
    There is a problem to which I dont know the reason,
    Consider the code below:
    <%@ import Converter, ConverterHome %>
    It gives me a Compile Time error of this type:
    '.' Required in import Converter ;
    but when i put these classes in a package suppose "converter"
    and the above import statement like this :
    <%@ import converter.Converter,converter.ConverterHome%>
    It gives me no error
    So whats the reason behind this? Cant I compile a JSP program by refrencing classes without in any package?
    please Reply
    Thanks in advance..

    So whats the reason behind this?
    Cant I compile a JSP program by refrencing classes without in any package?No, I do not beleive you can, is you are using Java 1.4. In 1.4, you can only reference classes in the Default Package (none) from other classes in the default package. If you are in a package, then you can not import from the default package. And this is for ALL java classes, not just JSP and Serlets. Since the JSP servlet would be part of a package (which depends on the server you are using) you will need to put your classes into packages to import them...

  • Error while importing .SCA files in track

    Hi Folks,
    I tried importing following .SCA files into a nwdi track but it Finished with Errors.
    ENGFACADE
    ENGINEAPI
    FRAMEWORK
    WD-RUNTIME
    By logs i got information that
    'File is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    Note: I am trying to setup nwdi track for CE developments and following this  [Document|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/7014086d-3fd9-2910-80bd-be3417810c6f?quicklink=index&overridelayout=true]
    Following .SCA files are imported successfully
    SAPBUILDT
    SAPJEE
    SAPJTECHS
    Please help me to resolve this issue.
    Thanks in anticipation.
    Mandeep Virk

    Hi John,
    Following are the log details
    20100309050525 Info   :Starting Step CBS-make at 2010-03-09 05:05:25.0359 -6:00
    20100309050526 Info   :wait until CBS queue of buildspace D01_Demo_D is completely processed, before starting the import
    20100309050526 Info   :CBS queue of buildspace D01_Demo_D is completely processed. Starting the import now.
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/base.tools.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/com.sap.base.technology.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/deploy.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/engine.j2ee14.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/engine.lm.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/engine.migration.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcbljcoapi.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcblvsiapi.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcjeappconfigurationapi.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcjecrossapi.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcjewebcontainerpublic~api.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcjewebservicesapi.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG20080202122500/DEPLOYARCHIVES/tcjewebserviceslib.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :deploy archive /usr/sap/JTrans/CMS/extract/201003091105190928_sap.comENGFACADESAP AG~20080202122500/DEPLOYARCHIVES/webservices.lib.facade.sda is not added to build request, because associated SC is marked with the 'non nwdi deployment flag'
    20100309050611 Info   :=================================================================
    20100309050611 Info   :buildspace = D01_Demo_D   build request id = 23
    20100309050611 Info   :wait until CBS queue of buildspace D01_Demo_D is completely processed, before asking for build results
    20100309050611 Info   :waiting for CBS queue activity
    20100309050641 Info   :build process already running: waiting for another period of 30000 ms
    20100309050641 Info   :CBS queue of buildspace D01_Demo_D is completely processed. Asking for build results now.
    20100309050641 Fatal  :processing of build request is not finished successfully, final status is:FAILED (more details in CBS log )
    20100309050641 Info   :no confirmation of request 23 because the status is not 'succeeded'
    20100309050641 Info   :=================================================================
    20100309050641 Info   :Remove software component ENGFACADE from further processing, because archive import failed
    20100309050641 Info   :Step CBS-make ended with result 'error' at 2010-03-09 05:06:41.0702 -6:00
    - Mandeep Virk

  • Error while importing sca file in local development

    Hi,
    I am trying to import a sca file (MDMJ71006_0-10006189.SCA) into the local development of my NWDS.
    I right click on local development--> Import SC --> Gave path of SC --> Next (All DCs gets displayed) --> Finish.
    After clicking finish I am getting error like:
    UI job failed with exception: Updating DC model for com.sap.mdm.tech.connector java.lang.NullPointerException
    After this i can see this SC in my local development list but when I update it, the SC gets deleted.
    Can anyone help me import this sca file.
    Thanks
    Arjun

    Hi,
    I am trying to import a sca file (MDMJ71006_0-10006189.SCA) into the local development of my NWDS.
    I right click on local development--> Import SC --> Gave path of SC --> Next (All DCs gets displayed) --> Finish.
    After clicking finish I am getting error like:
    UI job failed with exception: Updating DC model for com.sap.mdm.tech.connector java.lang.NullPointerException
    After this i can see this SC in my local development list but when I update it, the SC gets deleted.
    Can anyone help me import this sca file.
    Thanks
    Arjun

  • Import SCA files in Development Tab of the Transport Studio take more time

    Hi,
    After Check-In files in the Transport Studio, the import of SCA files starts in the development Tab of the Transport Studio.
    The import takes more time. Why this happens?
    Am I missing any configuration? Please specify in detail.
    Thanks in Advance,
    Sathya

    SC: sap.com_SAP-JEE:
    SDM-deploy
    Returncode : Not executed.
    How to check the username, password and url for SDM?
    Log file of Repository-import:
    Info:Starting Step Repository-import at 2009-10-13 22:15:49.0484 +5:00
    Info:Component:sap.com/SAP_JTECHS
    Info:Version  :SAP AG.20060119105400
    Info:3. PR is of type TCSSoftwareComponent
    Info:Component:sap.com/SAP_BUILDT
    Info:Version  :SAP AG.20060411165600
    Info:2. PR is of type TCSSoftwareComponent
    Info:Component:sap.com/SAP-JEE
    Info:Version  :SAP AG.20060119105300
    Info:1. PR is of type TCSSoftwareComponent
    Info:Step Repository-import ended with result 'not needed' at 2009-10-13 22:15:49.0500 +5:00
    Log File of CBS-make :
    Import got failed.
    Info:build process already running: waiting for another period of 30000 ms
    Info:no changes on the CBS request queue (DM0_DEMObp1_D) after a waiting time of 14430000 ms
    Fatal:The request queue is not processed by the CBS during the given time intervall => TCS cannot import the request because queue is not empty
    Fatal:There seems to be a structural problem in the NWDI. Please look after the operational status of the CBS.
    Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: The request queue is not processed during the given time intervall. There seems to be a structural problem in the NWDI. Please look after the operational status of the CBS.:communication error: The request queue is not processed during the given time intervall. There seems to be a structural problem in the NWDI. Please look after the operational status of the CBS.
    com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: The request queue is not processed during the given time intervall. There seems to be a structural problem in the NWDI. Please look after the operational status of the CBS.
         at com.sap.cms.tcs.client.CBSCommunicator.importRequest(CBSCommunicator.java:369)
         at com.sap.cms.tcs.core.CbsMakeTask.processMake(CbsMakeTask.java:120)
         at com.sap.cms.tcs.core.CbsMakeTask.process(CbsMakeTask.java:347)
         at com.sap.cms.tcs.process.ProcessStep.processStep(ProcessStep.java:77)
         at com.sap.cms.tcs.process.ProcessStarter.process(ProcessStarter.java:179)
         at com.sap.cms.tcs.core.TCSManager.importPropagationRequests(TCSManager.java:376)
         at com.sap.cms.pcs.transport.importazione.ImportManager.importazione(ImportManager.java:216)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.execImport(ImportQueueHandler.java:585)
         at com.sap.cms.pcs.transport.importazione.ImportQueueHandler.startImport(ImportQueueHandler.java:101)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:583)
         at com.sap.cms.pcs.transport.proxy.CmsTransportProxyBean.startImport(CmsTransportProxyBean.java:559)
         at com.sap.cms.pcs.transport.proxy.LocalCmsTransportProxyLocalObjectImpl0.startImport(LocalCmsTransportProxyLocalObjectImpl0.java:1736)
         at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1169)
         at com.sap.cms.ui.wl.wdp.InternalCustom1.importQueue(InternalCustom1.java:2162)
         at com.sap.cms.ui.wl.Worklist.onActionImportQueue(Worklist.java:880)
         at com.sap.cms.ui.wl.wdp.InternalWorklist.wdInvokeEventHandler(InternalWorklist.java:2338)
         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:422)
         at com.sap.tc.webdynpro.clientserver.window.WindowPhaseModel.processRequest(WindowPhaseModel.java:133)
         at com.sap.tc.webdynpro.clientserver.window.WebDynproWindow.processRequest(WebDynproWindow.java:344)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:143)
         at com.sap.tc.webdynpro.clientserver.session.ApplicationSession.doProcessing(ApplicationSession.java:298)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessingStandalone(ClientSession.java:705)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doApplicationProcessing(ClientSession.java:659)
         at com.sap.tc.webdynpro.clientserver.session.ClientSession.doProcessing(ClientSession.java:227)
         at com.sap.tc.webdynpro.clientserver.session.RequestManager.doProcessing(RequestManager.java:150)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:56)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:47)
         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)
    Info:Step CBS-make ended with result 'fatal error' ,stopping execution at 2009-10-14 02:16:28.0296 +5:00

  • Problems importing SCA files

    Hi
    I imported several SCA files and I openned their DCs at NWDS but several DCs are missed.
    An example is the DCs with Struts... I addeded its SCA but its DCs haven´t been imported at NWDS.
    STRUTS01_0-10003646.SCA is a pack of DCs to be used as a dependence, isn´t it ?
    so.. how can I add this in order to solve this dependences :
    12/02/2009 11:05:05 /userOut/Development Component (com.sap.ide.eclipse.component.provider.actions.dc.UsedDCFoundHandlerBase) [Thread[ModalContext,5,main]] ERROR: failed to resolve reference "sap.com/struts/lang" for DC "sap.com_SAP-SHRWEB_1:sap.com/crm/isa/web/b2b":Cannot find compartment of used component: sap.com:struts/lang
    Edited by: Michel Dambros Figueiredo - BR on Feb 12, 2009 8:51 PM

    Hi Michel,
                    May i know the business package you are going to implement. As of my knowledge for E-Commerce implementaion we will use this Struts.SCA file as an dependency(means just we need to add the SCA file to the related dependency).
    you will not get Struts.sca file into ur NWDS.
    In ur track just maintain SCA files which is related to ur business package source and add the dependencis for those source files.
    just add
    CUSTCRMPRJ,SHRWEB,SHRAPP,CRMWEB,CRMAPP to the track and remaing all as there depencdencies.
    Regards,
    Anil.

  • "File Repository Server error" when trying to commit a new CrystalEnterprise.Program instance to the InfoStore

    I've run into an issue where saving a new CrystalEnterprise.Program instance is throwing an ambiguous exception with no other information than a generic HRESULT code and the even less useful error message "File Repository Server error". I've debugged the code using the COMException managed debugging assistant and Reflector to get to the callsite of the COM object, but there is nothing there to indicate what the actual File Repository error is attributed to. Logging for the InputFileRepository service in the CMS was been set to HIGH, but nothing shows there as a result of my code executing.
    The call to myInfoStore.Commit(...) is where the COMException is thrown.
        protected void CreateProgramObject(InfoStore infoStore)
            using(PluginManager pluginManager = infoStore.PluginManager)
                using(InfoObjects newCollection = infoStore.NewInfoObjectCollection())
                    using(PluginInfo programPlugin = pluginManager.GetPluginInfo("CrystalEnterprise.Program"))
                        using(Program tempProg = (Program)newCollection.Add(programPlugin))
                            const string USER_FOLDER_QUERY =
                                "Select SI_ID From CI_INFOOBJECTS Where SI_NAME = '[email protected]'";
                            using(InfoObjects folders = infoStore.Query(USER_FOLDER_QUERY))
                                if(folders.Count < 1)
                                    Response.Write("No user folder was found!");
                                    return;
                                using(InfoObject userReportFolder = folders[1])
                                    tempProg.Title = "Scheduled File";
                                    tempProg.Description = "My new program";
                                    tempProg.ParentID = userReportFolder.ID;
                                    tempProg.ProgramType = CeProgramType.ceScript;
                                    tempProg.Files.Add(@"E:\sample.bat");
                                    try
                                        infoStore.Commit(newCollection);
                                    catch(SystemException snx)
                                       Trace.Write(snx.ToString());
    Has anyone run into this issue and found a resolution?

    Thank you for the reply. I changed the file path on the BOE Server to match the path I'm using in the Files.Add(...) call. At least now I get a different error message, but it's still not enough to resolve the issue. The message is "File Repository Server error : File system operation for D:\Scripts\test.bat on File Repository Server failed.  If the problem persists, please contact your system administrator for event log information." I verified the service account the SIA service runs under can access that path, but still no luck.
    Using a UNC path resulted in the original "File Repository Server error" message in the Exception.

  • CBS - Make Failed for SAP_ESS.sca file

    Hi All,
    We are trying to implement ESS package in NWDI. All the steps for installation and configuration are done. while importing the sca files in the development tab all the sca file like Jtechs, JEE, Buildt, PCUI are imported successfully.
    But SAP_ESS sca file alone is failing. when  i went through the log it says repository-import has been finished successfully. But the second step CBS it is failing. When i went through the log it says....
    Info:Starting Step CBS-make at 2007-02-26 17:43:05.0671 +5:00
    Info:wait until CBS queue of buildspace EPD_ESSTrack_D is completely processed, before starting the import
    Info:waiting for CBS queue activity
    Info:build process already running: waiting for another period of 30000 ms (1)
    Info:build process already running: waiting for another period of 30000 ms (2).....
    When i went through the CBS log the following is the erroe that i received.
    Integrate activities into active workspace(s)...
         Integration of activities in compartment "sap.com_SAP_ESS_1" started at 2006-09-30 07:16:40.703 GMT
         Integration of 1 activities in compartment "sap.com_SAP_ESS_1" finished at 2006-09-30 07:21:08.875 GMT and took 4 m 28 s 172 ms
    An incomplete integration in compartment "sap.com_SAP_ESS_1" of buildspace "EPC_ESSTRACK_D" has resulted because of errors during request processing!
    Request 169 has been created to re-initialize the compartment
    ===== Post-Processing =====  finished at 2006-09-30 07:21:09.140 GMT and took 6 m 47 s 859 ms
    Change request state from SUCCEEDED to FAILED
    ERROR! The following problem(s) occurred  during request processing:
    Communication error when performing integrations. Server error [500 Internal Server Error]. Request FAILED.
    REQUEST PROCESSING finished at 2006-09-30 07:21:19.000 GMT and took 25 m 9 s 500 ms
    I tried restarting the server also checked the CBS properties in Visual Admin. It looks everything is fine.
    Please help me in this regard.
    Thanks,
    Nagarajan.

    Dear Portal gurus,
    I too having the same problem . please provide  me the solution for this.
    how to check the default trace.
    regards
    prasad

  • CE 7.1 Ehp1 SP5 on Oracle 10.2.0.4 Performance - XSS track import of SCAs

    Hi,
    I'm currently building a new track on my newly built CE server which has the NWDI capability configured. I've had a few problems importing the SCA files into the track. I've been getting DTR internal server errors. Looking through the logs I couldn't see a specific reason as per OSS 774339 and the subsequent notes this refers to. After restarting the CE server I've imported the SCA files individually and this has at least enabled me to get the SCA files imported without error.
    The time taken to import is very long - the ESS SCA file (290 MB) took 3.5 hours alone.
    I've read OSS 1361525 which is related to DTR performance with Oracle but the Patch provided is for 7.01 / 7.02 releases of CE.
    I have already patched my CE 7.1 Ehp1 SP5 server with the available patches for DICMS05, DICLIENTS05 & DICBS05* - there is none current available for download for the DIDTR05* CE 7.1 Ehp1 release.
    Can anyone suggest what could be done to reduce the import runtimes ?.
    I'm regularly updating the Oracle Statistics as per OSS 1229080 and the Oracle params have been set as per OSS 830576.
    Regards,
    Brian.

    Hi Ervin,
    1. The NWDI Server is a distributed configuration - the DB instance is on it's own Solaris 10 zone and the central services & instance are on another Solaris zone. Both zones have plenty CPU/Memory resources and the load values on both are low. The systems are not overloaded.
    2. THis is a new build and I'm setting up the first track to enable the customer to start a XSS development project. The first 10 or so SCs imported without error into the track. ESS, MSS & PCUI_GP SCA files are the ones remaining and are failing to import.
    3. Our OS is Solaris 10 on Sun Sparc - so no windows type anti-virus software to contend with.
    4. I've run the statistics a few times over the last day or so :-
    brconnect -u / -c -o summary -f stats -o SAPSR3DB -t all -p 8 -f nocasc
    5. Trace levels are default.
    6. The logs & traces have no OutOfMemory errors as per OSS 1001502. The error received is :-
    20100908171424 Info   :Starting Step CBS-make at 2010-09-08 17:14:24.0632 +1:00
    20100908171425 Info   :wait until CBS queue of buildspace S01_Sandbox_D is completely processed, before starting the import
    20100908171425 Info   :CBS queue of buildspace S01_Sandbox_D is completely processed. Starting the import now.
    20100908181425 Fatal  :CBS throws exception during activation:
    20100908181425 Fatal  :caused by Exception:com.sap.tc.cbs.client.error.CommunicationException: Read timed out (Service call exception; nested exception is:
         java.net.SocketTimeoutException: Read timed out):Read timed out (Service call exception; nested exception is:
         java.net.SocketTimeoutException: Read timed out)
    The interesting thing here is that the error is thrown exactly one hour after the CBS-make operation starts.
    7. We've got Oracle DB.
    Hopefully you'll be able to suggest how best I can resolve the error and continue.
    Also - from the logs there was further error activity for this same import operation 3 hours later after I'd gone home  :-
    #2.#2010 09 08 21:34:50:064#+0100#Info#/Applications/CBS/Service#
    #BC-CTS-CBS#tc.CBS.Service#0021286D058200680000000E000004DB#14060650000000783##com.sap.tc.cbs.server.rt.rq.RequestOrc####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[CBS Request Orc,5,SystemThreadGroup]#Plain##
    Request arranged for processing for BuildSpace S01_Sandbox_D. [bsID:3, rID:62, node:14060650]#
    #2.#2010 09 08 21:34:50:086#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D058200690000006F000004DB#14060650000000783##com.sap.tc.cbs.server.dao.impl.Request####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
    Build number assigned: 67#
    #2.#2010 09 08 21:34:50:088#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000070000004DB#14060650000000783##com.sap.tc.cbs.server.dao.impl.Request####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
    Change request state from QUEUED to PROCESSING#
    #2.#2010 09 08 21:34:50:095#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000071000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
    #2.#2010 09 08 21:34:50:096#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000072000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
    REQUEST PROCESSING started at 2010-09-08 20:34:50.095 GMT#
    #2.#2010 09 08 21:34:50:098#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000073000004DB#14060650000000783##com.sap.tc.cbs.server.proc.RequestHandler####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
        ACTIVATION request in Build Space "S01_Sandbox_D" at Node ID: 14,060,650
            [id: 62; parentID: 0; type: 4]
            [options: IGNORE BROKEN DC, FORCE ACTIVATE PREDECESSORS, FORCE INTEGRATED, IGNORE COMPONENT INTERSECTION]#
    #2.#2010 09 08 21:34:50:149#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000074000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
    #2.#2010 09 08 21:34:50:150#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000075000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
        Waiting for access: 54 ms#
    #2.#2010 09 08 21:34:50:151#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000076000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
    #2.#2010 09 08 21:34:50:151#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000077000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
        ===== Pre-Processing =====  started at 2010-09-08 20:34:50.150 GMT#
    #2.#2010 09 08 21:34:50:152#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000078000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
            List of requested for activation activities:#
    #2.#2010 09 08 21:34:50:184#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000079000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                ''sap.com_SAPPCUI_GP_1'' compartment#
    #2.#2010 09 08 21:34:50:184#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D058200690000007A000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                    CMS_sap.com_SAPPCUI_GP_590_aabfda99de4511d9b84800300530c04f#
    #2.#2010 09 08 21:34:50:185#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D058200690000007B000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                        [ISN 2][created by MAIN at 2010-09-08 17:14:24.0][OID e4fdda79781d11dec2470030057116fe]#
    #2.#2010 09 08 21:34:50:185#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D058200690000007C000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                There is 1 activity in compartment sap.com_SAPPCUI_GP_1#
    #2.#2010 09 08 21:34:50:186#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D058200690000007D000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                1 activity will be processed by this request#
    #2.#2010 09 08 21:34:50:647#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D058200690000007E000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
    #2.#2010 09 08 21:34:50:648#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D058200690000007F000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
            Analyze dependencies to predecessor activities... started at 2010-09-08 20:34:50.647 GMT#
    #2.#2010 09 08 21:34:50:648#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000080000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                Analyzing predecessors in compartment "sap.com_SAPPCUI_GP_1"#
    #2.#2010 09 08 21:34:50:669#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000081000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                    No dependencies to predecessor activities found.#
    #2.#2010 09 08 21:34:50:669#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000082000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
            Analyze dependencies to predecessor activities... finished at 2010-09-08 20:34:50.669 GMT and took 22 ms#
    #2.#2010 09 08 21:34:50:670#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000083000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
    #2.#2010 09 08 21:34:50:670#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000084000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
            Analyze versions... started at 2010-09-08 20:34:50.670 GMT#
    #2.#2010 09 08 21:34:50:712#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000085000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                ===== Pre-Processing =====  finished at 2010-09-08 20:34:50.711 GMT and took 561 ms#
    #2.#2010 09 08 21:34:50:712#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000086000004DB#14060650000000783##com.sap.tc.cbs.server.dao.impl.Request####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                Change request state from PROCESSING to FAILED#
    #2.#2010 09 08 21:34:50:713#+0100#Error#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000087000004DB#14060650000000783##com.sap.tc.cbs.server.proc.RequestHandler####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                Error! The following problem(s) occurred  during request processing:#
    #2.#2010 09 08 21:34:50:713#+0100#Error#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000089000004DB#14060650000000783##com.sap.tc.cbs.server.proc.RequestHandler####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                Error! The following error occurred during request processing:Server error [500 Internal Server Error]#
    #2.#2010 09 08 21:34:50:714#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D058200690000008B000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
            REQUEST PROCESSING finished at 2010-09-08 20:34:50.714 GMT and took 619 ms#
    #2.#2010 09 08 21:34:50:728#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
    #BC-CTS-CBS#tc.CBS.Service#0021286D058200690000008C000004DB#14060650000000783##com.sap.tc.cbs.server.dao.impl.Request####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
    Regards,
    Brian.

  • SolMan CTS+ Best Practices for large WDP Java .SCA files

    As I know, CTS+ allows ABAP change management to steward non-ABAP objects.  With ABAP changes, if you have an issue in QA, you simply create a new Transport and correct the issue, eventually moving both transports to Production (assuming no use of ToC).
    We use ChaRM with CTS+ extensively to transport .SCA files created from NWDI. Some .SCA files can be very large: +300MB. Therefore, if we have an issue with a Java WDP application in QA, I assume we are supposed is to create a second Transport, attach a new .SCA file, and move it to QA. Eventually, this means moving both Transports (same ChaRM Document) to Production, each one having 300 MB files. Is this SAP's best practice, since all Transports should go to Production? We've seen some issues with Production not being to happy with deploying two 300MB files in a row.  What about the fact that .SCA files from the same NWDI track are cumulative, so I truly only need the newest one. Any advice?
    FYI - SAP said this was a consulting question and therefore could not address this in my OSS incident.
    Thanks,
    David

    As I know, CTS+ allows ABAP change management to steward non-ABAP objects.  With ABAP changes, if you have an issue in QA, you simply create a new Transport and correct the issue, eventually moving both transports to Production (assuming no use of ToC).
    We use ChaRM with CTS+ extensively to transport .SCA files created from NWDI. Some .SCA files can be very large: +300MB. Therefore, if we have an issue with a Java WDP application in QA, I assume we are supposed is to create a second Transport, attach a new .SCA file, and move it to QA. Eventually, this means moving both Transports (same ChaRM Document) to Production, each one having 300 MB files. Is this SAP's best practice, since all Transports should go to Production? We've seen some issues with Production not being to happy with deploying two 300MB files in a row.  What about the fact that .SCA files from the same NWDI track are cumulative, so I truly only need the newest one. Any advice?
    FYI - SAP said this was a consulting question and therefore could not address this in my OSS incident.
    Thanks,
    David

Maybe you are looking for