Hi,

I've a requirement like in datapower we need to add one extra filed like<attachmentfile>(filed is not in WSDL which is shared by backend team ) to my request  and will share it with front end team(front end service is a rest service) and they will send an attachment in base-64 in that filed send it to datapower. Moreover, within datapower we need to extract that base-64 content and send as an attachment(out of body as backend will have a performance issues) to backend vice versa.

Any prompt help would be greatly appreciated!

Thanks,

Venkateswarlu K.

------------------------------
kandukuri venkateswarlu
------------------------------

Hi,

I've a requirement like in datapower we need to add one extra filed like<attachmentfile>(filed is not in WSDL which is shared by backend team ) to my request  and will share it with front end team(front end service is a rest service) and they will send an attachment in base-64 in that filed send it to datapower. Moreover, within datapower we need to extract that base-64 content and send as an attachment(out of body as backend will have a performance issues) to backend vice versa.

Any prompt help would be greatly appreciated!

Thanks,

Venkateswarlu K.

------------------------------
kandukuri venkateswarlu
------------------------------

Hi Kandukuri,

Based upon the email you sent me directly for this, I'm providing my answer here in the forum.

Its difficult to say what your issue is without also seeing your JSON payload whose schema must match the code you've written, but just a few notes I made in evaluating your code you provided:

1. Typically the root body of the multipart form is the SOAP message.   Looks like you have the SOAP message as the last part which to me is unusual.
2. I don't see an ending boundary string with the suffix of two hyphens that follow to indicate the end of attachments after the last part of the form.
3. As for the attachments themselves, again I don't have the sample request JSON to look at to compare to what the code is doing, but for the following code

                                var attachmentList = inputJson.ELRASubmitDetailsRequest.AttachmentList.Attachment;

                                var v2 = '';

                                if ( attachmentList && attachmentList.length > 0) {

The accuracy of this code will depend on what the input JSON schema is.   Is the property "AttachmentList" a parent object of property "Attachment" that is an array of objects, and within each Attachment object are properties that are named Attachment* including AttachmentNotes?  The code

v2 += '<v1: >' + attachment.AttachmentNotes + '</v1:AttachmentNotes>' + crlf;

is missing the local name in the start tag.  That appears fixed based on the screen shot you provided, but the code you provided isn't correct.  Assuming you fixed that and provided a back level code sample, then I'd expect you'd either get <v1:AttachmentNotes>undefined</v1:AttachmentNotes> or an element with the actual value filled in.  Given you have nothing in your output, it is as if the input property value is an empty string.  What is AttachmentNotes anyway? Is that just a string value which could be an empty string?  If so the code should check for the presence of this property to ensure that you don't get a value of undefined when the property doesn't exist.  The code appears to indicate that the actual base-64 content is not in attachment.AttachmentNotes but in attachment.AttachmentContent.  Typically, I'd expect you would base64 decode this before placing it in the multipart form, but I don't see that happening either.   I see the following:

                                                                                //v2 += '<v1:AttachmentContent>' + attachment.AttachmentContent + '</v1:AttachmentContent>' + crlf;

So you've commented this out for now, and you aren't getting the base64 content put into your output for now, but you probably will want to also base-64 decode this.  Given the need to do the decode to place the actual file payload is required, for a .pdf it will most probably have binary data and you may need to use buffer objects instead of strings as the concatenation of the content would take any binary content, even if in a buffer, and would change the encoding of that content to be utf-8 which would change your binary data characters and make the pdf unusable, so just be warned when you get to that point.

So overall, I'm just speculating on the code since I don't know the actual schema of your input JSON data, but the above are just some observations from what you've provided.

Since you're in a MPGW, the best friend of a GatewayScript code developer is the GatewayScript debugger.  Please see more information on it at https://www.ibm.com/docs/en/datapower-gateway/10.5.0?topic=gatewayscript-debuggers.  To enable, you must have in your GatewayScript code a debugger; statement.  This will be your first breakpoint to pause your code execution that must be in the main execution path of the code.   You must also have enabled the GatewayScript debugger for the GatewayScript action you are executing.   Then the actual debugging is done in one of two ways

1. Using the DataPower CLI. You must be in your application domain in configuration mode, issue the show debug command and using the session id in that result, issue a debug <sessionid> command.
2. Using the remote debugger which requires the remote debugger to be enabled and using the chrome browser, configuring chrome://inspect/#devices to listen for GatewayScript code that is paused in the debugger. Selecting the transaction from the list shown will provide you the code, list of variables to that point, etc.

Either way, you can set breakpoints, change values of variables in your code before you execute code that would use that variable if you see that the variable value is currently incorrect which would allow you to continue debugging despite a code defect you know you need to fix but don't want to terminate your debugging session, step into and out of functions, etc.   I'd strongly recommend that you get very familiar with the debugger to help you.

Best Regards,
Steve

Hi,

I've a requirement like in datapower we need to add one extra filed like<attachmentfile>(filed is not in WSDL which is shared by backend team ) to my request  and will share it with front end team(front end service is a rest service) and they will send an attachment in base-64 in that filed send it to datapower. Moreover, within datapower we need to extract that base-64 content and send as an attachment(out of body as backend will have a performance issues) to backend vice versa.

Any prompt help would be greatly appreciated!

Thanks,

Venkateswarlu K.

------------------------------
kandukuri venkateswarlu
------------------------------

Hi Kandukuri,

Based upon the email you sent me directly for this, I'm providing my answer here in the forum.

Its difficult to say what your issue is without also seeing your JSON payload whose schema must match the code you've written, but just a few notes I made in evaluating your code you provided:

1. Typically the root body of the multipart form is the SOAP message.   Looks like you have the SOAP message as the last part which to me is unusual.
2. I don't see an ending boundary string with the suffix of two hyphens that follow to indicate the end of attachments after the last part of the form.
3. As for the attachments themselves, again I don't have the sample request JSON to look at to compare to what the code is doing, but for the following code

                                var attachmentList = inputJson.ELRASubmitDetailsRequest.AttachmentList.Attachment;

                                var v2 = '';

                                if ( attachmentList && attachmentList.length > 0) {

The accuracy of this code will depend on what the input JSON schema is.   Is the property "AttachmentList" a parent object of property "Attachment" that is an array of objects, and within each Attachment object are properties that are named Attachment* including AttachmentNotes?  The code

v2 += '<v1: >' + attachment.AttachmentNotes + '</v1:AttachmentNotes>' + crlf;

is missing the local name in the start tag.  That appears fixed based on the screen shot you provided, but the code you provided isn't correct.  Assuming you fixed that and provided a back level code sample, then I'd expect you'd either get <v1:AttachmentNotes>undefined</v1:AttachmentNotes> or an element with the actual value filled in.  Given you have nothing in your output, it is as if the input property value is an empty string.  What is AttachmentNotes anyway? Is that just a string value which could be an empty string?  If so the code should check for the presence of this property to ensure that you don't get a value of undefined when the property doesn't exist.  The code appears to indicate that the actual base-64 content is not in attachment.AttachmentNotes but in attachment.AttachmentContent.  Typically, I'd expect you would base64 decode this before placing it in the multipart form, but I don't see that happening either.   I see the following:

                                                                                //v2 += '<v1:AttachmentContent>' + attachment.AttachmentContent + '</v1:AttachmentContent>' + crlf;

So you've commented this out for now, and you aren't getting the base64 content put into your output for now, but you probably will want to also base-64 decode this.  Given the need to do the decode to place the actual file payload is required, for a .pdf it will most probably have binary data and you may need to use buffer objects instead of strings as the concatenation of the content would take any binary content, even if in a buffer, and would change the encoding of that content to be utf-8 which would change your binary data characters and make the pdf unusable, so just be warned when you get to that point.

So overall, I'm just speculating on the code since I don't know the actual schema of your input JSON data, but the above are just some observations from what you've provided.

Since you're in a MPGW, the best friend of a GatewayScript code developer is the GatewayScript debugger.  Please see more information on it at https://www.ibm.com/docs/en/datapower-gateway/10.5.0?topic=gatewayscript-debuggers.  To enable, you must have in your GatewayScript code a debugger; statement.  This will be your first breakpoint to pause your code execution that must be in the main execution path of the code.   You must also have enabled the GatewayScript debugger for the GatewayScript action you are executing.   Then the actual debugging is done in one of two ways

1. Using the DataPower CLI. You must be in your application domain in configuration mode, issue the show debug command and using the session id in that result, issue a debug <sessionid> command.
2. Using the remote debugger which requires the remote debugger to be enabled and using the chrome browser, configuring chrome://inspect/#devices to listen for GatewayScript code that is paused in the debugger. Selecting the transaction from the list shown will provide you the code, list of variables to that point, etc.

Either way, you can set breakpoints, change values of variables in your code before you execute code that would use that variable if you see that the variable value is currently incorrect which would allow you to continue debugging despite a code defect you know you need to fix but don't want to terminate your debugging session, step into and out of functions, etc.   I'd strongly recommend that you get very familiar with the debugger to help you.

Best Regards,
Steve

Hi,

I've a requirement like in datapower we need to add one extra filed like<attachmentfile>(filed is not in WSDL which is shared by backend team ) to my request  and will share it with front end team(front end service is a rest service) and they will send an attachment in base-64 in that filed send it to datapower. Moreover, within datapower we need to extract that base-64 content and send as an attachment(out of body as backend will have a performance issues) to backend vice versa.

Any prompt help would be greatly appreciated!

Thanks,

Venkateswarlu K.

------------------------------
kandukuri venkateswarlu
------------------------------

Hi Kandukuri,

Thanks for sending the sample input data which has ...

        "AttachmentList": {            "Attachment": [                {                    "AttachmentID": 57,                    "AttachmentRequestId": 10,                    "AttachmentLinkID": 49,                    "AttachmentNotes": "",                    "AttachmentType": "PDF",                    "AttachmentContent":"base64 encoded content"                                    },                {                    "AttachmentID": 58,                    "AttachmentRequestId": 11,                    "AttachmentLinkID": 50,                    "AttachmentNotes": "",                    "AttachmentType": "JPG"                }            ]        },

Indeed AttachmentNotes is an empty string which is why your XML is created for that element as <v1:AttachmentNotes></v1:AttachmentNotes> which is correct.  If that XML element isn't required, you could test for that JSON property to not be undefined and not an empty string before adding the element to your XML string.

Otherwise my previous comments still apply and I'd suggest you investigate the new attachment functions link that I provided in my previous post as it will save you the work of building the multipart form yourself.  I don't have cycles to do a prototype of those functions myself, but we've had numerous threads in this and the API Connect forum concerning building multipart forms and these functions were an enhancement to meet that requirement.

Best Regards,

Steve

Hi Kandukuri,

Based upon the email you sent me directly for this, I'm providing my answer here in the forum.

Its difficult to say what your issue is without also seeing your JSON payload whose schema must match the code you've written, but just a few notes I made in evaluating your code you provided:

1. Typically the root body of the multipart form is the SOAP message.   Looks like you have the SOAP message as the last part which to me is unusual.
2. I don't see an ending boundary string with the suffix of two hyphens that follow to indicate the end of attachments after the last part of the form.
3. As for the attachments themselves, again I don't have the sample request JSON to look at to compare to what the code is doing, but for the following code

                                var attachmentList = inputJson.ELRASubmitDetailsRequest.AttachmentList.Attachment;

                                var v2 = '';

                                if ( attachmentList && attachmentList.length > 0) {

The accuracy of this code will depend on what the input JSON schema is.   Is the property "AttachmentList" a parent object of property "Attachment" that is an array of objects, and within each Attachment object are properties that are named Attachment* including AttachmentNotes?  The code

v2 += '<v1: >' + attachment.AttachmentNotes + '</v1:AttachmentNotes>' + crlf;

is missing the local name in the start tag.  That appears fixed based on the screen shot you provided, but the code you provided isn't correct.  Assuming you fixed that and provided a back level code sample, then I'd expect you'd either get <v1:AttachmentNotes>undefined</v1:AttachmentNotes> or an element with the actual value filled in.  Given you have nothing in your output, it is as if the input property value is an empty string.  What is AttachmentNotes anyway? Is that just a string value which could be an empty string?  If so the code should check for the presence of this property to ensure that you don't get a value of undefined when the property doesn't exist.  The code appears to indicate that the actual base-64 content is not in attachment.AttachmentNotes but in attachment.AttachmentContent.  Typically, I'd expect you would base64 decode this before placing it in the multipart form, but I don't see that happening either.   I see the following:

                                                                                //v2 += '<v1:AttachmentContent>' + attachment.AttachmentContent + '</v1:AttachmentContent>' + crlf;

So you've commented this out for now, and you aren't getting the base64 content put into your output for now, but you probably will want to also base-64 decode this.  Given the need to do the decode to place the actual file payload is required, for a .pdf it will most probably have binary data and you may need to use buffer objects instead of strings as the concatenation of the content would take any binary content, even if in a buffer, and would change the encoding of that content to be utf-8 which would change your binary data characters and make the pdf unusable, so just be warned when you get to that point.

So overall, I'm just speculating on the code since I don't know the actual schema of your input JSON data, but the above are just some observations from what you've provided.

Since you're in a MPGW, the best friend of a GatewayScript code developer is the GatewayScript debugger.  Please see more information on it at https://www.ibm.com/docs/en/datapower-gateway/10.5.0?topic=gatewayscript-debuggers.  To enable, you must have in your GatewayScript code a debugger; statement.  This will be your first breakpoint to pause your code execution that must be in the main execution path of the code.   You must also have enabled the GatewayScript debugger for the GatewayScript action you are executing.   Then the actual debugging is done in one of two ways

1. Using the DataPower CLI. You must be in your application domain in configuration mode, issue the show debug command and using the session id in that result, issue a debug <sessionid> command.
2. Using the remote debugger which requires the remote debugger to be enabled and using the chrome browser, configuring chrome://inspect/#devices to listen for GatewayScript code that is paused in the debugger. Selecting the transaction from the list shown will provide you the code, list of variables to that point, etc.

Either way, you can set breakpoints, change values of variables in your code before you execute code that would use that variable if you see that the variable value is currently incorrect which would allow you to continue debugging despite a code defect you know you need to fix but don't want to terminate your debugging session, step into and out of functions, etc.   I'd strongly recommend that you get very familiar with the debugger to help you.

Best Regards,
Steve

Hi,

I've a requirement like in datapower we need to add one extra filed like<attachmentfile>(filed is not in WSDL which is shared by backend team ) to my request  and will share it with front end team(front end service is a rest service) and they will send an attachment in base-64 in that filed send it to datapower. Moreover, within datapower we need to extract that base-64 content and send as an attachment(out of body as backend will have a performance issues) to backend vice versa.

Any prompt help would be greatly appreciated!

Thanks,

Venkateswarlu K.

------------------------------
kandukuri venkateswarlu
------------------------------

Hi,

I've a requirement like in datapower we need to add one extra filed like<attachmentfile>(filed is not in WSDL which is shared by backend team ) to my request  and will share it with front end team(front end service is a rest service) and they will send an attachment in base-64 in that filed send it to datapower. Moreover, within datapower we need to extract that base-64 content and send as an attachment(out of body as backend will have a performance issues) to backend vice versa.

Any prompt help would be greatly appreciated!

Thanks,

Venkateswarlu K.

------------------------------
kandukuri venkateswarlu
------------------------------