415 Error while invoking createcase API

[subbanna girish]

I am invoking the createcase API using REST Plugin from BW and in the response 415 message code. But in BPM logs i see the below error

20 Apr 2016 03:18:21,051 [httpConnector_30] [WARN ] org.apache.cxf.jaxrs.utils.JAXRSUtils - No operation matching request path "/bpm/rest//globaldata/model/com.example.firstproject.Profile/1/create" is found, Relative Path: /model/com.example.firstproject.Profile/1/create, HTTP Method: POST, ContentType: text/plain, Accept: application/json,. Please enable FINE/TRACE log level for more details.

Please advise the resolution steps

Thanks

[Balakrishnan Balasubramanian]

Looks like you are invoking a REST API (vai HTTP POST) by specifying a wrong Content-type - text/plain.

 

You should specifyapplication/json orapplication/xml (as per the requirement) as mentioned here.

[subbanna girish]

Thanks Balakrishnan. I have modified the settings and tried again. can you please look into the other query i raise couple of days back

 

Need help to create structure in TIBCO Streambase

 

 

[subbanna girish]

Hi Balakrishnan,

 

I have deployed the process with the name RecieveRequest which as startevent set to Message.when i try to invoke thru REST API i see the below error.Please advise

 

Error locating the pageflow with name [RecieveRequest][com.tibco.n2.pfe.internal.exception.PageFlowExecutionException: Error locating the pageflow with name [RecieveRequest]]`, componentClassName=`com.tibco.n2.busserv.services.impl.BusinessServiceImpl`, requestReceived=`2017-04-22T17:56:38.487Z`, hostAddress=`10.0.0.18`, nodeName=`BPMNode`, eventType=`FAULT`, messageCategory=`PAGE_FLOW`, componentId=`PFE`, stackTrace=`com.tibco.n2.busserv.services.InternalServiceFault: com.tibco.n2.pfe.internal.exception.PageFlowExecutionException: Error locating the pageflow with name [RecieveRequest][com.tibco.n2.pfe.internal.exception.PageFlowExecutionException: Error locating the pageflow with name [RecieveRequest]]

[Balakrishnan Balasubramanian]

Did setting the correct Content-type solve the problem If yes, please vote up the right answer so that it may be helpful for others. 

[GanapathiK -]

Yes, this solves my error. I was facing the same error and solved this after adding header field Content-Type as 'application/xml'. Thanks