Installer 10.15 | Complete Installation and Upgrade Information for Software AG Products | Upgrading Software AG Products On Premises | Upgrade webMethods OneData | Complete the Upgrade
 
Complete the Upgrade
Perform the tasks below as appropriate.
*If you customized the old Java Service Wrapper, go to the Software AG_directory/profiles/ODE/configuration directories in the old and new installations, open the custom_wrapper.conf files, and copy the customizations from the old file to the new file.
Note:
As noted in the Software AG Infrastructure Administrator's Guide, you should never modify the wrapper.conf file unless instructed to do so by Software AG. If you mistakenly modified the old wrapper.conf file, manually copy values for properties you modified in the old wrapper.conf file to the corresponding properties in the new custom_wrapper.conf file.
*If you customized the old Log4j, go to the Software AG_directory/profiles/ODE/bin/onedata/config directory in the old and new installations, open the log4j.properties files, and copy the customizations from the old file to the new file.
*Go to the Software AG_directory/profiles/ODE/bin/onedata/config directories in the old and new installations and open the onedata.properties file. If the old onedata.search.elasticsearch.indexanalyzer property was set to autocomplete_analyzer, set the new onedata.search.elasticsearch.indexanalyzer property to autocomplete.
*If you are using JMS with webMethods OneData, copy the client jar files you backed up earlier to the new_Software AG_directory/profiles/ODE/webapp/onedata/WEB-INF/lib directory.
*If you are using Kerberos authentication with webMethods OneData, reconfigure it using the backups of the web.xml, server.xml, jaas.config, custom_wrapper.conf and com.softwareag.jaas.realm.pid-SSO_realm_name.properties files you created earlier. For instructions, see Administering webMethods OneData.
Adjust the webMethods OneData Metadata schema.
1. Log in to the Metadata schema.
2. Check the number of columns in the OD_MD_QUEUE_RCD table. If your table has COLUMN_1 through COLUMN_200, skip this step.
*If the table has the default of 50 columns, extend the table by running ALTER TABLE OD_MD_QUEUE_RCD ADD
*If the table has more than 50 columns but less than 200, add only the columns required to reach 200.
*For Oracle, each column should look like COLUMN_<number> varchar2(2000 byte, and the last line should be ;
*For SQL Server, each column should look like COLUMN_<number> [nvarchar](2000) NULL, and the last line should be ;
3. Go to the Software AG_directory/profiles/ODE/bin/onedata/config directory in the new installation and open the onedata.properties file. Set the two properties shown below as follows:.
onedata.exceptionqueue.fetchsize=50
onedata.exceptionqueue.numberofcolumns=200