webNetwork 5.1.0.x Hotfix

Summary

This is a list of things to keep in mind before during and after installing 5.1.0.x Hotfix for webNetwork 5.
Please take time to read the information below and if you have any questions contact Stoneware Support prior to starting the upgrade.

• As good practice, be sure that you have a good backup of your stoneware system.
  If you did not shut down webnetwork and make a full backup of the STONEWARE directory, please do not perform the upgrade.
  

• In the past, the Linux and Solaris installs were a .tar download. We have decided to use gzip now to shorten the download times. You can use any of the gui tools to un gzip the file or command like tools such as gunzip filename.bin.gz. Once extracted, set the permissions to Executable. Depending on your linux/unix gui you can do this by right clicking on the file, go to Permissions and check the executable box. Do do this from a shell prompt, type chmod 777 wn5104.bin

• Plan your upgrade
  Unless you have clustering and redundant relays, users will not be able to login when you are performing the upgrade.
  Do not perform upgrade if you have recently made other changes to system or infrastructure or while you are having problems with infrastructure.
  Doing so makes it very difficult to diagnose any issues.
  

• Secondary username / password for 8090 Management Console
  If you have console security turned on your 8090 Management Console, it is a good idea to make sure that you have set up a username and password to get into the 8090 Management Console and it works.
  Make sure this account is an account that does NOT exist in your directory services. The purpose of this account is a way to get into the 8090 Management console if webNetwork is unable to talk to the ldap server.
  This account is only able to get into the Managment Console, it can NOT be used to run the upgrade wizard or get into webAdmin.
  

• anti Virus packages
  Many of the anti virus packages have been know to cause issues when run on a high traffic server. Symantec and Mcafee in particular. If they are not configured to ignore the stoneware directory and its temp location, unexpected results can occur. In particular many of the new packages can hook into the TCP stack and analyze the tcp content, this also has caused problems with communication. It is advised that if you are running fine with an anti virus product currently that you be cautious when making any changes or updates to it. If problems occur with webnetwork, try disabling the anti virus product and see if problems still happen and adjust the anti virus product accordingly.

• Before running install, check and make sure your core features are working. Check things like key webapps, swift nodes, etc..
  If they do not work now, they will most likely not work after upgrade either.
  After the upgrade, test these same features out to make sure they behave correctly.
  

• Relay Central
  If you use Relay Central to sync files from a master server to your other relays AND you have your master files in a location other than where stoneware is installed, please continue reading.
  Assume your relay central is configured to use d:\relay-central-files\webserv and d:\relay-central-files\webserv-sec
  After this update you will need to copy the files from c:\stoneware\webserv and c:\stoneware\webserv-sec to your d:\relay-central-files directories
  If you do not do this, then the new files from this update will not be synchronized properly to all of your relays.
  Many customers do not change the path of relay central files from the location of the stoneware directory, if this is your case then you don't have to worry about copying these files by hand.
  

• Run the appropriate install file for your Operating System. Do this on EVERY webnetwork server.
  Do not apply individual files from the install, they should all be installed as a set via the install process. The update must be applied to all server.
  

• Start your upgrade on core loader servers (the one configured to talk to your ldap server) and work your way out to your relays testing as you go.
  After doing first server, verify that everything came back up, if you have a relay on that same box as loader, use that as a test.
  If you do not have a relay on that loader, then login to :8090 management console and get into webAdmin. If you can view users, links, browse your tree you are talking to the directory and should be good to continue to next webNetwork server.
  
  

• This upgrade will automatically purge your /stoneware/temp directory to make sure that any updated .jsp files get re compiled.
  

• Be sure to run the Upgrade Wizard from the 8090 console against at least 1 relayobject to ensure that you get any new links/objects created.
  You only have to run the wizard ONE time, it does not have to be done on every webnetwork server or for every relayobject.
  

• You will need to run Community Service Pack 7 link under Admin programs. This will apply the latest changes to the community database.
  Unlike before, this update will work with HSQL, MySQL, and MS SQL. Even though this is a small change to the database, it is always good to make a backup of the database first.
  

• Stoneware debugging options.
  It is a good idea to shut off the debug settings when you are done with them.
  The 8090 management console now has a button to reset them all back to defaults.
  Go to the 8090 management console for each server
  Click on your profile in the left pane
  Click on Logging button at top of screen.
  Click on the Reset to Defaults Button.
  When the page refreshes, click Save.
  

• Common debug settings that can be used to diagnose issues.
  The common startup sequence for webNetwork and the debug settings that will show this information can be found here.
  The common debug settings and sample out that they display can be found here.
  

Reference

Additional information on the changes in this hotfix can be found here : http://www.stone-ware.com/webos/support/swdownloads/wnhf510x/wnhf510x.txt.