bw:installation_upgrade_guide

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
bw:installation_upgrade_guide [2020/08/04 11:55]
akoehler
bw:installation_upgrade_guide [2020/12/14 17:07] (current)
akoehler [Configure SQL Server for Web Service Calls]
Line 136: Line 136:
 <WRAP center round alert 90%> <WRAP center round alert 90%>
 Be sure that all instances of the Bizweaver application are ended before beginning the update.  You can check this using Windows Task Manager > Users tab.  <color #ed1c24>**Do not begin the upgrade if any instances are open**</color>. Be sure that all instances of the Bizweaver application are ended before beginning the update.  You can check this using Windows Task Manager > Users tab.  <color #ed1c24>**Do not begin the upgrade if any instances are open**</color>.
-</WRAP> 
- 
-<WRAP center round alert 90%> 
-When upgrading to Bizweaver 2.5, recurring schedules over minutes or hours on the day the workflow runs (what is now set on the Run Times tab), will need rescheduling due to the previously defined start and stop (until) times, which refer to the time on the start date the schedule will start and time on the end date the schedule will end. These times will insert into the From and To times for the Run Every option. If left unchanged after upgrading to version 2.5, a schedule will not execute as initially intended. 
- 
-In addition to new scheduling functionality, an update to the web services tool 2.0 has been included in version 2.5.  After upgrading, workflows containing the web services tool 2.0 must be opened and saved to enable the new features. Third wave is in the process of adding a wizard to handle this process automatically in future builds of Bizweaver. 
 </WRAP> </WRAP>
  
Line 155: Line 149:
 </WRAP> </WRAP>
  
 +To upgrade Bizweaver, simply follow the installation instructions as outlined above. Bizweaver workflows are stored in the database so they will remain intact during the upgrade process.
  
 +=== Bizweaver Workflow Upgrade Wizard ===
 +Beginning in Bizweaver 2.5.17 a wizard will run after the upgrade completes. This wizard opens and saves each workflow to update any tools that have been upgraded in the newest release of Bizweaver. 
 +
 +{{ :bw:upgradewindow.png?400 |}}
 +
 +  * The wizard will process through all workflows in a Bizweaver instance. 
 +
 +{{ :bw:upgradewindow2.png?400 |}}
 +
 +  * Once the wizard is complete a list of all errors if any, will be displayed.
 +    * **Open Log** This will open a text document with all errors displayed in the wizard.
 +    * **OK** This will close the wizard and proceed to Bizweaver.
 +  * To manually upgrade any workflow that failed, open the indicated workflow, fix the error and save.
 +  * If no errors are encountered, the wizard will close completing the upgrade process.
  
-To upgrade Bizweaver, simply follow the installation instructions as outlined above. Bizweaver workflows are stored in the database so they will remain intact during the upgrade process. 
  
-==== Final Upgrade Steps ====+=== Final Upgrade Steps ===
  
   * Check the **Bizweaver Service** service and confirm that the designated domain user described in the environment requirements is still in place.  Reset the user if it is not.   * Check the **Bizweaver Service** service and confirm that the designated domain user described in the environment requirements is still in place.  Reset the user if it is not.
Line 202: Line 210:
 In many SQL environments it is desirable to use the Bizweaver API to initiate a Bizweaver workflow.  A common example is when something occurs in SAP Business One. In many SQL environments it is desirable to use the Bizweaver API to initiate a Bizweaver workflow.  A common example is when something occurs in SAP Business One.
  
-To support this type of processing, some configuration in SQL Server is required.  The configuration process is outlined **//[[SQLWS_Config|here]]//**.  The use of this functionality is found **//[[SQLWS_Use|here]]//**.+To support this type of processing, some configuration in SQL Server is required.  The configuration process is outlined **//[[SQLWS_Config|here]]//**.
  
bw/installation_upgrade_guide.1596556518.txt.gz · Last modified: 2020/08/04 11:55 by akoehler