Mapping documents, nothing in pipeline

, ,
1

Hello,

…I have problem with mapping documents.
After document is (properly?) mapped, pipeline dump gives me nothing (only input documents are in pipeline dumped to file).

Implementation:
docBillingRequest - publishable document (with Billing reference document)
subscriptionTrigger - calling service “handling”
handling - input to this service was choosen by document type chooser (docBillingRequest)

next thing is the problematic service which maps docBillingRequest to docTypeRef_tns_BillingOut_submit_Input

map steps looks like this:

Billing(reference)\dept

is mapped to

nativeDoc\BillingRequest\dept

etc.
lists, are mapped in loops - each field is mapped to newly created field in target document

the whole target document is created in succesive map steps, and after everything is mapped, the nativeDoc is simply mapped to:
billing(reference)

the problem is:

  1. when I am starting (from developer) “handling” service - the document maps
  2. when I am publishing document to broker, trigger is calling “handling” service and - the document doesnt maps ; (

With Best Regards,
GOLAN.

ps: Help please. I was trying to solve this for few days looking for a different approuches, searched web resources, and find nothing helpfull to solve this problem.

2

Hi,

Try to compare input document name with name in MAP step. Are they identical? I had a lot of cases when in start or end field name was space or a typo. When you use developer it matches.

–
lskierkowski
www.bluesoft.net.pl

3

Hi,

compare the name space of Broker document type and handling service .

Regards,
Saravanan.E

4

Hi,

Could you share your code somewhere? I look at it and test it on my environment. In such cases the problem has always been caused by a simple mistake.

–
lskierkowski
www.bluesoft.net.pl

5

Hi, I really (really!) appreciate Your answers.

I have checked map (one field is not mapped for now), but mapping looks good to me.

Broker document type has no namespace and handling services too.

I have attached exported packages with source needed.
In GsKolektor You will find publishable document type and in the other one source.

With Best Regards,
GOLAN.
GsServices.zip (58.5 KB)
GsKolektor.zip (4.9 KB)

6

Hi,

I think that solution is very simple. Your trigger service using a document reference which name is ‘Billing’ and when you run this with developer everything is all right. But when you want to use trigger your service should meet some requirements:

  • the name for this document reference must be the fully qualified name of the publishable document type
  • the input signature for the trigger service needs to have a document reference to the publishable document type

Your input should look like this:

[ATTACH=CONFIG]863[/ATTACH]

When you change the input signature and adjust your mapping it should work fine.

–
lskierkowski
www.bluesoft.net.pl
input.jpg

7

Thank you very much, it solves my problem : )

It turns out that my eyes was on other problem when I was looking for an answer - and information about service input signature is located in 7-1-1_Publish_Subscribe_Developers_Guide.pdf on page 112.

Again, thank You : )))

With Best Regards,
GOLAN.

edit:
btw, it looks like realisation of processes on IS is possibly hardcoded somewhere…

8

how can i set common name space for configuration file which is going to invoked by service
for example insted of specifying
C:\webMethods7\IntegrationServer\packages\FRX_JRS_Veeva_Subscribe\config\FRX_JRS_Veeva_Subscribe_config.xml

as

/frx/ESB/FRX_JRS_Veeva_Subscribe_Config.xml

post me the replies