Constellation tips: how to reference a custom http header included in a dxapi call

General
, , , ,
1

When a custom http header is useful?
for example, a user make a ticket order using mobile app…the fron end server, which interact with mobile app, generate unique interaction_id for each request from mobile apps and log invocation message with the interaction_id…in some situation, the front end server will delegate end user’s request to the back end server (Pega) via dx api call and append interaction_id to the custom http header…the back end server (Pega) also generates invocation log message containing interaction_id so that developers can trouble shoot by matching interaction_id in log messages in both front and back end system…

you can use below Java code to reference a custom http header included in a dxapi call.

custom-http-header-java.png
custom-http-header-java.png2871×1421 329 KB

javax.servlet.http.HttpServletRequest vRequest = (javax.servlet.http.HttpServletRequest) tools.getRequestor().getRequestorPage().getObject("pxHTTPServletRequest");
if (vRequest != null) {
  myHttpHeader = vRequest.getHeader("X-MyHttp-Header");
  if (myHttpHeader != null) {
    tools.getRequestor().getRequestorPage().getProperty(".pyHTTPRequestHeaders.myHttpHeader").setValue(myHttpHeader);
  }
}
2
[Change of support from Tomcat 9 to Tomcat 10.1.x](https://docs.pega.com/bundle/platform/page/platform/deployment/client-managed-cloud/prereq-pega-platform-25.html)
Starting in Pega Platform '25, Pega only supports deploying on Tomcat 10.1.x. The change in support from previous releases is due to the lack of backward compatibility between Tomcat 9.x and 10.1.x. Tomcat 10.1.x made the [transition from Java EE 8 to Jakarta EE 9](https://blogs.oracle.com/javamagazine/post/transition-from-java-ee-to-jakarta-ee), and, as a result, Tomcat 10.1 is Jakarta EE 9 compatible. __The primary package structure for J2EE library APIs has changed from `javax.*` to `jakarta.*`__. Pega Platform '25 uses Jakarta EE 9, so deployment on Tomcat 9.x is no longer possible. Running applications on Tomcat 10.1 requires updates to Rules and JAR libraries stored in the database. Before updating Pega Platform, it is critical that you review the impacted Rules and ensure that your custom CodeSets and JARs are compatible with the new environment. For more information, see [Updating Pega Platform to Tomcat 10.1](https://docs.pega.com/bundle/platform/page/platform/deployment/tomcat-10-prepare-overview.html).