Creating/Maintaining ARS Development Environment
I am looking for feedback on what methods you use to create and maintain your AR System development environment(s)? Do you build from scratch and just import .def from production? What about data? (manual synchronization with prod, no data synchronization, automated tool) Is it possible to do a database copy and have an exact replica of the production environment? Other solutions? Please point me to any links, documentation or archived posts you’ve found useful. Thanks, Ken. *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.Hubbell.com - Hubbell Incorporated** ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are
Re: Creating/Maintaining ARS Development Environment
Database copy is the most reliable/quickest method. If on Unix/Linux, the Remedy filesystem can be copied between the app servers. There are some steps that have to be taken after the database and filesystem copies to ensure that the system does not start generating email messages, etc. after the db is copied and before the app server is started. Axton Grams On Wed, Feb 22, 2012 at 9:16 AM, Cecil, Ken kce...@hubbell.com wrote: ** I am looking for feedback on what methods you use to create and maintain your AR System development environment(s)? Do you build from scratch and just import .def from production? What about data? (manual synchronization with prod, no data synchronization, automated tool) Is it possible to do a database copy and have an exact replica of the production environment? Other solutions? Please point me to any links, documentation or archived posts you’ve found useful. Thanks, Ken. *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.Hubbell.com - Hubbell Incorporated** _attend WWRUG12 www.wwrug.com ARSlist: Where the Answers Are_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are
Re: Creating/Maintaining ARS Development Environment
Thanks for your reply. Current environment is Windows Servers, MS SQL database, and ITSM apps. If we do a clean fresh install of the AR server and applications on the dev server (then take an image of that server for future rebuilds) would the db copy still work? Just overwrite the db that got created upon install? Beside disabling the email, Is there any data/schema that needs to be modified when you do a db copy before bringing up the new dev server? For instance I wonder if you have to search for references to the production server name in the workflow that should be changed to the dev server name? Thanks again, Ken. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Axton Sent: Wednesday, February 22, 2012 10:37 AM To: arslist@ARSLIST.ORG Subject: Re: Creating/Maintaining ARS Development Environment Database copy is the most reliable/quickest method. If on Unix/Linux, the Remedy filesystem can be copied between the app servers. There are some steps that have to be taken after the database and filesystem copies to ensure that the system does not start generating email messages, etc. after the db is copied and before the app server is started. Axton Grams On Wed, Feb 22, 2012 at 9:16 AM, Cecil, Ken kce...@hubbell.com wrote: ** I am looking for feedback on what methods you use to create and maintain your AR System development environment(s)? Do you build from scratch and just import .def from production? What about data? (manual synchronization with prod, no data synchronization, automated tool) Is it possible to do a database copy and have an exact replica of the production environment? Other solutions? Please point me to any links, documentation or archived posts you've found useful. Thanks, Ken. *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.Hubbell.com - Hubbell Incorporated** _attend WWRUG12 www.wwrug.com ARSlist: Where the Answers Are_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.Hubbell.com - Hubbell Incorporated** ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are
Re: Creating/Maintaining ARS Development Environment
It should work. There should not be any references to the hardcoded server names in the workflow. You could find the sqls to search for workflow server references in this forum or you could write your own sqls. Only stuff that did not work for us is AIE. So we had to reinstall AIE after db copy. We did very similar thing when we deployed ITSM 7.6.03 mid last year. ITSM is installed in dev and production independently. Then in dev server we did all configurations, tested thoroughly. Before deploying it to production we just deleted all the data created during testing in Incident,Change,Task main and child forms. Then copied the db and put that into our production server and then did a few changes. I At that time I did a search on this forum and there were several postings with the schema names that need to be touched after the db copy. I mentioned all those here but many of them are not relevant to recent versions. Copy db from Staging to Production during the initial production deployment: Pre copy steps: 1. In production servers(2 servers) disable email engine in ar.conf 2. In dev server disable email mail boxes 3. Delete all email entries Post db copy: 1. Update the default web path 2. Update Servername, Servergroupname, servergroup ranking entries 3. Form data changes: -- Report form entries with new Server Name -- change server name to development.fqdn or development -- SHARE:Application_Properties, HelpFile URL pointers -- SYS:Application form -- Survey URL -- CAI Application Registry -- In Connection tab, change all Server names from production.fqdn to development.fqdn -- SHR:Association -- The server name is stored in two fields on the form - Server 1 and Server 2 -- Configure Custom Form Info -- SYS:Attachments form -- CMS Configuration Management -- AP:Notifications - Check any custom notifications with Server links -- AP:Rule Definition (Server = @) -- AR System Server Group Operation Ranking -- AR System User Preferences -- Change Report Server values from production to development for any user account you are going to log in with on development -- AR System Administrator Preferences -- Partial List Settings - Partial List Details:Other - Pack List Settings -- AR System Searches Preference -- Delete records from original server -- AR System User Central File -- Delete records for user -- KMS:Administration_Integration-- Change Server Name and Short Description -- SRD:STAGE:MasterDataMappingList -- SRM:ApplicationSettings, if SRM installed, to point to correct web path -- AST:ARServerConnection -- AR Login Info -- AST:ComplianceARBased_Advanced--AR System License Type Compliance -- SYS:Escalations -- SYS:Attachments -- SLM:ConfigPreferences -- Update Dashboard MidTier URL -- SLM:RuleActionSetValue_base -- Found four records to change with SLA_destination Server Name = production.fqdn,Changed all of them to @ -- SLA data sources, service agreements, and service targets with milestones, after the db had been restored -- CHG:CCMCalendar:PrintActionWUT -- Active Links that contain server references -- AREmail Configuration -- update with production email accounts -- Table fields -- check with sql select distinct tfserver from field_table -- AIS:GlobalPreferences form (Atrium Impact Simulator) -- AIE EIE:ApplicationSettings form (field name: Help File Path) -- AIE EIE:BackUpLoadFlag form entries (field names: Host, Internal Instance Name,InstanceName) -- AIE EIE:DataExchange form entries (field names: Instance Name, zTmpInstanceAlias) -- BMC.CORE.CONFIG:BMC_FederatedInterface records (Field name: ARServerName) -- IEORA:RuleHelper (field name: Path) -- EIE:CommonDialog (Help File Path) -- Reinstall and Reconfigure AIE and all Data Exchanges 4.The mid-tier configuration, where you specify the Data Visualization server 5.If you have customised any of the OOB notification messages to include a hardcoded a url then you need to change the server name reference. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are
Re: Creating/Maintaining ARS Development Environment
Thanks From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of patchsk Sent: Wednesday, February 22, 2012 11:44 AM To: arslist@ARSLIST.ORG Subject: Re: Creating/Maintaining ARS Development Environment ** It should work. There should not be any references to the hardcoded server names in the workflow. You could find the sqls to search for workflow server references in this forum or you could write your own sqls. Only stuff that did not work for us is AIE. So we had to reinstall AIE after db copy. We did very similar thing when we deployed ITSM 7.6.03 mid last year. ITSM is installed in dev and production independently. Then in dev server we did all configurations, tested thoroughly. Before deploying it to production we just deleted all the data created during testing in Incident,Change,Task main and child forms. Then copied the db and put that into our production server and then did a few changes. I At that time I did a search on this forum and there were several postings with the schema names that need to be touched after the db copy. I mentioned all those here but many of them are not relevant to recent versions. Copy db from Staging to Production during the initial production deployment: Pre copy steps: 1. In production servers(2 servers) disable email engine in ar.conf 2. In dev server disable email mail boxes 3. Delete all email entries Post db copy: 1. Update the default web path 2. Update Servername, Servergroupname, servergroup ranking entries 3. Form data changes: -- Report form entries with new Server Name -- change server name to development.fqdn or development -- SHARE:Application_Properties, HelpFile URL pointers -- SYS:Application form -- Survey URL -- CAI Application Registry -- In Connection tab, change all Server names from production.fqdn to development.fqdn -- SHR:Association -- The server name is stored in two fields on the form - Server 1 and Server 2 -- Configure Custom Form Info -- SYS:Attachments form -- CMS Configuration Management -- AP:Notifications - Check any custom notifications with Server links -- AP:Rule Definition (Server = @) -- AR System Server Group Operation Ranking -- AR System User Preferences -- Change Report Server values from production to development for any user account you are going to log in with on development -- AR System Administrator Preferences -- Partial List Settings - Partial List Details:Other - Pack List Settings -- AR System Searches Preference -- Delete records from original server -- AR System User Central File -- Delete records for user -- KMS:Administration_Integration-- Change Server Name and Short Description -- SRD:STAGE:MasterDataMappingList -- SRM:ApplicationSettings, if SRM installed, to point to correct web path -- AST:ARServerConnection -- AR Login Info -- AST:ComplianceARBased_Advanced--AR System License Type Compliance -- SYS:Escalations -- SYS:Attachments -- SLM:ConfigPreferences -- Update Dashboard MidTier URL -- SLM:RuleActionSetValue_base -- Found four records to change with SLA_destination Server Name = production.fqdn,Changed all of them to @ -- SLA data sources, service agreements, and service targets with milestones, after the db had been restored -- CHG:CCMCalendar:PrintActionWUT -- Active Links that contain server references -- AREmail Configuration -- update with production email accounts -- Table fields -- check with sql select distinct tfserver from field_table -- AIS:GlobalPreferences form (Atrium Impact Simulator) -- AIE EIE:ApplicationSettings form (field name: Help File Path) -- AIE EIE:BackUpLoadFlag form entries (field names: Host, Internal Instance Name,InstanceName) -- AIE EIE:DataExchange form entries (field names: Instance Name, zTmpInstanceAlias) -- BMC.CORE.CONFIG:BMC_FederatedInterface records (Field name: ARServerName) -- IEORA:RuleHelper (field name: Path) -- EIE:CommonDialog
Re: Creating/Maintaining ARS Development Environment
You might consider copying the prod database to the new environment and installing against that instead of doing a fresh install. The installers will run more quickly as they don't have much work to do on the database. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Cecil, Ken Sent: 22 February 2012 15:49 To: arslist@ARSLIST.ORG Subject: Re: Creating/Maintaining ARS Development Environment Thanks for your reply. Current environment is Windows Servers, MS SQL database, and ITSM apps. If we do a clean fresh install of the AR server and applications on the dev server (then take an image of that server for future rebuilds) would the db copy still work? Just overwrite the db that got created upon install? Beside disabling the email, Is there any data/schema that needs to be modified when you do a db copy before bringing up the new dev server? For instance I wonder if you have to search for references to the production server name in the workflow that should be changed to the dev server name? Thanks again, Ken. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Axton Sent: Wednesday, February 22, 2012 10:37 AM To: arslist@ARSLIST.ORG Subject: Re: Creating/Maintaining ARS Development Environment Database copy is the most reliable/quickest method. If on Unix/Linux, the Remedy filesystem can be copied between the app servers. There are some steps that have to be taken after the database and filesystem copies to ensure that the system does not start generating email messages, etc. after the db is copied and before the app server is started. Axton Grams On Wed, Feb 22, 2012 at 9:16 AM, Cecil, Ken kce...@hubbell.com wrote: ** I am looking for feedback on what methods you use to create and maintain your AR System development environment(s)? Do you build from scratch and just import .def from production? What about data? (manual synchronization with prod, no data synchronization, automated tool) Is it possible to do a database copy and have an exact replica of the production environment? Other solutions? Please point me to any links, documentation or archived posts you've found useful. Thanks, Ken. *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.Hubbell.com - Hubbell Incorporated** _attend WWRUG12 www.wwrug.com ARSlist: Where the Answers Are_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.Hubbell.com - Hubbell Incorporated** ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are
Re: Creating/Maintaining ARS Development Environment
Great! Any idea if I will need to do any touch up to the data (i.e. referencing the prod server name)? Ken. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Peter Romain Sent: Wednesday, February 22, 2012 12:07 PM To: arslist@ARSLIST.ORG Subject: Re: Creating/Maintaining ARS Development Environment You might consider copying the prod database to the new environment and installing against that instead of doing a fresh install. The installers will run more quickly as they don't have much work to do on the database. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Cecil, Ken Sent: 22 February 2012 15:49 To: arslist@ARSLIST.ORG Subject: Re: Creating/Maintaining ARS Development Environment Thanks for your reply. Current environment is Windows Servers, MS SQL database, and ITSM apps. If we do a clean fresh install of the AR server and applications on the dev server (then take an image of that server for future rebuilds) would the db copy still work? Just overwrite the db that got created upon install? Beside disabling the email, Is there any data/schema that needs to be modified when you do a db copy before bringing up the new dev server? For instance I wonder if you have to search for references to the production server name in the workflow that should be changed to the dev server name? Thanks again, Ken. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Axton Sent: Wednesday, February 22, 2012 10:37 AM To: arslist@ARSLIST.ORG Subject: Re: Creating/Maintaining ARS Development Environment Database copy is the most reliable/quickest method. If on Unix/Linux, the Remedy filesystem can be copied between the app servers. There are some steps that have to be taken after the database and filesystem copies to ensure that the system does not start generating email messages, etc. after the db is copied and before the app server is started. Axton Grams On Wed, Feb 22, 2012 at 9:16 AM, Cecil, Ken kce...@hubbell.com wrote: ** I am looking for feedback on what methods you use to create and maintain your AR System development environment(s)? Do you build from scratch and just import .def from production? What about data? (manual synchronization with prod, no data synchronization, automated tool) Is it possible to do a database copy and have an exact replica of the production environment? Other solutions? Please point me to any links, documentation or archived posts you've found useful. Thanks, Ken. *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.Hubbell.com - Hubbell Incorporated** _attend WWRUG12 www.wwrug.com ARSlist: Where the Answers Are_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.Hubbell.com - Hubbell Incorporated** ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.Hubbell.com - Hubbell Incorporated** ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are
Re: Creating/Maintaining ARS Development Environment
Not for the installation as far as I remember but you'll still need to update server references as per a previous email to get it to work properly. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Cecil, Ken Sent: 22 February 2012 17:16 To: arslist@ARSLIST.ORG Subject: Re: Creating/Maintaining ARS Development Environment Great! Any idea if I will need to do any touch up to the data (i.e. referencing the prod server name)? Ken. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Peter Romain Sent: Wednesday, February 22, 2012 12:07 PM To: arslist@ARSLIST.ORG Subject: Re: Creating/Maintaining ARS Development Environment You might consider copying the prod database to the new environment and installing against that instead of doing a fresh install. The installers will run more quickly as they don't have much work to do on the database. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Cecil, Ken Sent: 22 February 2012 15:49 To: arslist@ARSLIST.ORG Subject: Re: Creating/Maintaining ARS Development Environment Thanks for your reply. Current environment is Windows Servers, MS SQL database, and ITSM apps. If we do a clean fresh install of the AR server and applications on the dev server (then take an image of that server for future rebuilds) would the db copy still work? Just overwrite the db that got created upon install? Beside disabling the email, Is there any data/schema that needs to be modified when you do a db copy before bringing up the new dev server? For instance I wonder if you have to search for references to the production server name in the workflow that should be changed to the dev server name? Thanks again, Ken. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Axton Sent: Wednesday, February 22, 2012 10:37 AM To: arslist@ARSLIST.ORG Subject: Re: Creating/Maintaining ARS Development Environment Database copy is the most reliable/quickest method. If on Unix/Linux, the Remedy filesystem can be copied between the app servers. There are some steps that have to be taken after the database and filesystem copies to ensure that the system does not start generating email messages, etc. after the db is copied and before the app server is started. Axton Grams On Wed, Feb 22, 2012 at 9:16 AM, Cecil, Ken kce...@hubbell.com wrote: ** I am looking for feedback on what methods you use to create and maintain your AR System development environment(s)? Do you build from scratch and just import .def from production? What about data? (manual synchronization with prod, no data synchronization, automated tool) Is it possible to do a database copy and have an exact replica of the production environment? Other solutions? Please point me to any links, documentation or archived posts you've found useful. Thanks, Ken. *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.Hubbell.com - Hubbell Incorporated** _attend WWRUG12 www.wwrug.com ARSlist: Where the Answers Are_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.Hubbell.com - Hubbell Incorporated** ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has
Re: Creating/Maintaining ARS Development Environment
There is also the Remedy Restore Tool Version in the BMC Communities to help with the process. https://communities.bmc.com/communities/docs/DOC-7710 Jason On Wed, Feb 22, 2012 at 9:23 AM, Peter Romain p.romain.arsl...@parsolutions.co.uk wrote: Not for the installation as far as I remember but you'll still need to update server references as per a previous email to get it to work properly. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Cecil, Ken Sent: 22 February 2012 17:16 To: arslist@ARSLIST.ORG Subject: Re: Creating/Maintaining ARS Development Environment Great! Any idea if I will need to do any touch up to the data (i.e. referencing the prod server name)? Ken. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Peter Romain Sent: Wednesday, February 22, 2012 12:07 PM To: arslist@ARSLIST.ORG Subject: Re: Creating/Maintaining ARS Development Environment You might consider copying the prod database to the new environment and installing against that instead of doing a fresh install. The installers will run more quickly as they don't have much work to do on the database. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Cecil, Ken Sent: 22 February 2012 15:49 To: arslist@ARSLIST.ORG Subject: Re: Creating/Maintaining ARS Development Environment Thanks for your reply. Current environment is Windows Servers, MS SQL database, and ITSM apps. If we do a clean fresh install of the AR server and applications on the dev server (then take an image of that server for future rebuilds) would the db copy still work? Just overwrite the db that got created upon install? Beside disabling the email, Is there any data/schema that needs to be modified when you do a db copy before bringing up the new dev server? For instance I wonder if you have to search for references to the production server name in the workflow that should be changed to the dev server name? Thanks again, Ken. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Axton Sent: Wednesday, February 22, 2012 10:37 AM To: arslist@ARSLIST.ORG Subject: Re: Creating/Maintaining ARS Development Environment Database copy is the most reliable/quickest method. If on Unix/Linux, the Remedy filesystem can be copied between the app servers. There are some steps that have to be taken after the database and filesystem copies to ensure that the system does not start generating email messages, etc. after the db is copied and before the app server is started. Axton Grams On Wed, Feb 22, 2012 at 9:16 AM, Cecil, Ken kce...@hubbell.com wrote: ** I am looking for feedback on what methods you use to create and maintain your AR System development environment(s)? Do you build from scratch and just import .def from production? What about data? (manual synchronization with prod, no data synchronization, automated tool) Is it possible to do a database copy and have an exact replica of the production environment? Other solutions? Please point me to any links, documentation or archived posts you've found useful. Thanks, Ken. *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.Hubbell.com - Hubbell Incorporated** _attend WWRUG12 www.wwrug.com ARSlist: Where the Answers Are_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are *** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote also confirms that this email message has been swept for the presence of computer viruses. www.Hubbell.com - Hubbell Incorporated** ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: Where
