Wiki

Scale Your Enterprise

User Tools

Site Tools

Trace: • Workflow Tools • charts_configuration • Filters • Introduction (Bizweaver) • downloads • APP - Report Maintenance and Delivery Screens • Versago Upgrade • Introduction (Email and Password Configuration) • Site Theme • Introduction (Payments)
bw:global_connections

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:global_connections [2020/04/21 12:54]
runger 		bw:global_connections [2021/05/10 14:21] (current)
akoehler [SAP Service Layer Connections]
Line 30: Line 30:
 The Global Configurations function is started by clicking on the appropriate icon in the toolbar as shown below. The Global Configurations function is started by clicking on the appropriate icon in the toolbar as shown below.
  
-{{:bw:gcimage1.png?223x47}}+{{  :bw:gcimage1.png?223x47  }}
  
 ===== Connection Listing ===== ===== Connection Listing =====
  
-{{:bw:gcimage2.png?384x417}}+{{  :bw:gcimage2.png?384x417  }}
  
   - The area at the top of the page lists all connections that are currently defined.   - The area at the top of the page lists all connections that are currently defined.
Line 52: Line 52:
 **SQL connections** are used to connect Bizweaver to Microsoft SQL Server databases. **SQL connections** are used to connect Bizweaver to Microsoft SQL Server databases.
  
-{{:bw:gcimage3.png?400}}+{{  :bw:gcimage3.png?400  }}
  
   * Enter the **Server** name to which you are connecting.   * Enter the **Server** name to which you are connecting.
Line 69: Line 69:
 ===== HANA Connections ===== ===== HANA Connections =====
  
-HANA connections are used to connect Bizweaver to SAP HANA databases.+HANA connections are used to connect Bizweaver to SAP HANA databases.  These connections are typically used to __read__ data only, although insert/update/delete can be accomplished as well.
  
-{{:bw:gcimage4.png?400}}+In Bizweaver v2.5 there are two options available: Single container (single tenant) and Multi Container (multi-tenant). The setup is very similar for both, and each one is illustrated below. 
 + 
 +====Single Tenant==== 
 + 
 +{{ :bw:hana_db_connection_single.png?400 |HANA single tenant}} 
 + 
 +  * Enter the **Server name** to which you are connecting. 
 +    * This will typically be a server/IP address & port number. 
 +    * The standard port number for HANA single tenant databases is **30015**. 
 +    * The server and port are separated by a colon ( : ). 
 +  * Select the //Single Container// **mode**. 
 +  * Enter the **HANA Username** and **Password** to access the HANA database. 
 +    * Creating a database user specifically for Bizweaver connections is recommended (although it is not required) as it can aid in troubleshooting connection issues. 
 +  * Enter the name of the **Database** to which you are connecting. 
 +  * Enter the **HANA Timeout** period 
 +    * The value is expressed in seconds. 
 +    * The default value of 30 is appropriate for most installations. 
 +      * This value is set on each database connection, so it can be different for each database if needed. The timeout value is used when the workflow is executed on a schedule or using the “Run now” option. 
 +    * Increase the value if you see connection timeouts occurring in HANA logs. 
 + 
 +====Multi-Tenant==== 
 + 
 +{{ :bw:hana_db_connection_multi.png?400 |HANA multi-tenant}}
  
   * Enter the **Server name** to which you are connecting.   * Enter the **Server name** to which you are connecting.
     * This will typically be a server/IP address & port number.     * This will typically be a server/IP address & port number.
-    * The standard port number for HANA databases is 30015.+    * The standard port number for HANA multi-tenant databases is **30013**. 
 +    * The server and port are separated by a colon ( : ). 
 +  * Select the //Multiple Containers// **mode**. 
 +  * Enter the **Tenant Database** name. 
 +  * Enter the **HANA Username** and **Password** to access the HANA database. 
 +    * Creating a database user specifically for Bizweaver connections is recommended (although it is not required) as it can aid in troubleshooting connection issues.
   * Enter the name of the **Database** to which you are connecting.   * Enter the name of the **Database** to which you are connecting.
-  * Enter the **HANA Username** and **Password** to access the SQL Server database. 
-    * Creating a HANA user specifically for Bizweaver connections is recommended (although it is not required) as it can aid in troubleshooting connection issues. 
   * Enter the **HANA Timeout** period   * Enter the **HANA Timeout** period
     * The value is expressed in seconds.     * The value is expressed in seconds.
     * The default value of 30 is appropriate for most installations.     * The default value of 30 is appropriate for most installations.
       * This value is set on each database connection, so it can be different for each database if needed. The timeout value is used when the workflow is executed on a schedule or using the “Run now” option.       * This value is set on each database connection, so it can be different for each database if needed. The timeout value is used when the workflow is executed on a schedule or using the “Run now” option.
-    * Increase the value if you see SQL timeouts occurring in HANA logs.+    * Increase the value if you see connection timeouts occurring in HANA logs.
  
 ===== DI Server Connections ===== ===== DI Server Connections =====
Line 89: Line 114:
 DI Server connections are only used in SAP Business One environments. They are used to connect Bizweaver to the SAP Business One DI Server application. The DI Server is a tool that interacts with SAP Business One to add and update data in the SAP Business One company database. DI Server connections are only used in SAP Business One environments. They are used to connect Bizweaver to the SAP Business One DI Server application. The DI Server is a tool that interacts with SAP Business One to add and update data in the SAP Business One company database.
  
-{{:bw:gcimage5.png?400}}+{{  :bw:gcimage5.png?400  }}
  
   * **Server** is the server (SQL or HANA) name where the SAP Business One database is found. If named instances are being used (e.g. ServerName\InstanceName) then the full instance name should be entered.   * **Server** is the server (SQL or HANA) name where the SAP Business One database is found. If named instances are being used (e.g. ServerName\InstanceName) then the full instance name should be entered.
Line 112: Line 137:
 DI API connections are only used in SAP Business One environments. They are used to connect Bizweaver to the SAP Business One DI API. The DI API is a tool that interacts with SAP Business One to add and update data in the SAP Business One company database. DI API connections are only used in SAP Business One environments. They are used to connect Bizweaver to the SAP Business One DI API. The DI API is a tool that interacts with SAP Business One to add and update data in the SAP Business One company database.
  
-{{:bw:gcimage6.png?400}}+<WRAP center round important 60%> **Currently SAP DI API Connections starting in Bizweaver version 2.5 will support SAP version 10. Only one connection of a SAP version will be allowed through Bizweaver either a SAP version 9.3 or SAP version 10 connection can be established not both ** </WRAP> 
 + 
 +{{  :bw:gcimage6.png?400  }}
  
   * **Server** is the server (SQL or HANA) name where the SAP Business One database is found. If named instances are being used (e.g. ServerName\InstanceName) then the full instance name should be entered.   * **Server** is the server (SQL or HANA) name where the SAP Business One database is found. If named instances are being used (e.g. ServerName\InstanceName) then the full instance name should be entered.
Line 134: Line 161:
 SMTP connections are used to provide connection information for the server(s) that handle email. Most installation will only have one SMTP connection. However, there is no technical restriction on the number of connections that are defined. SMTP connections are used to provide connection information for the server(s) that handle email. Most installation will only have one SMTP connection. However, there is no technical restriction on the number of connections that are defined.
  
-{{:bw:gcimage7.png?384x243}}+{{  :bw:gcimage7.png?384x243  }}
  
   * **Server** is the server where your SMTP application is found   * **Server** is the server where your SMTP application is found
Line 168: Line 195:
 The following image shows how this setup is implemented as a Bizweaver Global Connection. The following image shows how this setup is implemented as a Bizweaver Global Connection.
  
-{{:bw:gcimage11.png?477x347}}+{{  :bw:gcimage11.png?477x347  }}
  
 ===== Exchange Connections ===== ===== Exchange Connections =====
 Exchange connections are used to access a Microsoft Exchange server directly.  This is different from the SMTP connection, even if you use Exchange as your SMTP server.  This allows you to read incoming email and create appointments (meetings) for other users.  Defining this type of connection does not apply if you do not use an Exchange server. Exchange connections are used to access a Microsoft Exchange server directly.  This is different from the SMTP connection, even if you use Exchange as your SMTP server.  This allows you to read incoming email and create appointments (meetings) for other users.  Defining this type of connection does not apply if you do not use an Exchange server.
  
-{{:bw:gcimage12.png?475x249}}+{{  :bw:gcimage12.png?475x249  }}
  
   - Select the **Exchange Version** from the drop-down list.   - Select the **Exchange Version** from the drop-down list.
Line 195: Line 222:
 oAuth **1** is not supported in Bizweaver. oAuth **1** is not supported in Bizweaver.
 </WRAP> </WRAP>
- 
-===== SAP Service Layer Connections ===== 
-The SAP **Service Layer** is an API connection to Business One company databases.  The Service Layer is available for HANA v9.3 and higher.  It will be available for SQL v10 and higher.  The button to add a new Service Layer connection is labeled **SAP Service** 
- 
-{{:bw:gcimage13.png?400|Service Layer}} 
- 
-  - the **URL** is the pointer to the server where SAP Business One is installed.  The only thing that needs to be changed is the server name.  You can copy/paste this example, replacing <YourServer> (without the < >)with the appropriate value. 
- 
-<code> 
-https://<YourServer>:50000/b1s/v1 
-</code> 
-  - **Database** is the SAP Business One company database name.  This value is case sensitive. 
-  - **Username** and **Password** are the credentials that will be used to "login" to SAP Business One.  This user should be identified as a "superuser" and should have either a Professional or Indirect Access user license. 
  
 ==== Basic Authentication ==== ==== Basic Authentication ====
  
-{{:bw:gcimage8.png?475x249}}+{{  :bw:gcimage8.png?475x249  }}
  
   - Select the **Basic Authentication** radio button.   - Select the **Basic Authentication** radio button.
Line 219: Line 233:
 ==== oAuth 2 Authentication ==== ==== oAuth 2 Authentication ====
  
-{{:bw:gcimage9.png?469x331}}+{{  :bw:gcimage9.png?469x331  }}
  
   - Select the **oAuth 2 Authentication** radio button.   - Select the **oAuth 2 Authentication** radio button.
Line 227: Line 241:
     - Again, the API documentation should provide instructions on how to obtain the various authorization elements.     - Again, the API documentation should provide instructions on how to obtain the various authorization elements.
   - The Redirect URI can generally be anything you like (e.g. https://mysite.com). This function is typically used for a website as opposed to an API. However, some APIs still require a value of some sort. Check with the API author if you have problems with this setting.   - The Redirect URI can generally be anything you like (e.g. https://mysite.com). This function is typically used for a website as opposed to an API. However, some APIs still require a value of some sort. Check with the API author if you have problems with this setting.
 +  - The connection information is saved but is not validated. Any connection errors will only be shown when the connection is used in a workflow.
 +
 +
 +===== SAP Service Layer Connections =====
 +The SAP **Service Layer** is an API connection to Business One company databases.  The Service Layer is available for HANA v9.3 and higher.  It will be available for SQL v10 and higher.  The button to add a new Service Layer connection is labeled **SAP Service**
 +
 +{{  :bw:gcimage13.png?400  |Service Layer}}
 +
 +  - the **URL** is the pointer to the server where SAP Business One is installed.  The only thing that needs to be changed is the server name.  You can copy/paste this example, replacing <YourServer> (without the < >)with the appropriate value.
 +
 +<code>
 +https://<YourServer>:50000/b1s/v1
 +</code>
 +  - **Database** is the SAP Business One company database name.  This value is case sensitive.
 +  - **Username** and **Password** are the credentials that will be used to "login" to SAP Business One.  This user should be identified as a "superuser" and should have either a Professional or Indirect Access user license. <WRAP info round center> If  single sign-on user is used to sign in to the service layer an extra backslash is needed to pass it through the Service Layer ex: domain\\user </WRAP>
   - The connection information is saved but is not validated. Any connection errors will only be shown when the connection is used in a workflow.   - The connection information is saved but is not validated. Any connection errors will only be shown when the connection is used in a workflow.
  
Line 233: Line 262:
 When a Global Connection is deleted, a consistency check is performed to ensure that any workflows using the connection are updated. A list of associated workflows and steps are listed in the lower area of the window. Replacement connections must be specified or the deletion process will not continue. When a Global Connection is deleted, a consistency check is performed to ensure that any workflows using the connection are updated. A list of associated workflows and steps are listed in the lower area of the window. Replacement connections must be specified or the deletion process will not continue.
  
-{{:bw:gcimage10.png?472x160}}+{{  :bw:gcimage10.png?472x160  }}
  
   - Option 1 is to use the “Replace all” option to update all listed workflow (Task) steps with a new connection.   - Option 1 is to use the “Replace all” option to update all listed workflow (Task) steps with a new connection.
bw/global_connections.1587488055.txt.gz · Last modified: 2020/04/21 12:54 by runger

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial 4.0 International
CC Attribution-Noncommercial 4.0 International Valid HTML5 Valid CSS Driven by DokuWiki