Installation and Upgrade > Installing and Configuring PTC FlexPLM > Modifying Configuration Files for Development, Testing, and Production > Configuring PTC FlexPLM for Cluster Configuration and Multiple PTC Embedded Servlet Engine Instances > LoadBalancer and Multiple Servlet Engine Configuration
  
LoadBalancer and Multiple Servlet Engine Configuration
For PTC FlexPLM 10.1 and later releases, Embedded Servlet Engine runs embedded within the method server. For each new Embedded Servlet Engine server that you need, add one new method server.
In all releases of PTC FlexPLM, it is standard practice to run an Embedded Servlet Engine instance for every method server that you are running. Now that Embedded Servlet Engine is embedded in the method server, only add new method server instances to gain a new Embedded Servlet Engine instance.
PTC FlexPLM also requires you to enable sticky bits or sessions for Embedded Servlet Engine or the loadbalancer being used, so you can bind a client machine to a particular Embedded Servlet Engine instance. This binding ensures that the client session information is preserved and accessible during interaction with the application.
In Windchill 10.1 and later releases, sticky session mode is already set by the AJP worker in PTC HTTP Server as a stickysession for each Embedded Servlet Engine instance. If you are using a loadbalancer, ensure that stickysession is also enabled.