Issue in importing CAR FILES

[Former Member]

Hi Everyone,

I am getting the below Error when trying to import the CAR file into our Quality system which I saved on my desktop.

I used the below procedure to import the CAR file which I saved on my desktop

Using Imports

1. Navigate to Promotion > Import

2. Choose Import from the context-menu.

Here I have choosen the option: Upload file to server( selected the file from my desktop)

ERROR 2015-03-03 18:31:01,637 America/New_York [Redwood Job Thread Pool: GLOBAL.System.System worker 0] job.System_Import_Archive.2773 - Import failed, no objects have been imported.

-- JOB RUN STACK TRACE --

java.util.zip.ZipException: Open failed for '/usr/sap/RQ1/J00/j2ee/cluster/server0/scheduler/0-9999/2773/JOB_2773carin.car.car' with errno 2

at java.util.zip.ZipFile.open(Native Method)

at java.util.zip.ZipFile.<init>(ZipFile.java:154)

at java.util.jar.JarFile.<init>(JarFile.java:141)

at java.util.jar.JarFile.<init>(JarFile.java:78)

at sun.net.www.protocol.jar.URLJarFile.<init>(URLJarFile.java:72)

at sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:48)

at sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:70)

at sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:104)

at com.redwood.scheduler.model.imprt.JarDerivedUrlConnection.connect(JarDerivedUrlConnection.java:49)

at com.redwood.scheduler.model.imprt.CronacleArchiveReader.importAll(CronacleArchiveReader.java:82)

at com.redwood.scheduler.system.jobs.CronacleArchiveImport.runInternal(CronacleArchiveImport.java:397)

at com.redwood.scheduler.system.jobs.CronacleArchiveImport.run(CronacleArchiveImport.java:193)

at com.redwood.scheduler.system.jobs.CommonSystemJob.execute(CommonSystemJob.java:53)

at com.redwood.scheduler.systemjobservice.impl.JobWorker.doWork(JobWorker.java:253)

at com.redwood.scheduler.infrastructure.workqueue.Worker.run(Worker.java:76)

at java.lang.Thread.run(Thread.java:763)

Please help

Thank you,

Chandu

[gmblom]

Hello,

You are probably running your CPS system in a multi node setup.

In that case set a Registry Entry /configuration/jcs/upload/UploadedFilesPath and make sure the path that you specify is accessible from all nodes in the cluster.

Regards Gerben

[Former Member]

Thank you Gerben.

I saved the car file onto my desktop. To import it into our QA system, instead of specifying the registry key, can I import the CAR file from my desktop by going to promotion -->import

and by choosing the option: Upload file to server( select the file from desktop)?

Please advise.

Regards,

Chandu

[Former Member]

Dear Friends,

Below are the steps which I did. Please advise.

Step 1: I have defined the export rule set in Development and exported one application.

Step 2: Saved the CAR file onto my desktop

Step 3. We are running our QA CPS in a multi node setup where we have 2 APP servers
But instead of using the cluster URL, I used the APP01 server URL to login to QA.

step 4: In QA, I used the below steps to import the car file which is saved on my desktop

        a. Navigate to Promotion > Import

        b. Choose Import from the context-menu.

Here I have choosen the option: Upload file to server( selected the file from my desktop)

I am getting the below error using the above process.

ERROR 2015-03-05 12:42:43,400 America/New_York [Redwood Job Thread Pool: GLOBAL.System.System worker 0] job.System_Import_Archive.4001 - Import failed, no objects have been imported.
-- JOB RUN STACK TRACE --
java.util.zip.ZipException: Open failed for '/usr/sap/RQ1/J00/j2ee/cluster/server0/scheduler/0-9999/4001/JOB_4001carin.car.car' with errno 2
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(ZipFile.java:154)
at java.util.jar.JarFile.<init>(JarFile.java:141)
at java.util.jar.JarFile.<init>(JarFile.java:78)
at sun.net.www.protocol.jar.URLJarFile.<init>(URLJarFile.java:72)
at sun.net.www.protocol.jar.URLJarFile.getJarFile(URLJarFile.java:48)
at sun.net.www.protocol.jar.JarFileFactory.get(JarFileFactory.java:70)
at sun.net.www.protocol.jar.JarURLConnection.connect(JarURLConnection.java:104)
at com.redwood.scheduler.model.imprt.JarDerivedUrlConnection.connect(JarDerivedUrlConnection.java:49)
at com.redwood.scheduler.model.imprt.CronacleArchiveReader.importAll(CronacleArchiveReader.java:82)
at com.redwood.scheduler.system.jobs.CronacleArchiveImport.runInternal(CronacleArchiveImport.java:397)
at com.redwood.scheduler.system.jobs.CronacleArchiveImport.run(CronacleArchiveImport.java:193)
at com.redwood.scheduler.system.jobs.CommonSystemJob.execute(CommonSystemJob.java:53)
at com.redwood.scheduler.systemjobservice.impl.JobWorker.doWork(JobWorker.java:253)
at com.redwood.scheduler.infrastructure.workqueue.Worker.run(Worker.java:76)
at java.lang.Thread.run(Thread.java:763)

But I am able to export a test application successfully from QA system and import into our Development system using the above mentioned process. Please help.

Regards, Chandu

[nanda_kumar21]

1. Go to monitoring-->Monitor Tree
2. Expand System-->Cluster-->CLUSTER-->Expand all node below that.
3. Expand the server details
4. Note which server has "Master" set to true.
5. Login to http://<Master>:50000/scheduler and try the import.

Whenever you reboot any of your nodes, check which is the master and then try the import from the master node.

If you think is painful, maintain the registry key provided by , so that irrespective of master or slave, you file get imported.

thanks

Nanda

[gmblom]

Like Nanda says: if you have a cluster without a shared file system and the registry key set, you can only import from the master node.

Regards Gerben

[Former Member]

Thank you so much Nanda. We have imported all the objects into our new QA system successfully with your instructions.

As per Gerben's advice, we were already in the process of setting up of shared file system which can be accessible from all nodes in the cluster to do the export and import.
As it takes some time by our admins to configure the shared file system at our place due to processes involved, we copied all the dev objects into our new QA system using the above method.

Regards,
Chandu