Application Server version 8.0, 184.108.40.206 and 220.127.116.11 CF1 only, the administrative user (wsadmin) must have read/write access to c:\NitroUser_Temp\WEB-INF in Windows, or /NitroUser_Temp/WEB-INF in Unix. If wsadmin does not have access, the initial setup fails on step 3. If these directories do not exist, create them with the appropriate read/write access and then rerun the
Forms Experience Builder setup in the web browser.
1. To set up the DB2
a. Create an empty DB2
database with a maximum database name of eight characters, and a maximum page size of 32768.
For example, a sample command is: db2"CREATE DB FEBDB using codeset UTF-8 territory us PAGESIZE 32768".
b. Connect to the database and create a User Temporary Table Space.
Use the following settings for the temporary table space:
- Large_usertemp pagesize 32K
- Managed by automatic storage extentsize 16
- Bufferpool LARGE_BUFFER_POOL. "LARGE_BUFFER_POOL" is the name of your DB2 large buffer pool. Each DB2 server may have a different name. For example, a sample command is: db2"CREATE USER TEMPORARY TABLESPACE LARGE_USERTEMP PAGESIZE 32k MANAGED BY AUTOMATIC STORAGE EXTENTSIZE 16 PREFETCHSIZE 16 BUFFERPOOLbufferpool-name"
2. To deploy Forms Experience Builder to WebSphere
Application Server, open the WebSphere
Application Server Administrative console.
3. Configure the data sources. Depending on your version of WebSphere
Application Server, go to either:
- Resources or
- Application server
a. Expand the JDBC tree, and go to Data sources
- Create a new data source
- Provide the host name, port, database name, connection ID, and password. The connection ID must have dbadmin access granted for the database.
- If you are connecting to a DB2 database with WebSphere Application Server 8.0 Connection pool data source, ensure that you select a non-XA DB2 JDBC provider, and use a Type 4 driver when configuring the data source.
- Click Test connection to ensure that the connection is made.
b. You must set additional properties for the created data source.
- Click the name link for the created data source, then click Custom Properties.
- Locate "fullyMaterializeLobData", and change the value to false.
- Add a property called "progressiveStreaming", and set the value to 2.
- Set the "webSphereDefaultIsolationLevel" to 2.
Note: If you expect a high volume of users, set the default value of Maximum connections to 50.
4. Go to Mail
-> Mail sessions
- Select the correct scope and choose New.
- Choose Built-in Mail Provider.
- Provide a name, and a JNDI Name.
- Depending on your version of WebSphere Application Server, you might need to click Apply before setting the following properties.
- Complete the Outgoing Mail Properties.
- Set the Server, and Return email address fields.
- Click OK
5. Go to Application Servers
-> Java and Process Management
-> Process definition
-> Java Virtual Machine
, and set the default maximum heap size to at least 512 MB.
6. Deploy the Forms Experience Builder EAR:
a. Go to Applications
-> Application Types
-> WebSphere Enterprise Applications
b. Select Install
c. Select Local file system
, provide the location of the EAR file, and click Next
For example: <Installation Directory>/deploy/ibm-experience-builder.ear.
d. From the "How do you want to install the application?"
options, select Detailed
, then click Next
e. If you are using a server other than server1, then you will need to bind the application to the server in step 2. Click the forms and forms-basic applications checkboxes, select the server you want to deploy to and then click Apply
f. Accept the defaults presented by clicking Next
for all steps until Map resource references to resource
g. On Map resource references to resource
- In the javax.mail.Session section, go to Target Resource JNDI Name, and select the mail source.
- In the javax.sql.DataSource section, go to Target Resource JNDI Name, and select the data source.
h. Click Next
i. Accept the defaults for the next step and click Next
j. On Map context roots for web modules
use the default context roots, and click Next
k. On Map security roles to users or groups
- Select the EditApplicationUsers role, and click Map Special Subjects. Select either All authenticated in Application’s Realms, or All authenticated in Trusted Realms to map the value to the role. If both options are available, select All authenticated in Trusted Realms.
- Select the AdministrativeUsers role, and click Map Users... or Map Groups.... Select the administrative users or groups to map to the role.
- Select the UseApplicationUsers role, and click Map Special Subjects. Select either All authenticated in Application’s Realms, or All authenticated in Trusted Realms to map the value to the role. If both options are available, select All authenticated in Trusted Realms.
Additional information about available roles:
You must map Administrative users and Edit Application users to an appropriate realm.
- AdministrativeUsers – Administrative users are able to set up the Forms Experience Builder server. You must have an Administrative User to complete the installation process as described in Completing the installation. A sample setting is: "Special subject: None, Mapped users, admin_user_name".
- EditApplicationUsers – Authenticated users that can design, deploy, and use Forms Experience Builder applications. A sample setting is: "Special subject: All authenticated in Application’s Realms".
- UseApplicationsUsers – Authenticated users that can use deployed Forms Experience Builder applications. All users in the AdministrativeUsers, and EditApplicationUsers automatically have access to use deployed applications. Only adjust this setting if you want to allow a broader set of users than those listed in the AdministrativeUsers, and EditApplicationUsers roles. Otherwise, leave this role unmapped. A sample setting, if you must map the role, is: "Special subject: All authenticated in Trusted Realms".
l. Continue to the summary page.
m. Click Finish
to deploy the ear file.
7. Set the class loading and update detection:
a. Go to Enterprise Applications -> Forms Experience Builder -> Class loader .
b. Go to Class loader order and select "Classes loaded with local class loader first (parent last)".
c. Go to Enterprise Applications -> Forms Experience Builder -> Manage Modules -> IBM Forms Experience Builder xxx.war.
d. Go to Class loader order and select "Classes loaded with local class loader first (parent last)"
e. Click Apply to apply changes.
8. Enabling security:
a. Expand the Security tree and select Global security.
b. In the Administrative security section, select the check box beside Enable administrative security.
c. In the Application security section, select the check box beside Enable application security.
d. In the User Account Repository, ensure Current Realm Definition is set to Federated repositories.
e. Click Apply to apply your changes.
9. Configuring the user account:
a. Go to Users and Groups
-> Manage Users