Program guide > (deprecated) Partitioning facility > z/OSzOS platform considerations > z/OSzOS restrictions in WPF


Deprecated feature: The partitioning facility (WPF) feature is deprecated. You can configure partitioning with WebSphere eXtreme Scale.


WPF programming pattern in z/OSzOS

This article describes the partitioning facility (WPF) programming pattern in Extended Deployment for z/OS v6.0.1.

Since the WPF-WLM Internet Inter-ORB Protocol (IIOP) routing is not supported in Extended Deployment for z/OS v6.0.1, applications must handle their partition routing using the Java™ Message Service (JMS) technology or other mechanisms.

The Java Message Service (JMS) based routing mechanism is illustrated in the following figure. Two requests are shown, request 1 and request 2. Notice that each request must go to a designated JMS topic/queue for a partition routing. The JMS topic/queue should forward the request to the target partition, which prepares to process the request and sends the response to a designated JMS topic/queue for routing responses. Though the execution steps are the same, the order of request execution is not guaranteed since many factors depend on execution, including machine location, server performance, and the network setup.

The request routes for request 1 (1-1.3) and request 2 (2-2.3) are shown in the following graphic, resulting in the Appclient getting responses (3).

JMS based routing mechanism

The following steps describe the route of request 1. Note that for request 2 or any other request follows this same route. Each request execution is independent from each other and the order in which they are received is not guaranteed.


Parent topic:

z/OSzOS restrictions in WPF


Related concepts

z/OS restrictions in WPF