Managing IPF instances
An IPF instance is a running installation of an IPF version. To manage IPF instances, select and use the toolbar options. These tasks are performed on the IPF Instances tab:
- Create an IPF instance
- Delete an IPF instance
Creating an IPF instance
The IPF Instances tab lists the running instances of the IPF architecture.
IPF instances must be added after an IPF version update, as explained in the portal installation guide. Adding an IPF instance creates an entry in the IPFControl Database in a Locked state and creates the asynchronous Deploy_IPFInstance, which completes setup of the IPFinstance on all servers in the farm.
The farm status indicates that an update is in progress. When complete, the Farm Manager indicates that the farm has been updated, and the IPFinstance is unlocked.
The end result is that an IIS WebApp pool has been created with a single site and the IPF web application files have been deployed to an IIS subdirectory.
You can add a new IPF instance to test it out while your current IPF version is still being used by production portals.
Deleting an IPF instance
This action is hot safe.
You can delete an IPF instance only if no portals are configured to use it.
The IPF instance is changed to the Locked state in the IPFControl Database and creates the asynchronous Retract_IPFInstance, which completes the removal of the IPFinstance from all servers in the farm
The IPFinstance status indicates that an update is in progress. When complete, the Farm Manager indicates that the IPFInstance has been deleted.
The end result is that the IIS WebApp pool and site have been deleted along with the IIS subdirectory for this site.