package processing in CCM (AUTH_UPDATE batch-job)

[Former Member]

Hello all

We're using CCM 2.0 with SP03. We send CatalogueUpdateNotification_in messages (in XML format) to our XI and route it 1:1 to our CCM system. There it is processed by an <b>async started AUTH_UPDATE batch-job</b>. This job finally processes our catalog items.

As log as this batch-job runs the concerned catalog being updated is locked for other updates. And this is what causes us some head aches!

We send XML messages containing up to 2000 catalog items. This makes the batch job run quite long (up to 1.5h). Now, when we have more than 2000 updates to send to our catalog, we split it up into packages with up to 2000 items each.

Each package being sent from XI to CCM creates such a AUTH_UPDATE batch-job. The 1st starting is able to lock the catalog but this way of course also blocks processing of all other packages.

Every single minute the next (waiting / blocked) package tries to lock the catalog itself before it can be processed. This ensures parallel update processings but the other way around it also causes to fall into a timeout after lets say ca. 30 retries.

From XI point of view the timedout out package(s) sent to CCM were successfully processed... means: not restartable!

In CCM I can't find a way trying to re-process such a timedout package.

Re-generating the same package from the source system is not an option for us as well... it takes to much efforts.

Is there a way to change the wait time between retrying to lock the catalog?

OR

Is there a way to ensure that only 1 AUTH_UPDATE batch-job is started at the same time?

Thanks for some ideas to solve this.

Renaud

[Former Member · Accepted solution]

Hi

<b>Please go through the follwoing SAP OSS Notes -></b>

Note 724152 - Timeout w/ publication via XI

Note 728495 - Timeout short dump for large catalogs

Note 737469 - Debugging for file upload and publication easier

Note 723199 - Name of file to be uploaded must stand in log

Note 740263 - Short dump in report /CCM/PROCESS_PACKAGE

Do let me know.

Regards

- Atul

[Former Member · Accepted solution]

Hi Atul

Thanks!

Note 724152 - Timeout w/ publication via XI

-> fits to CCM 1.0, we're on CCM 2.0 SP03

-> fits to catalog publication not to catalog updates (step before publication)

Note 728495 - Timeout short dump for large catalogs

-> fits to CCM 1.0, we're on CCM 2.0 SP03

Note 737469 - Debugging for file upload and publication easier

-> fits to CCM 1.0, we're on CCM 2.0 SP03

-> don't see how it should relate to our problem

Note 723199 - Name of file to be uploaded must stand in log

-> fits to CCM 1.0, we're on CCM 2.0 SP03

-> we're not uploading files, XI sends XML data via server proxy

Note 740263 - Short dump in report /CCM/PROCESS_PACKAGE

-> fits to CCM 1.0, we're on CCM 2.0 SP03

-> doesn't address our problem / my question

I also went through other OSS notes... didn't find something useful.

Any other thoughts? Ideas?

Regards,

Renaud

[Former Member · Accepted solution]

Hi

<b>Please go through the SAP OSS Notes and pointers as well -></b>

Note 908054 - CCM 2.0 SP03 on Netweaver 04s SP Stack 06

Note 1002775 - Asynchronous deletion of old version after publication

Note 955096 - Rule condition (Not Equal with Not Valuated) in the view

Note 887328 - CCM20 - modifications for /CCM/VERIFY_CATALOG

Note 865138 - CCM20SP0 upload overview message "Category not found"

Note 873340 - Problems with BMECat mapping after patching XI

Note 864313 - Input help for mass editor

<u>Related links -></u>

Incase this does not help, please raise a customer OSS Message with SAP as well for faster resolution of your queries.

Do let me know. Hope this will help.

Regards

- Atul

[Former Member]

Was able to solve it. Changed 2 things:

1) Implemented TransmissionHeader in CatalogueUpdateNotification message

2) We're now sending the packages now using qos=EOIO which makes the XI forwarding the packages in their respective order to CCM

Thanks for your inputs and thought, Atul

Regards

Renaud