Pre Install
This is a list of things to keep in mind before during and after
installing the latest Service Pack for webNetwork 5.4.
This service pack
will take any 5.4 version of webNetwork and patch it to 5.4.6.0. Because
of this some notes may not apply to you.
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 prior to installing the service pack. If you did not shut down webNetwork and
make a full backup of the STONEWARE directory, please do not
perform the upgrade! To perform a backup, all that is needed it to make a copy of the stoneware directory.
If you have Stoneware clustering, the cluster will need to be re configured
If you are upgrading from a version of webNetwork prior to 6.0.6.0 your cluster will be removed during the upgrade. Before upgrading be sure you know which servers were participating in the cluster. In the 8090 management console, click on Cluster Services and Cluster status and it will tell you which servers are part of the cluster.
After upgrading to webNetwork 6 the cluster will be automatically removed and will have to be re created. It is also imporant that the clocks on each cluster node be in sync within 1 minute of each other. For more information visit http://www.stone-ware.com/swql.jsp?kb=s3132
If you have any SSO forms that have ? and & in the
trigger, then you will need to edit those and add a \ (escape
character) before those. For example : To do SSO to Sugar, you
normally trigger on /crm/index.php?action=Login&module=Users
, now it will be /crm/index.php\?action=Login\&module=Users
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.
If you have a development system, test the upgrade on test
system prior to upgrade. If you have custom software using
stoneware API's via methods like SOAP, please be sure to test
your applications prior to upgrading production system.
webNetwork has updated its Axis client and some functions in
application like Visual Studio 2003 .Net 1.1 may not support
these updates. The upgrade will also modify the
/stoneware/webapps/axis/WEB-INF/server-config.wsdd You will now
have lines like : <handler
type="java:com.stoneware.soap.WhiteListHandler"/> on
the various services. These allow the use of the allowHosts and
denyHosts files in the same directory to restrict what IP
addresses can utilize these services. Out of the box, the
services are locked down. You either need to remove the
WhiteListHandler line form the service or modify the
allow/denyHosts files.
Profiles should be updated
Some webNetwork service packs
update the functionality of the profiles. This means that
periodically your custom profile will require an update. For
example. If you were using 5.4.0.0 previously and copied the
webOSProfile to make your own company profile you will want to
update it. To update it, first start by backing up your stoneware
system. Then copy the files from
\stoneware\webserv-sec\webOSProfile to your custom company
profile directory. As long as you used the profile editor your
changes will remain in tact. If you fail to update your profile
you "MAY" have an error during the login process as
explained in http://www.stone-ware.com/swql.jsp?KB=s2119
This example of upgrading assumed you used the webOSProfile, if
you used another profile use that profiles files to update your
profile. If you are unsure of which profile you used, please go
to http://www.stone-ware.com/cloud/support/
to submit a support request prior to upgrade.
Optional Schema Updates
Password self service was updated
to provide more features. To use these new features you will have
to use the Update Schema button on the Directory Services section
of the 8090 management console. The same rules apply as during
the install of webNetwork. The username/password has to have the
ability to update the schema. For Active Directory the IP/DNS
name for the ldap server needs to be a schema master. You do not
have to apply these schema updates if you do not wish to use the
new password reset features. If the schema updates are not done,
then you may see some errors during the Service Pack wizard.
These are normal and is just a warning that the new objects for
password self service will not be created.
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 Management 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, unless the Service Pack specifically
addresses this issue. 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.
Due to image licensing the following images will be replaced with a different image after the upgrade.
Cloud_Wallpaper_Large.jpg, Cloud_Wallpaper_Medium.jpg, WebOS_Wallpaper_Large.jpg, WebOS_Wallpaper_Medium.jpg
Performing install
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 servers. If you are using Linux, depending on what version of
Linux you have, you may have a problem with the GUI install. You
can get around this by running the console mode install. To
launch the install in console mode, run the following command :
./wn5300.bin -i console This will run the install without the
GUI, so you can perform the upgrade using a SSH client. After the
install manually update your license file
(/usr/stoneware/config/license.sw) as the console install does
not copy the new license file for you.
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.
Post install
If you use user registration, double check your
/stoneware/webserv/createuser.jsp and fix the context parameter
from o=stoneware to where you want users create. Also use
webAdmin to update the RELAYUSER object and add the User
Registration role. This is a new requirement in 5.4 If you do not
do this then user registration will not work. Once you add the
role to the relayuser account, restart the relay to activate the
changes. If you customized your createuser.jsp file, then you may need to make the same changed after the service pack or put old createuser.jsp back.
If you used Exchange calendar integration you will want to
upgrade your exchange agent code. It has been updated to handle
null characters that might be in 3rd party added calendar
appointments.
The updated agent is in
/stoneware/agents/StonewareExchangeAgent. Backup what you have,
remove all of the files and extract the contents of the new zip
file.
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.
Starting webNetwork in a cmd window.
When webNetwork
runs as a service you do not see any output when webNetwork is
loading. To debug many issues, you may need to run webNetwork in
a cmd/console window. To launch webNetwork console window on MS
Windows , start a DOS cmd prompt, change directory to the
stoneware\bin directory and run webnetwork.exe You will now see
webNetwork starting up and it may help debug any issues that you
are having. To start it up in Linux, type ./webNetwork To shut
down webnetwork, go to the 8090 console and click on the loader
and choose shutdown. Once you are done you can start webNetwork
back up as a service. Windows : net start webNetwork Linux :
/etc/init.d/webNetworkctl start
Reference
The POST install notes from the install can be found here.
The list of files that are in this update can be found here.
Additional information on the changes can be found here.
|