Specifying alternative extensions directoriesAdded by IBM on May 5, 2011 | Version 1 (Original)
|You can optionally specify alternative extensions directories that tell the IBM® Forms Server – Forms Services Platform where to look for extra JAR and .properties files start up. Tags: specifying, bundle directories, start up, reading: JAR files, reading: properties files, reading, properties files: startup, JAR files: startup, FSP, 18.104.22.168, developing, 22.214.171.124
You can optionally specify alternative extensions directories that tell the IBM® Forms Server – Forms Services Platform where to look for extra JAR and .properties files start up.
Specifying alternative extensions directories overwrites the Forms Services Platform's extensions
directory. In other words, if you specify alternative extensions directories, <Install directory>\extensions
To specify alternative extensions directories:
- Open fsp.properties.
Note: If deployed in WebSphere® Application Server as a servlet, fsp.properties is located in <WAS profile directory>\installedApps\<cellname>\wfsp.ear\wfsp.war\WEB-INF\classes.
In standalone mode, fsp.properties is located in <Install directory>\ServicesPlatform\redist\standalone.
- Edit the file to include your extension directory.
For example, if you want the Forms Services Platform to look for extra JAR and properties files in the C:\solutions\myExtensions
directory, you would type:
- Save and close the file.
- (In standalone mode only.) Add fsp.properties to your class path.
After you add this file to your class path, the Forms Services Platform will look for extra JAR and properties files in the directories you specified in fsp.properties.
- Restart your server.
Parent topic: Installing Forms Services Platform and setting up your environment