If you change the settings of a once started Web application, you must initialize the preference information stored in the database.

This subsection describes the procedure for initializing preference information stored in a database.

1. Copy the template file to any location.
   A template file is provided as an SQL file used for initializing the preference information stored in a database. The storage locations of template files for each database used are:
   
   • Storage location of template files when using HiRDB
     In Windows: Application-Server-installation-directory\CC\sfo\sql\hirdb_reset_apptbl.sql
     In UNIX: /opt/Cosminexus/CC/sfo/sql/hirdb_reset_apptbl.sql
     
   • Storage location of template files when using Oracle
     In Windows: Application-Server-installation-directory\CC\sfo\sql\oracle_reset_apptbl.sql
     In UNIX: /opt/Cosminexus/CC/sfo/sql/oracle_reset_apptbl.sql
     
2. Edit the template file.
   Edit the template file in accordance with the preference information of the Web application and create an SQL file for initializing the preference information stored in the Web application. The following table describes change locations and change contents in template files.
   

   Table 6-50 Change locations and change contents in template files

   Change location	Change target	Change contents
   First line	APPLICATION_ID	Change application identifier of the application to be used.

3. Execute the SQL file for initializing the preference information stored in the created database.
   For executing the SQL file, use SQL Executer when using HiRDB and SQL*Plus when using Oracle.
   

Change the amount of global session information in the database in accordance with the upper limit of the number of HTTPsession objects. However, if negotiation processing executed when starting an application fails, the amount of global session information in the database and the setting of upper limit of the number of HTTPsession objects can be different if you have set to continue the processing of starting a Web application.

This subsection describes the procedure for changing the amount of global session information in a database. If you change the amount of global session information in a database, all session information in the database is deleted.

1. Stop the J2EE applications and J2EE servers.
   Stop all applications in the J2EE server and all replicated J2EE servers.
   
2. Copy the template file to any location.
   A template file is provided as an SQL file for changing the amount of global session information in a database. The storage locations of template files for each used database are:
   
   • Storage location of template files when using HiRDB
     In Windows: Application-Server-installation-directory\CC\sfo\sql\hirdb_change_session_num.sql
     In UNIX: /opt/Cosminexus/CC/sfo/sql/hirdb_change_session_num.sql
     
   • Storage location of template files when using Oracle
     In Windows: Application-Server-installation-directory\CC\sfo\sql\oracle_change_session_num.sql
     In UNIX: /opt/Cosminexus/CC/sfo/sql/oracle_change_session_num.sql
     
3. Edit the template file.
   Edit the template file in accordance with the preference information of the Web application and create an SQL file for changing the amount of global session information in the database. The following table describes change locations and change contents in template files.
   

   Table 6-51 Change locations and change contents in template files

   Change location		Change target	Change contents
   HiRDB	Oracle
   First line Second line Third line Sixth line Seventh line	First line Second line Third line Sixth line	APPLICATION_ID	Change the application identifier of the application to be used.
   Fourth line Seventh line	Fourth line Sixth line	HTTP_SESSION_NO	Change the amount of global session information stored in the database.

4. Execute the SQL file created for changing the amount of global session information in the database.
   For executing the SQL file, use SQL Executer when using HiRDB and SQL*Plus when using Oracle.
   

If you change the maximum size of HTTP session attribute information that you can include in global session information that is set in a Web application after creating a session information storage table, you must change the maximum size of the HTTP session attribute information in the database. Set a value for the maximum size of HTTP session attribute information in the database that is greater than the maximum size of HTTP session attribute information that you can include in the global session information set in a Web application. For details on setting the maximum size of HTTP session attribute information that you can include in global session information set in a Web application, see 6.5 Definitions in cosminexus.xml.

This subsection describes the procedures for changing the maximum size of HTTP session attribute information in a database. These procedures are required only when using HiRDB.

1. Stop the J2EE applications and J2EE servers.
   Stop all applications in the J2EE server and all replicated J2EE servers.
   
2. Copy the template file to any location.
   A template file is provided as an SQL file for changing maximum size of HTTP session attribute information in a database. The storage locations of template file are:
   In Windows: Application-Server-installation-directory\CC\sfo\sql\hirdb_change_attributes_size.sql
   In UNIX: /opt/Cosminexus/CC/sfo/sql/hirdb_change_attributes_size.sql
   
3. Edit the template file.
   Edit the template file in accordance with preference information of a Web application and create an SQL file used for changing the maximum size of HTTP session attribute information in a database. The following table describes the change locations and change contents in template files.
   

   Table 6-52 Change locations and change contents in template files

   Change location	Change target	Change contents
   First line	APPLICATION_ID	Change the application identifier of the application to be used.
   Second line	ATTRIBUTE_DATA_SIZE_MAX	Change size (units: bytes) of the column that stores HTTP session attribute information.

4. Execute the SQL file created for changing the amount of global session information in a database.
   For executing the SQL file, use SQL Executer.