Categories
- All Categories
- 164 Oracle Analytics News
- 30 Oracle Analytics Videos
- 14.8K Oracle Analytics Forums
- 5.7K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 56 Oracle Analytics Trainings
- 13 Oracle Analytics Data Visualizations Challenge
- 4 Oracle Analytics Career
- 2 Oracle Analytics Industry
- Find Partners
- For Partners
BIP API ScheduleService states ftpOptions element ftpUserName is unexpected but matches WSDL

This ca be ignored, I would delete it if I could. I kept overlooking some typos.
Trying to use BI Publihser API ScheduleService, but response staes the ftpOptions item element contains an unexpected element ftpUserName, even though it matches WSDL. I am doing this from Postman, and there may be a error in my XML that I am overlooking that might be the root cause. As far as I see the request matches the WSDL definition, and I actually can't find a single example online that uses the ftp delivery option. Any suggestions would be apricated.
endpoint example: https://<host>/xmlpserver/services/v2/ScheduleService
The fault string: Unmarshalling Error: unexpected element (uri:"http://xmlns.oracle.com/oxp/service/v2", local:"ftpUserName"). Expected elements are (none)
Apologize for the lack of formatting, but this form removed the formatting. Values of elements have been changed to fake values.1
Full Request:
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:v2="http://xmlns.oracle.com/oxp/service/v2"> <soapenv:Header/> <soapenv:Body> <v2:scheduleReport> <v2:scheduleRequest> <v2:deliveryChannels> <v2:ftpOptions> <v2:item> <v2:ftpServerName>ftp.NotReal.com</v2:ftpServerName> <v2:ftpUserName>NotReal<v2:ftpUserName> <v2:ftpUserPassword>NotReaal<v2:ftpUserPassword> <v2:remoteFile>test.pdf<v2:remoteFile> <v2:sftpOption>true<v2:sftpOption> </v2:item> </v2:ftpOptions> </v2:deliveryChannels> <v2:notificationTo>NOTREAL@NOTREAL.com</v2:notificationTo> <v2:notificationUserName>fakeUserName</v2:notificationUserName> <v2:notifyHttpWhenWarning>true</v2:notifyHttpWhenWarning> <v2:notifyWhenFailed>true</v2:notifyWhenFailed> <v2:notifyWhenSuccess>true</v2:notifyWhenSuccess> <v2:notifyWhenWarning>true</v2:notifyWhenWarning> <v2:reportRequest> <v2:attributeFormat>pdf</v2:attributeFormat> <v2:attributeTemplate></v2:attributeTemplate> <v2:reportAbsolutePath>/Test/TestReport.xdo</v2:reportAbsolutePath> </v2:reportRequest> <v2:saveDataOption>true</v2:saveDataOption> <v2:scheduleBurstingOption>true</v2:scheduleBurstingOption> <v2:scheduleBurstringOption>true</v2:scheduleBurstringOption> <v2:userJobName>JOB_TestReport</v2:userJobName> </v2:scheduleRequest> <v2:userID>NOT REAL USER ID</v2:userID> <v2:password>NOT REAL PASSWORD</v2:password> </v2:scheduleReport> </soapenv:Body></soapenv:Envelope>
Response
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"> <soapenv:Body> <soapenv:Fault> <faultcode>soapenv:Client</faultcode> <faultstring>Unmarshalling Error: unexpected element (uri:"http://xmlns.oracle.com/oxp/service/v2", local:"ftpUserName"). Expected elements are (none) </faultstring> </soapenv:Fault> </soapenv:Body></soapenv:Envelope>
Best Answer
-
I found my typos, working tired does not pay, XML Syntax error helps if close your tags correctly. Kept overlooking it.
0
Answers
-
0
-
We are using cloud.
We are in the progress of migrating. Oddly if we just send the exact request, we were sending to On-Prem OBIEE, the schedule request is successful even though that request uses localOptions for delivery which, as expected, fails to deliver when report runs. Change the request to use ftpOptions for delivery and we get the unexpected element.
Also, if I purposefully use an element name that I know is wrong, for example userName rather than ftpUserName, the error response lists the expected elements, which include ftpUserName.
Unmarshalling Error: unexpected element (uri:"http://xmlns.oracle.com/oxp/service/v2", local:"userName"). Expected elements are <{http://xmlns.oracle.com/oxp/service/v2}remoteFile>,<
{http://xmlns.oracle.com/oxp/service/v2}ftpServerName>,<{http://xmlns.oracle.com/oxp/service/v2}ftpUserName>,<{http://xmlns.oracle.com/oxp/service/v2}ftpUserPassword>,<{http://xmlns.oracle.com/oxp/service/v2}sftpOption>
Thank you for the response.
1 -
0
-
Yes, it resolved the issue.
Thank you,
0