Program guide > (deprecated) Partitioning facility > Partitioning facility programming > Partitioned EJB overview

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

Partitioning facility restrictions

Partition names must be cluster unique

Cluster scoped partition names must be unique within the cluster they are hosted within. For example, if a partitioned Java™ 2 Platform Enterprise Edition (J2EE) application creates a partition named PartitionX, another application in the same cluster cannot create another partition with the same name.

Use the PartitionManager.getApplicationName() interface, and, if carefully used (specifically, do not use long strings), it can prepend the partition name with a deployed application name to the partition name. For example, assume the administrator deployed the application with App45v1r2, the createPartitionDefinition(....) API could prepend the App45v1r2 to PartitionX, and create a partition named "App45v1r2_PartitionX."

Node scoped partition names within the same application will be the same for each application on each logical node, but node scoped partition names across different partitioned applications need to be unique.

Other restrictions

Please refer to each partitioning facility (WPF) subsystem to review specific restrictions (such as the Proxy DataSource).

Parent topic:

Partitioned EJB overview

Related concepts

Partitioned EJB overview

z/OSzOS restrictions in WPF