on 08-04-2014 9:11 AM
Hi,
Our redwood M28 is running on Solman on netweaver 701 with redwood license. Now we have planned to migrate the redwood CPS to new standalone java system.
I have installed SAP netweaver java 7.31 with CPS M33.92 version and created environment SAP which automatically created a queue. Now we want to move all job chains from old redwood in solman to new system. I am able to export and import single job chain successfully but not able to export and import through car file. Is it possible to export all job chain and import in new system. We have the license for new redwood CPS also. I tried to look in many blogs mentioned below but could not find the correct solution.
http://wiki.scn.sap.com/wiki/display/SM/FAQ+Job+Scheduling+Management
http://scn.sap.com/thread/3381486
http://scn.sap.com/thread/1571783
Also I have noted that, export tree option under the application SAP is disabled. I have tried export using export rule set but it did not worked.
Any help with regards to export/ import of the job chains will be great
Regards,
Vinz
Hi Vineet,
You are on the right track.
The SAP application is built-in.
Create your own application named Export at the root, on the same level as the application Redwood.
Now, "move" all applications which contain your job chains and their dependencies into the Export application (You simply set the parent application to Export if the application in question has no parent application OR the parent application is a built-in application, such as "SAP").
Ideally, you want to preserve your application "hierarchy", because it certainly helps you identify what is what. The idea is to move the hierarchy into the "Export" application. You will have to make sure that all objects referenced by the job chain (job definitions, child job chains, time windows, queues etc) exist in the car file or new system.
Move your environment into the applciation "Export": Platform process servers, SAP systems, queues, time windows, submit frames etc should all be in a child application of "Export".
Then move defintions like job definitions, reports, events ...
Then you export the "Export" application, using the export tree option, and import that into your new system.
Regards,
HP
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vineet,
No, this has absolutely no incidence on job schedules or behavior. The application property of objects is used to organize them functionally, e.g. like a tag.
Remember that it is a good idea to have all objects that can have an application in applications with functional names. for exports. If you have a great number of objects (1000's) it might be better to export them into several CAR files.
Regards,
HP
Hi Vineet,
Another thing you can do, is create an export ruleset that exports all objects, simply use the Export List tab, export by modification date, so you set the field Where the object was changed after, to a date way back in the past ... 1990, to be on the safe side ;-).
Now you save it, and in the list of export rule sets, select the previously created export rule set and click Submit Export job. This will create a job will a car file containing all your objects.
Regards,
HP
Hi Vineet,
Indeed, I have not seen M28 for such a long time ... hm, I guess that would be your only option.
You can use the below code, adapt it for job definitions, process servers, sap systems, time windows, submit frames ... to execute in the Shell (Scripting > Shell)
{
Partition partition = jcsSession.getPartitionByName("GLOBAL");
Application exportApplication = jcsSession.getApplicationByName("Export");
Application unsortedApplication = jcsSession.getApplicationByName(partition, exportApplication, "Unsorted")
for (Iterator it = jcsSession.executeObjectQuery("select Queue.* from Queue where Name <> 'System'",null); it.hasNext();)
{
Queue Queue = (Queue) it.next();
if (Queue.getParentApplication() == null)
{
try
{
Queue.setParentApplication(application);
}
catch(exception e)
{//ignore}
}
jcsSession.persist();
}
}
To adapt above code to process servers, for example, simply replace Queue with ProcessServer.
Regards,
HP
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.