Unable to export or import custom request dataset

Hi,
I am a newbie to OIM, please let me know where I am going wrong with either export or importing the custom request dataset.
Following are the steps which I followed:
1. Modified the weblogic.properties file with required values such as
wls_servername = xxx
application_name=OIMMetadata
metadata_from_loc=D://Oracle//Middleware//Oracle_IDM1//server//metadata//custom
metadata_to_loc=D://Oracle//Middleware//Oracle_IDM1//server//metadata//custom
metadata_files=/**
2. Created the request dataset to provision a user to a resource.
<?xml version="1.0" encoding="UTF-8"?>
<request-data-set xmlns="http://www.oracle.com/schema/oim/request"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.oracle.com/schema/oim/request"
name="Provision ABC Interface" entity="ABC Interface" operation="PROVISION">
<AttributeReference name="User ID"
attr-ref="User ID"
available-in-bulk="false"
type="String"
length="50"
widget="text"
required="true" />
<AttributeReference name="Last Name"
attr-ref="Last Name"
available-in-bulk="false"
type="String"
length="50"
widget="text"
required="true"
mls="false" />
<AttributeReference name="First Name"
attr-ref="First Name"
available-in-bulk="false"
type="String"
length="50"
widget="text"
required="true"
mls="false" />
<AttributeReference name="Email"
attr-ref="Email"
available-in-bulk="false"
type="String"
length="50"
widget="text"
required="true"
mls="false" />
<AttributeReference name="Type"
attr-ref="Type"
available-in-bulk="false"
type="String"
length="50"
widget="dropdown"
lookup-code="Type"
required="true" />
</request-data-set>
3. Placed the request dataset in D://Oracle//Middleware//Oracle_IDM1//server//metadata//custom/ABC
4. OIMMetadata is in Active State.
5. Tried to import the dataset with credentials but failed with the following error:
UserWarning: MDS-91002: MDS Application runtime MBean for "OIMMetadata" is not available. "importMetadata" operation failure.
while importing request datasets
There is no error while starting the OIM server with MBean too.
Could anyone suggest me to resolve this error.
Appreciate your help
Thanks
SG.

Import issue got resolved. Thank you.
Problem is with the case sensitivity of server name in weblogic.properties.
Now am facing other issue. I am not able to see the attributes which i have defined in request dataaset when am creating request template, but, I am able to get the xml file (request dataset) when I am exporting.
Any clue?
Thanks
SG

Similar Messages

  • Customizing request datasets in OIM 11g

    Hi Friends,
    I have couple of questions/issues while customizing request datasets in OIM 11g. Can you please help me?
    1) I gave read-only="true" in my request dataset for one of the attribute, but I was still able to edit that attribute value while raising requests.
    2) I gave hidden="true" in my request dataset for one of the attribute, but I was still able to see that attribute while raising requests.
    3) I have around 90 attributes in my request dataset. Is there any way to display category type and under that category display the attrbitues i.e. just like attributes in user profile.
    4) As I have 90 attributes, I am expecting the format will be like first 45 will be shown in left panel(column) and remaining 45 in right panel (column). Instead of this , it is showing first 70 in left panel and the remaining 20 in right panel which is very ugly to see. Is there any way to show frist 45 on left side and remaining 45 on the right side? Please help me.

    Regarding the first two points:
    1) The read only property applies to the approver only, i.e. approver can read and not modify the attribute. It does not apply to the requester. I don't believe you can configure a read-only attribute in the data set.
    2) If you want to hide an attribute, you can restrict it in your request template.

  • How to export and import customized Object

    Hi All,
    I would like to communicate with system clipboard by importing and exporting the Objects.
    Assume that i have a RectangleBean object containing x,y,width and height properties and respective setters and getters.
    i am drawing the rectangle object by using the RectangleBean object values.
    now i want to export and import the RectangleBean object to system clipbord to draw a rectangle on other window when the user performed paste functionality. In other words communicating the RectangleBean objects between the two windows.
    Thanks in Advance
    Dorairaj M

    DoraiRaj wrote:
    Hi All,
    I would like to communicate with system clipboard by importing and exporting the Objects.
    Assume that i have a RectangleBean object containing x,y,width and height properties and respective setters and getters.
    i am drawing the rectangle object by using the RectangleBean object values.
    now i want to export and import the RectangleBean object to system clipbord to draw a rectangle on other window when the user performed paste functionality. That's not going to work: if you are talking past the bean object into the clipboard and have something like MS-Word use it as a way of recreating your graphic using your bean... no, that's just not going to happen.
    If you are saying you want to create another of your graphics on another Java window in the same JVM session, then just pass a reference of the window's graphic context to a setter and have at it.
    If you're talking about some JEE functionality, then you're going to have to use RMI or some other standard method to get your object over to the other box or it's effects.
    In other words communicating the RectangleBean objects between the two windows.Not by cutting and pasting to the clipboard.

  • Export and Import  transport request between different version?

    Hi,
    I have tried to Export the transport requests from ECC5 to ECC6 via STMS .Its not throughing any error but no Master datas are transported. Anyone have idea about that?

    Hello,
    From my experience SAP didn't recomneded transporting from 46C -> ECC5.
    The structure of tables and objects are a little bit different between different
    releases.
    Dimitry

  • How to export and import custome functions...

    Hi Biddies,
    I am wondering is there any way the custome functions in an existed report can be exported.
    If there is, how can I do it?
    For example,   "Custome Functions.rpt", which was distributed  with Crystal Reports, has a custome function library. How can I export it from the report?
    Thanks
    Edited by: Jonas sun on Mar 18, 2009 7:13 AM

    Hi,
    Did  you try exporting it ?
    What format you are using to export it .
    As I have seen you can export the custom functions contained report.
    I had done it in pdf format for your references go to sample report folder
    select featured example report folder in that open custom function report and export it to pdf format.
    The report will exported with the field data of custom function.
    Is this answer you wanted ? if not please explain me bit further.
    Regards,
    Neo.

  • Uploading Request Datasets

    Hi,
    I have a problem to change the Dataset of a request for a provision resource.
    I import the xml with the changes and run the PurchCache but the form of the request does not change.
    Note: The import was done properly because I checked in the database.
    What should I do?

    I am not sure if this will help, but request datasets can be imported both through metadata upload and the deployment manager. One thing you could perhaps try, if you are so far importing through metadata upload, is to do :
    1) First export the request dataset via the deployment manager, and validate if this is the old or new dataset.
    2) If the exported XML has the old dataset, update this file to replace the old dataset with the new one.
    3) Import the request dataset (containing the new dataset) via the deployment manager. This may help even if you did not have to make a change at step 2 as sometimes importing triggers additional processes you may not be aware of.

  • Unable to Export/Import between different CPS Enviornments( Test& QAS)

    HI all,
    i am facing some issues while doing export and import of Objects from one CPS host to another host.
    I did see another thread mentioning the same but stilll was not clear.
    I am trying to Export Application from one host to another host.
    My Case:
    Steps taken to Export:
    >selected SAP System in Application under SAP and do Export Tree . and Export is successfull. Copied the *.car file localy to desktop.
    I go to another CPS host and do Import Rule Set . I dont put any rule there but just submitt the Jobs. It asks to Upload the file to server. give path to *.car file , Once done. Import Job Runs but goes to error status.
    I have attached the logs.
    ERROR 2011-07-22 15:31:40,977 Africa/Harare [Redwood Job Thread Pool: GLOBAL.System.System worker 0] job.System_Import_Archive.2835 - Import failed, no objects have been imported.
    -- JOB RUN STACK TRACE --
    JCS-113051: Exception while parsing source jar:file:/C:/usr/sap/QRP/JC00/j2ee/cluster/server0/scheduler/JOB_2835carin.car.car!/SAPSystem/GLOBAL.QSR.xml at line 22: JCS-113004: No such field LoadThreshold on object type SAPSystem. See cause for further information
         at com.redwood.scheduler.model.imprt.BaseImporter.importObject(BaseImporter.java:297)
         at com.redwood.scheduler.model.imprt.ImportScanner.importObject(ImportScanner.java:52)
         at com.redwood.scheduler.model.imprt.BaseImporter.importObject(BaseImporter.java:185)
         at com.redwood.scheduler.model.imprt.CronacleArchiveReader.scanArchive(CronacleArchiveReader.java:111)
         at com.redwood.scheduler.model.imprt.CronacleArchiveReader.importAll(CronacleArchiveReader.java:84)
         at com.redwood.scheduler.system.jobs.CronacleArchiveImport.runInternal(CronacleArchiveImport.java:396)
         at com.redwood.scheduler.system.jobs.CronacleArchiveImport.run(CronacleArchiveImport.java:192)
         at com.redwood.scheduler.system.jobs.CommonSystemJob.execute(CommonSystemJob.java:53)
         at com.redwood.scheduler.systemjobservice.impl.JobWorker.doWork(JobWorker.java:242)
         at com.redwood.scheduler.infrastructure.workqueue.Worker.run(Worker.java:74)
    I do feel i have to use import Rule . But what feild do i need to include to replace with as per new host.
    Seconldy when i try to export EVENTS. I am able to do successfully. by giving an export rule for specfic events.
    But when i import it ,, i get in issues.
    Error Log:
    INFO  2011-07-22 10:06:24,091 Africa/Harare [Redwood Job Thread Pool: GLOBAL.System.System worker 0] job.System_Import_Archive.2685 - Starting to import all definitions from archive.
    INFO  2011-07-22 10:06:24,163 Africa/Harare [Redwood Job Thread Pool: GLOBAL.System.System worker 0] job.System_Import_Archive.2685 - Scanning : jar:file:/C:/usr/sap/QRP/JC00/j2ee/cluster/server0/scheduler/JOB_2685carin.car.car!/EventDefinition/GLOBAL.QFS_Detect_Z_C6_ABSA_119020.xml
    ERROR 2011-07-22 10:06:24,662 Africa/Harare [Redwood Job Thread Pool: GLOBAL.System.System worker 0] job.System_Import_Archive.2685 - Unable to parse input source: jar:file:/C:/usr/sap/QRP/JC00/j2ee/cluster/server0/scheduler/JOB_2685carin.car.car!/EventDefinition/GLOBAL.QFS_Detect_Z_C6_ABSA_119020.xml line 9
    I guess iagain i should be using import rule correctly.
    what feilds should i be replacing in import rule. is it going to be Application ( as feild ) or partition or anything else..
    Please advise if i am doing something worng.
    Thank You
    Deepak

    Hi ,
    There was version mismatch between Target CPS host and Sources CPS Host.
    I bought the Sources CPS host version same as Target CPS version (.Build: M33.21-49924 ). But stil when i do the Applciation Export from sourcs CPS to Target CPS i am still receiving same error as  below:
    INFO  2011-07-25 10:12:37,009 Africa/Harare [Redwood Job Thread Pool: GLOBAL.System.System worker 0] job.System_Import_Archive.3913 - Starting to import all definitions from archive.
    INFO  2011-07-25 10:12:37,055 Africa/Harare [Redwood Job Thread Pool: GLOBAL.System.System worker 0] job.System_Import_Archive.3913 - Scanning : jar:file:/C:/usr/sap/QRP/JC00/j2ee/cluster/server0/scheduler/JOB_3913carin.car.car!/JobDefinition/GLOBAL.Z_SRM-220_I_POW_UPD_ERP_DAT_POWL.xml
    INFO  2011-07-25 10:12:37,057 Africa/Harare [Redwood Job Thread Pool: GLOBAL.System.System worker 0] job.System_Import_Archive.3913 - Scanning : jar:file:/C:/usr/sap/QRP/JC00/j2ee/cluster/server0/scheduler/JOB_3913carin.car.car!/Application/GLOBAL.ESKOM_QUALITY_SRM_SYSTEM.xml
    ERROR 2011-07-25 10:12:37,069 Africa/Harare [Redwood Job Thread Pool: GLOBAL.System.System worker 0] job.System_Import_Archive.3913 - Unable to parse input source: jar:file:/C:/usr/sap/QRP/JC00/j2ee/cluster/server0/scheduler/JOB_3913carin.car.car!/Application/GLOBAL.ESKOM_QUALITY_SRM_SYSTEM.xml line 7
    JCS-113007: Cannot set field User/Role on Grant on Application <Name Not Set> to <Grantee Subject Not Set>:<Grantee Subject Not Set> to Subject:Role.Everyone
    Please advice.
    Regards
    Deepak

  • Unable to create a customizing request to transport BPC10 content to Quality

    Hi
    Unable to create a customizing request to transport BPC10 content to Quality .
    From the transport connections tab, i am selecting the required objects and then clicking the transport truck but it does not pop up and ask for a transport request .
    So please provide any solution.

    Hi,
    Check whether Standard transport switched-on is enabled or not. To get transport request your setting should be as follows : RSA1-->Transport Connection-->Edit-->Transport
    Hope it helps...
    regards,
    Raju

  • Custom step type Export and Import

    Hi,
       I have created custom step types similar IVI for all my HAL drivers.
    I need help in sharing it with my team in different locations.
    I am looking at exporting and importing of the custome step types similar to templates.
    Could anyone help me with this.
    Thanks in advance
    Anna

    Anna,
    when creating the step type definition, you have picked a location for it. By default, it is "MyTypes.ini".
    You can create your own custom ini-file containing your specific step types in the type editor.
    When distributing your step types, you have to pass the ini-file containing the type definition(s) AND all sources connected to that types (substep modules).
    On the target machine, you have to include that ini-file in the system for type definitions in the type editor.
    Norbert
    CEO: What exactly is stopping us from doing this?
    Expert: Geometry
    Marketing Manager: Just ignore it.

  • How to export & import customer table space from non-unicode to unicode sys

    hello all,
    I have performed a migration of Single code to Unicode system. -
    (ECC 6.0 SR2)
    After completion of export & import i have noticed  there is one customer table space which is missing.
    eg - PSAPABCD
    I have checked in source system & noticed that Table space is created by customer & not maintained properly as required,
    therefore it is not either exported or imported.
    Please advice me how should i manage to export tablespace from Non - unicode system & import in Unicode.
    Is there any work out.
    Thanks & rgds,
    -rahul

    Hi Rahul,
    please have a look at
    http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f0f9f37c-be11-2a10-3baf-d5d7de5fb78d
    point 3) f. and g.
    However in order to keep consistency I would highly recommend to export and import all tables at the same time.
    Best regards,
    Nils Buerckel
    SAP AG

  • Customizing request & Workbench request

    Dear all,
                    What is the differance between Customizing Request & workbench request?

    Hi,
    Workbench Requests
    When you change a Repository object of the ABAP Workbench, a query window appears in which you need to specify a Workbench request. You can only save the changes if you have assigned the object to a change request.
    Workbench requests and the tasks assigned to them are normally used to record changes to Repository objects and Customizing for all clients. However, you can also include client-specific Customizing.
    Whether the changes to Repository objects are transported depends on whether a transport route is defined from the current SAP System for the package of these objects. From the system settings, the system automatically determines whether the change requests are transportable and to which target system they should be transported.
    Workbench requests record changes made to ABAP Workbench objects.
    There are local and transportable Workbench requests. (Local Workbench requests have the target system <space>.)
    The package of the object and the transport route settings in the Transport Management System determine whether changes are recorded in a local or a transportable Workbench request.
    Customizing requests
    Customizing requests record client-specific Customizing settings made in a single client (the source client of the request).
    Automatic recording of configuration activities in the Customizing work for a client can be activated or deactivated for each client with Client Control. If automatic recording is active, a query window appears when you change Customizing settings, asking you to specify a Customizing request.
    Whether Customizing requests are transported or not, does not depend on the objects entered, as is the case with Workbench change requests. The Customizing requests in an SAP System (or in a client if you use Extended Transport Control) are either all transportable or all local, depending on the system setting. The system uses the standard transport layer to determine automatically whether the change requests are transportable and to which target system they should be transported. However, you can change this manually.
    Changes to Customizing settings are recorded in Customizing requests.
    When you release the requests, the current status of the recorded settings is exported, and can then be imported into the consolidation system and, if necessary, into subsequent delivery systems.
    The client settings determine whether
    o changes to the Customizing settings are possible
    o the changes are recorded
    When you create Customizing requests, the transport target is automatically assigned the standard transport layer by the R/3 System.
    Regards,
    Satish

  • Export and Import of Configuration Data

    Hi All,
    I have created a number of custom properties, structures, groups, renderers, layout sets etc and would like to move them from Dev to Test system.
    I have found the following in the help doco:
    "Export and Import of Configuration Data"
    http://help.sap.com/saphelp_nw04/helpdata/en/e1/029c414c79b25fe10000000a1550b0/content.htm
    However I am unable to see its functionality in our portal systems (namely the Actions->Export and Actions->Import functions).
    Our version of Portal is: 6.0.9.6.0
    KM: 6.0.9.3.0 (NW04 SPS09 Patch3)
    Therefore we should be able to see it? no?
    Are there any special settings to see these buttons?
    Cheers,
    Vic

    Thanks for your replies.
    OK, so in otherwords, it is not available in SP09 and only in SP12+.
    So, to "transport" this information I will have to manually reapply thes settings in the Test system!
    Message was edited by: Victor Yeoh

  • Unable to Export certificates as Personal Information Exchange - PKCS #12 (.PFX) file format.

    We are using Windows 2003 Certificate Authorities, and we are unable to Export certificates as .PFX, our only options are, DER encoded binary X.509 (.CER), Base-64 encoded X.509 (.CER), or Cryptographic Message Syntax Standard - PKCS #7 Certificates (.P7B).  The .PFX option is grayed out in the Certificate Export Wizard on the CA.
    This posses a problem because our Windows 2008 server running IIS 7 wants us to import a certificate as .PFX
    can someone explain what is happening and how to fix it please

    Greg --
    The private key doesn't exist on the CA, but it does exist on the computer on whic you created the request. Here's what happens when you request a certificate.
    If you're generating a request with a new key pair -- which you will in the vast majority of cases -- Windows first generates the public and private key pair. The private key is written to a key store. Where the key store is located will depend on which
    Cryptographic Service Provider (CSP) or Key Storage Provider (KSP) is specified in the template. KSPs were introduced in Windows Server 2008/Vista, and are only available in v3 templates. In the case of most of the default Microsoft CSP/KSPs (with the exception
    of those used with Smart Cards), the key store is located in either the user's profile, or in the case of computer certificates, the All Users profile. It is at this point, by the way, that the properties of that private key are also written to the key store.
    One property of interest to you immediately is whether or not Windows should allow the private key to be exported.
    Once the key pair is generated, the request is then created. The request contains the information that should be in the certificate. This information is generally specified by the template with the exception of the Subject field, which contains the Common
    Name or Distinguished name of whoever is requesting the certificate. In the case of IIS, the Subject will be your site name. The public key is included in the request. Windows then signs the request with the newly created private key.
    Windows also creates a dummy certificate object in the Certificate Enrollment Requests store so that it knows that there is an outstanding request.
    At this point, the request is saved to a file or sent to an online CA depending on how you generated the request. Note that the private key is
    not sent to the CA in most cases. The exception to this rule occurs when you have Key Archival enabled on the CA, and the template specifies that the private key should be archived in the CA database. If this is the case, Windows retrieves
    the CA Exchange certificate from the CA and uses the public key in that certificate to encrypt the newly created private key. This encrypted private key is included in the request.
    Once the CA receives the request, it processes that request to determine if it should issue the certificate or not. In the case of the Enterprise CA, this decision is based on the permissions on the template. One can also specify that certain templates
    require CA manager approval before they can be issued. Assuming that everything is correct in the request, and that the necessary information can be retrieved from Active Directory (perhaps the user's email address, or the computer's DNS host name -- it depends
    on the settings in the template), and that any CA Manager approvals specified in the template have been performed, the CA builds the certificate and signs it with its current private key. The certificate has been created.
    This certificate is stored in the CA database, which is why you can export it in the Certificate Authority snap-in. If the encrypted private key for that certificate has been included in the request to be archived, the CA decrypts it first with its CA Exchange
    private key, and then re-encrypts it using the public key(s) for any Key Recovery Agents configured on the CA. The newly encrypted private key is also stored in the CA database. Note that this encrypted private key can only be retrieved and decrypted
    by a valid KRA.
    The CA then returns the certificate to principal who requested it. If the request was first saved as a file and then submitted to the CA you have to retrieve the certificate manually. It is only returned automatically if you submitted the request via the
    Certificiates MMC, or if the application you use to submit the request retrieves it for you. IIS does this, when you use the certificate request wizard to request a Web Server certificate.
    When the client has received the certificate, it locates the dummy certificate object in the Certificate Enrollment Requests store. From this object, Windows copies the location of the key store for the private key (among other things). This dummy certificate
    object is then deleted, and the new certificate is imported into the Personal store. The private key information is then written to an internal property of the certificate in the store. This is how Windows locates the private key of that certificate in order
    to use it when you invoke the associated certificate.
    When you go to export the certificate and private key, Windows reads the private key locate information from the certificate properties in order to find the key store wherein it is located. Assuming export is allowed, the certificate and private key are written
    to a password protected PFX file.
    That's how a certificate request gets turned into a certificate, and explains why the private key doesn't exist on the CA. If you need to generate a PFX file, then you'll have to export the certificate from the computer on which you generated the request.
    Hope this helps.
    Jonathan Stephens
    Jonathan Stephens

  • Export and import XI are different

    I have seen a similar message in this forum but it does not apply to my scenario. I have exhausted all avenues and SAP has not responded to my customer message so I am hoping someone has seen this error. Below is the entire dump I am receiving when I try to export a directory object in XI using CMS. My repository objects transport successfully. I am running XI 3.0 SP16 (with the SP16 additional patches).
    Info:Starting Step Repository-import at 2006-04-12 15:11:52.0585 -4:00
    Info:Component:sap.com/SAP-INTDIR
    Info:Version  :DXI_ID.ALL_D.6
    Info:1. PR is of type TCSChangeRequest
    Info:export and import XI are different: http://bsrdxi001:51400/dir -> http://bsrqxi001:52400/dir
    Info:reading of XI2a15dd10c95511daa4f4001143e11d98.cl for xichangelist 2a15dd10c95511daa4f4001143e11d98
    Fatal Exception:com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: XiTransportException received:
    ClientServerException exception:java.lang.NullPointerException
    com.sap.aii.ib.core.transport.api.TransportCsException: java.lang.NullPointerException
         at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcImport(PvcTransport.java:145)
         at com.sap.aii.ibdir.server.transport.impl.pvc.DirPvcTransport.pvcImport(DirPvcTransport.java:74)
         at com.sap.aii.ibdir.server.transport.impl.service.InternalDirTransportServiceImpl.pvcImport(InternalDirTransportServiceImpl.java:127)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:705)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importXiStream(InternalTransportServiceImpl.java:494)
         at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importXiStream(TransportServiceImpl.java:224)
         at com.sap.aii.ib.server.transport.impl.hmi.CmsHmiMethods.process(CmsHmiMethods.java:223)
         at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
         at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
         at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
         at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl10.process(HmisLocalLocalObjectImpl10.java:144)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211)
         at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
         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)
    Serialized exception:java.lang.NullPointerException
    java.lang.NullPointerException
         at com.sap.aii.ibdir.server.sldaccess.gen.LDAccess.getSAPBusinessSystem(LDAccess.java:302)
         at com.sap.aii.ibdir.server.sldaccess.gen.LDAccess.getMySAPIntegrationServerBusinessSystem(LDAccess.java:262)
         at com.sap.aii.ibdir.server.sldaccess.gen.LDAccess.getMyBusinessSystemGroup(LDAccess.java:195)
         at com.sap.aii.ibdir.server.sldaccess.gen.LDAccess.getBusinessSystemNameInMyGroup(LDAccess.java:125)
         at com.sap.aii.ibdir.server.transport.impl.postprocessing.TransportPostprocessor.renameService(TransportPostprocessor.java:810)
         at com.sap.aii.ibdir.server.transport.impl.postprocessing.TransportPostprocessor.createNewXiKeyFor_RD_ID_RA_SA(TransportPostprocessor.java:1104)
         at com.sap.aii.ibdir.server.transport.impl.postprocessing.TransportPostprocessor.postprocessTransport(TransportPostprocessor.java:424)
         at com.sap.aii.ibdir.server.transport.impl.postprocessing.DirImportPostprocessor.postprocess30Import(DirImportPostprocessor.java:101)
         at com.sap.aii.ibdir.server.transport.impl.postprocessing.InternalPostprocessingService.postprocess(InternalPostprocessingService.java:210)
         at com.sap.aii.ibdir.server.transport.impl.postprocessing.PostprocessingService.doPostprocessing(PostprocessingService.java:168)
         at com.sap.aii.ibdir.server.pvcadapt.XIDirPropagationProvider.transportFinished(XIDirPropagationProvider.java:90)
         at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcImport(PvcTransport.java:107)
         at com.sap.aii.ibdir.server.transport.impl.pvc.DirPvcTransport.pvcImport(DirPvcTransport.java:74)
         at com.sap.aii.ibdir.server.transport.impl.service.InternalDirTransportServiceImpl.pvcImport(InternalDirTransportServiceImpl.java:127)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:705)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importXiStream(InternalTransportServiceImpl.java:494)
         at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importXiStream(TransportServiceImpl.java:224)
         at com.sap.aii.ib.server.transport.impl.hmi.CmsHmiMethods.process(CmsHmiMethods.java:223)
         at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
         at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
         at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
         at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl10.process(HmisLocalLocalObjectImpl10.java:144)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211)
         at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
         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)
    :communication error: XiTransportException received:
    ClientServerException exception:java.lang.NullPointerException
    com.sap.aii.ib.core.transport.api.TransportCsException: java.lang.NullPointerException
         at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcImport(PvcTransport.java:145)
         at com.sap.aii.ibdir.server.transport.impl.pvc.DirPvcTransport.pvcImport(DirPvcTransport.java:74)
         at com.sap.aii.ibdir.server.transport.impl.service.InternalDirTransportServiceImpl.pvcImport(InternalDirTransportServiceImpl.java:127)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:705)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importXiStream(InternalTransportServiceImpl.java:494)
         at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importXiStream(TransportServiceImpl.java:224)
         at com.sap.aii.ib.server.transport.impl.hmi.CmsHmiMethods.process(CmsHmiMethods.java:223)
         at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
         at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
         at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
         at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl10.process(HmisLocalLocalObjectImpl10.java:144)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211)
         at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
         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)
    Serialized exception:java.lang.NullPointerException
    java.lang.NullPointerException
         at com.sap.aii.ibdir.server.sldaccess.gen.LDAccess.getSAPBusinessSystem(LDAccess.java:302)
         at com.sap.aii.ibdir.server.sldaccess.gen.LDAccess.getMySAPIntegrationServerBusinessSystem(LDAccess.java:262)
         at com.sap.aii.ibdir.server.sldaccess.gen.LDAccess.getMyBusinessSystemGroup(LDAccess.java:195)
         at com.sap.aii.ibdir.server.sldaccess.gen.LDAccess.getBusinessSystemNameInMyGroup(LDAccess.java:125)
         at com.sap.aii.ibdir.server.transport.impl.postprocessing.TransportPostprocessor.renameService(TransportPostprocessor.java:810)
         at com.sap.aii.ibdir.server.transport.impl.postprocessing.TransportPostprocessor.createNewXiKeyFor_RD_ID_RA_SA(TransportPostprocessor.java:1104)
         at com.sap.aii.ibdir.server.transport.impl.postprocessing.TransportPostprocessor.postprocessTransport(TransportPostprocessor.java:424)
         at com.sap.aii.ibdir.server.transport.impl.postprocessing.DirImportPostprocessor.postprocess30Import(DirImportPostprocessor.java:101)
         at com.sap.aii.ibdir.server.transport.impl.postprocessing.InternalPostprocessingService.postprocess(InternalPostprocessingService.java:210)
         at com.sap.aii.ibdir.server.transport.impl.postprocessing.PostprocessingService.doPostprocessing(PostprocessingService.java:168)
         at com.sap.aii.ibdir.server.pvcadapt.XIDirPropagationProvider.transportFinished(XIDirPropagationProvider.java:90)
         at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcImport(PvcTransport.java:107)
         at com.sap.aii.ibdir.server.transport.impl.pvc.DirPvcTransport.pvcImport(DirPvcTransport.java:74)
         at com.sap.aii.ibdir.server.transport.impl.service.InternalDirTransportServiceImpl.pvcImport(InternalDirTransportServiceImpl.java:127)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:705)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importXiStream(InternalTransportServiceImpl.java:494)
         at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importXiStream(TransportServiceImpl.java:224)
         at com.sap.aii.ib.server.transport.impl.hmi.CmsHmiMethods.process(CmsHmiMethods.java:223)
         at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
         at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
         at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
         at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl10.process(HmisLocalLocalObjectImpl10.java:144)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211)
         at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
         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)
    com.sap.cms.tcs.interfaces.exceptions.TCSCommunicationException: communication error: XiTransportException received:
    ClientServerException exception:java.lang.NullPointerException
    com.sap.aii.ib.core.transport.api.TransportCsException: java.lang.NullPointerException
         at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcImport(PvcTransport.java:145)
         at com.sap.aii.ibdir.server.transport.impl.pvc.DirPvcTransport.pvcImport(DirPvcTransport.java:74)
         at com.sap.aii.ibdir.server.transport.impl.service.InternalDirTransportServiceImpl.pvcImport(InternalDirTransportServiceImpl.java:127)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:705)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importXiStream(InternalTransportServiceImpl.java:494)
         at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importXiStream(TransportServiceImpl.java:224)
         at com.sap.aii.ib.server.transport.impl.hmi.CmsHmiMethods.process(CmsHmiMethods.java:223)
         at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
         at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
         at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
         at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl10.process(HmisLocalLocalObjectImpl10.java:144)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211)
         at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
         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)
    Serialized exception:java.lang.NullPointerException
    java.lang.NullPointerException
         at com.sap.aii.ibdir.server.sldaccess.gen.LDAccess.getSAPBusinessSystem(LDAccess.java:302)
         at com.sap.aii.ibdir.server.sldaccess.gen.LDAccess.getMySAPIntegrationServerBusinessSystem(LDAccess.java:262)
         at com.sap.aii.ibdir.server.sldaccess.gen.LDAccess.getMyBusinessSystemGroup(LDAccess.java:195)
         at com.sap.aii.ibdir.server.sldaccess.gen.LDAccess.getBusinessSystemNameInMyGroup(LDAccess.java:125)
         at com.sap.aii.ibdir.server.transport.impl.postprocessing.TransportPostprocessor.renameService(TransportPostprocessor.java:810)
         at com.sap.aii.ibdir.server.transport.impl.postprocessing.TransportPostprocessor.createNewXiKeyFor_RD_ID_RA_SA(TransportPostprocessor.java:1104)
         at com.sap.aii.ibdir.server.transport.impl.postprocessing.TransportPostprocessor.postprocessTransport(TransportPostprocessor.java:424)
         at com.sap.aii.ibdir.server.transport.impl.postprocessing.DirImportPostprocessor.postprocess30Import(DirImportPostprocessor.java:101)
         at com.sap.aii.ibdir.server.transport.impl.postprocessing.InternalPostprocessingService.postprocess(InternalPostprocessingService.java:210)
         at com.sap.aii.ibdir.server.transport.impl.postprocessing.PostprocessingService.doPostprocessing(PostprocessingService.java:168)
         at com.sap.aii.ibdir.server.pvcadapt.XIDirPropagationProvider.transportFinished(XIDirPropagationProvider.java:90)
         at com.sap.aii.ib.server.transport.impl.pvc.PvcTransport.pvcImport(PvcTransport.java:107)
         at com.sap.aii.ibdir.server.transport.impl.pvc.DirPvcTransport.pvcImport(DirPvcTransport.java:74)
         at com.sap.aii.ibdir.server.transport.impl.service.InternalDirTransportServiceImpl.pvcImport(InternalDirTransportServiceImpl.java:127)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importZippedStream(InternalTransportServiceImpl.java:705)
         at com.sap.aii.ib.server.transport.impl.service.InternalTransportServiceImpl.importXiStream(InternalTransportServiceImpl.java:494)
         at com.sap.aii.ib.server.transport.impl.service.TransportServiceImpl.importXiStream(TransportServiceImpl.java:224)
         at com.sap.aii.ib.server.transport.impl.hmi.CmsHmiMethods.process(CmsHmiMethods.java:223)
         at com.sap.aii.utilxi.hmis.server.HmisServiceImpl.invokeMethod(HmisServiceImpl.java:169)
         at com.sap.aii.utilxi.hmis.server.HmisServer.process(HmisServer.java:178)
         at com.sap.aii.utilxi.hmis.sbeans.HmisBeanImpl.process(HmisBeanImpl.java:86)
         at com.sap.aii.utilxi.hmis.sbeans.HmisLocalLocalObjectImpl10.process(HmisLocalLocalObjectImpl10.java:144)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:290)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.processRequestByHmiServer(HmisServletImpl.java:211)
         at com.sap.aii.utilxi.hmis.web.workers.HmisInternalClient.doWork(HmisInternalClient.java:70)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doWork(HmisServletImpl.java:496)
         at com.sap.aii.utilxi.hmis.web.HmisServletImpl.doPost(HmisServletImpl.java:634)
         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)
         at com.sap.cms.tcs.client.XICommunicator.writeChangelistData(XICommunicator.java:258)
         at com.sap.cms.tcs.core.RepositoryImportTask.processRepositoryImport(RepositoryImportTask.java:186)
         at com.sap.cms.tcs.core.RepositoryImportTask.process(RepositoryImportTask.java:500)
         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.LocalCmsTransportProxyLocalObjectImpl20.startImport(LocalCmsTransportProxyLocalObjectImpl20.java:1144)
         at com.sap.cms.ui.wl.Custom1.importQueue(Custom1.java:1279)
         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.task.WebDynproMainTask.handleAction(WebDynproMainTask.java:101)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.handleActionEvent(WebDynproMainTask.java:304)
         at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:659)
         at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
         at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
         at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
         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 Repository-import ended with result 'fatal error' ,stopping execution at 2006-04-12 15:11:56.0382 -4:00

    Hi,
    unfortunately i can't help you with your CMS problem, however if SAP has not responded to your OSS message, why don't you escalate it? In OSS Note 560499 you can find the phone number of the support hotline and they will be able to find a processor and speed up the processing of your message. 
    regards
    Christine

  • Customizing requests

    hi all sd gurus
    plz send me some information about the transport requests ,and how do we post when do we release?who releases  etc,in realtime work..
    i know se09,but what dowe do in that tcode.
    id- [email protected]
    thank u all
    vivek

    Dear Vivek,
    You would release the transport using Transction SE09/SE10/SE01. You would release the request in the current server so that it can be imported in QA/PROD etc. Releasing of the requests does not automatically take them in to QA/PROD. You would have to import them.
    Transport Layers and Transport Routes are defined based on your system landscape.
    BASIS people would <b>import them using transaction STMS</b> in to QA/PROD. Only released requests can be imported.
    Transport Layers and Transport Routes:
    http://help.sap.com/saphelp_nw04/helpdata/en/57/38ddff4eb711d182bf0000e829fbfe/frameset.htm
    All development projects developed in the same SAP System and transported on the same transport routes are grouped together to form a transport layer.
    Before you start the first development project, you create a transport layer in the TMS  transport route editor. This transport layer is assigned to the development system as its  standard transport layer. Objects delivered by SAP belong to the transport layer "SAP". Other transport layers are generally only needed when new development systems are included in the system group.
    After you have set up the transport layer you set up the transport routes. There are two types of transport routes. First you set up consolidation routes, and then you set up delivery routes:
    Consolidation routes
    To make your changes transportable, set up a consolidation route for each transport layer. Specify your development system as the starting point (source) of these consolidation routes. Specify the quality assurance system as the transport target (in a two-system landscape, specify the production system as the transport target).
    Any modified objects that have a consolidation route set up for their transport layer are included in transportable change requests. After the request has been released the objects can be imported into the consolidation system.
    If you make changes to objects which have no consolidation route defined for their transport layer, then the changes are made automatically in local change requests (or in Customizing requests without a transport target). You cannot transport them into other SAP Systems.
    You can set up one consolidation route only for each SAP System and transport layer.
    When you define consolidation routes, note the additional functions available when you use Extended Transport Control.
    Delivery routes
    After you have imported your development work into the quality assurance system, you then want to transport it into your production system. You may even want to transport it into several SAP Systems (for example, additional training systems). To do this, you have to set up delivery routes.
    Delivery routes have a source system and a target system.
    When you set up a delivery route, you are making sure that all change requests that are imported into the route’s source system are automatically flagged for import into the route’s target system.
    You can set up several delivery routes with the same source system and different target systems (parallel forwarding). You can also set up delivery routes in sequence (multilevel forwarding).
    CTS transport control makes sure that all requests from the development system are flagged for import into all other SAP Systems in the same order in which they were exported. This is important, since different requests can contain the same Repository object or the same Customizing setting at different development levels, and you must avoid overwriting a more recent version with an older version.
    Hope this will help.
    Regards,
    Naveen.

Maybe you are looking for

  • How to get active layer comp

    Is there a way of getting the active layer comp? I have a script that applies a series of layer comps saving different versions of the file in between, however it seems that on a very fast machine it the script tries to move onto saving before the la

  • Powering on a new Quad G5 ?

    I just got in a Quad, and the reality of not being able to power it on by touching the power button on my ADC monitors, just hit home. I of course have to use the ADC to DVI adapters, and my G5 is located deep under my desk. I have a bad neck, and re

  • Need help with uploading photos from PSE 12 to Revel

    When I first logged into Revel from my new Photoshop 12 I selected the option to have me select which photos would be uploaded to Revel.  That turned out to be a huge mistake.  All I want to do is upload my current catelogue with the albums intact to

  • KPF6 : Enter Sales Planning

    Hi, Is it posssible to enter a planning by value and by quantity (Sales Planning) with Tcode KPF6 ? Please If yes, How ? Regards.

  • Problems installing downloaded applications

    I am having problems installing downloaded applications.  After I download an application, I can see it in my "downloads" folder.  When I double click it, instead of finding the package, I am taken directly to my "terminal" screen, and then cannot in