I have imported app build starting point zip in my Linux lite VM .I was trying to understand the Front stage application case life cycle .
In the Hotel case type,after entering all information ,as per the flow,Hotel proxy case gets created ,through pega's rest API(Post method).
I am getting HTTP 500 error code from rest connector and not able to create Hotel proxy case .
the HTTP response code of 500 indicated a server error. The response data may contain a reason. // The body of the service's response, which is set up for mapping in the Connector rule, was empty for this service call.
The Hotel application is not meant to be run standalone in Production. The only Production application is the the Booking application. The Booking application is built on the Hotel application which is built on the FSGEmail application which is built on the FSG application.
The FSGEmail "component" application is self-testable. The Hotel "component" application is supposed to be self-testable as well -- it was originally. Unfortunately the app build exam starting-point Booking application introduced a bug.
You could trace the Pega API "cases" REST service to see why it returns HTTP 500 but there is no point in doing so. The 8.3.1 version of the Hotel and Hotel Proxy application will have a shared Component, one ruleset that contains the FSG-Data-Hotel-RoomsRequest class and a second ruleset that contains the shared REST connector's class.
Again, the Hotel application is not meant to used standalone. In Production the Hotel case is only supposed to used as a subcase - asking a specific hotel to reserve rooms for an event.