Wiki

Scale Your Enterprise

User Tools

Site Tools

Trace:
bw2: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
bw2:global_connections [2021/02/07 18:24]
akoehler [DI Server Connections] 		bw2:global_connections [2023/01/29 12:48] (current)
mfoster [SMTP Connections]
Line 139: Line 139:
 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.
  
-<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>+<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 an SAP version will be allowed through Bizweaver either an SAP version 9.3 or SAP version 10 connection can be established not both ** </WRAP>
  
-{{  :bw:gcimage6.png?400  }}+{{ :bw2:bizweaverconnectionmanager7.png |}}
  
-  * **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.
     * This information is displayed on the SAP Business One “Choose Company” screen.     * This information is displayed on the SAP Business One “Choose Company” screen.
   * **Database** is the specific company database to be accessed by the DI API.   * **Database** is the specific company database to be accessed by the DI API.
Line 151: Line 151:
   * **SBO Username** and **Password** for the user needed to logon to the SAP Business One company.   * **SBO Username** and **Password** for the user needed to logon to the SAP Business One company.
     * This user must have a valid license assigned.     * This user must have a valid license assigned.
-    * In most cases the license will be an “Indirect” user license.+    * In most cases, the license will be an “Indirect” user license.
   * **DB** (database) **Username** and **Password** for the user needed to logon to the SAP Business One company.   * **DB** (database) **Username** and **Password** for the user needed to logon to the SAP Business One company.
-    * This will typically be the same user defined for SQL and HANA connections+    * This will typically be the same user-defined for SQL and HANA connections
   * **Language** is language in use for the SAP Business One company.   * **Language** is language in use for the SAP Business One company.
   * **License Server** is the server and port where the DI Server will connect to get its license information.   * **License Server** is the server and port where the DI Server will connect to get its license information.
     * The format is Servername:PortNumber (e.g. Server1:30000).     * The format is Servername:PortNumber (e.g. Server1:30000).
-    * The default port for SAP Business One license server is 30000. This should be used unless otherwise advised by Third Wave support.+    * The default port for the SAP Business One license server is 30000. This should be used unless otherwise advised by Third Wave support.
  
 ===== SMTP Connections ===== ===== SMTP Connections =====
  
-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 installations will only have one SMTP connection. However, there is no technical restriction on the number of connections that are defined.
  
-{{  :bw:gcimage7.png?384x243  }}+{{ :bw2:bizweaverconnectionmanager8.png |}}
  
   * **Server** is the server where your SMTP application is found   * **Server** is the server where your SMTP application is found
-  * **Port Number** is the specific communication port used to connect to the SMTP application. Port 25 is the most common when connecting to an internal server. Port 465 or 567 are common when SSL is in use. Contact your system administrator if you are not sure of what value to use.+  * **Port Number** is the specific communication port used to connect to the SMTP application. Port 25 is the most common when connecting to an internal server. Port 465 or 587 are common when SSL is in use. Contact your system administrator if you are not sure of what value to use.
   * **Enable SMTP Credentials** (Username & password) \\ <WRAP info round center> Your installation may not require SMTP credentials to send mail from Bizweaver. However, identifying a valid user in this step is required to use the error handling functions of Bizweaver. </WRAP>   * **Enable SMTP Credentials** (Username & password) \\ <WRAP info round center> Your installation may not require SMTP credentials to send mail from Bizweaver. However, identifying a valid user in this step is required to use the error handling functions of Bizweaver. </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 172: Line 172:
 ==== Email Setup for Microsoft Office365 ==== ==== Email Setup for Microsoft Office365 ====
  
-There are three different options for using Microsoft Office365 as your SMTP connector to send email from Bizweaver. Fortunately, the simplest, and recommended, option works quite well. The following information is from Microsoft.+There are three different options for using Microsoft Office365 as your SMTP connector to send emails from Bizweaver. Fortunately, the simplest and recommended, option works quite well. The following information is from Microsoft.
  
 **Option 1 (recommended): Authenticate your device or application directly with an Office 365 mailbox, and send mail using SMTP client submission** **Option 1 (recommended): Authenticate your device or application directly with an Office 365 mailbox, and send mail using SMTP client submission**
  
-This option supports most usage scenarios and it's the easiest to set up. Choose this option when:+This option supports most usage scenarios, and it's the easiest to set up. Choose this option when:
  
-  * You want to send email from a third-party hosted application, service, or device. +  * You want to send an email from a third-party hosted application, service, or device. 
-  * You want to send email to people inside and outside your organization.+  * You want to send emails to people inside and outside your organization.
  
 To configure your device or application, connect directly to Office 365 using the SMTP client submission endpoint **smtp.office365.com**. To configure your device or application, connect directly to Office 365 using the SMTP client submission endpoint **smtp.office365.com**.
Line 187: Line 187:
 **How to set up SMTP client submission** **How to set up SMTP client submission**
  
-Enter the following settings directly on your device or in the application **as their guide instructs** (it might use different terminology than this article). As long as your scenario meets the requirements for SMTP client submission, the following settings will enable you to send email from your device or application.+Please enter the following settings directly on your device or in the application **as their guide instructs** (it might use different terminology than this article). As long as your scenario meets the SMTP client submission requirements, the following settings will enable you to send emails from your device or application.
  
 ^Device or Application setting      ^Value                                                         ^ ^Device or Application setting      ^Value                                                         ^
Line 193: Line 193:
 |Port                               |Port 587 (recommended) or port 25                             | |Port                               |Port 587 (recommended) or port 25                             |
 |TLS/ StartTLS                      |Enabled                                                       | |TLS/ StartTLS                      |Enabled                                                       |
-|Username/email address and password|Enter the sign in credentials of the hosted mailbox being used|+|Username/email address and password|Enter the sign-in credentials of the hosted mailbox being used|
  
 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  }} +{{ :bw2:bizweaverconnectionmanager8.png |}}
 ===== 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 emails 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  }}+{{ :bw2:bizweaverconnectionmanager9.png |}}
  
   - Select the **Exchange Version** from the drop-down list.   - Select the **Exchange Version** from the drop-down list.
 +    - Versions include: 2007_SP1,2010,2010_SP1,2010_SP2,2013,2013_SP1,2015,2016
   - Enter the **Username** and **Password** for a user that can access Exchange.   - Enter the **Username** and **Password** for a user that can access Exchange.
   - Enter the **Domain** name of which the Exchange service is a member.   - Enter the **Domain** name of which the Exchange service is a member.
Line 211: Line 211:
  
 <WRAP center round help 60%> <WRAP center round help 60%>
-Only one mailbox can be monitored per connection.  If you want to monitor multiple mailboxes you will need to create a connection for each one.+Only one mailbox can be monitored per connection.  If you want to monitor multiple mailboxes, you will need to create a connection for each one.
 </WRAP> </WRAP>
  
Line 227: Line 227:
 ==== Basic Authentication ==== ==== Basic Authentication ====
  
-{{  :bw:gcimage8.png?475x249  }}+{{ :bw2:bizweaverconnectionmanager10.png |}}
  
   - Select the **Basic Authentication** radio button.   - Select the **Basic Authentication** radio button.
Line 235: Line 235:
 ==== oAuth 2 Authentication ==== ==== oAuth 2 Authentication ====
  
-{{  :bw:gcimage9.png?469x331  }}+{{ :bw2:bizweaverconnectionmanager11.png |}}
  
   - Select the **oAuth 2 Authentication** radio button.   - Select the **oAuth 2 Authentication** radio button.
Line 242: Line 242:
     - The remaining fields that can be accessed will change based on the Grant Type.     - The remaining fields that can be accessed will change based on the Grant Type.
     - 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.   - 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 249: Line 249:
 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** 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}}+{{ :bw2:bizweaverconnectionmanager12.png |}}
  
   - 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.   - 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.
Line 257: Line 257:
 </code> </code>
   - **Database** is the SAP Business One company database name.  This value is case sensitive.   - **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.+  - **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.
  
 ====== Delete A Global Configuration ====== ====== Delete A Global Configuration ======
  
-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.+To delete a connection, double-click on the desired connection to delete. In the upper right corner of the connection, select "Delete Connection." 
 + 
 +When a 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 is listed in the lower area of the window. Replacement connections must be specified, or the deletion process will not continue.
  
-{{  :bw:gcimage10.png?472x160  }}+{{ :bw2:bizweaverconnectionmanager13.png |}}
  
-  - Option 1 is to use the “Replace all” option to update all listed workflow (Task) steps with a new connection.+  - Option 1 uses the “Replace All” option to update all listed workflow (Task) steps with a new connection.
       - Use the drop-down to select a connection from the list presented.       - Use the drop-down to select a connection from the list presented.
       - The “New Connection” value for all rows is set automatically.       - The “New Connection” value for all rows is set automatically.
   - Option 2 is to update each workflow/step individually.   - Option 2 is to update each workflow/step individually.
       - Use the drop-down in each row to select a connection from the list presented.       - Use the drop-down in each row to select a connection from the list presented.
-  - Option 3 is use options 1 and 2 together.+  - Option 3 is to use options 1 and 2 together.
       - Use option 1 to update the “New Connection” value for all rows.       - Use option 1 to update the “New Connection” value for all rows.
       - Use option 2 to update individual rows to a different connection as needed.       - Use option 2 to update individual rows to a different connection as needed.
-  - Click [**Replace and Save**] to complete the update.+  - Click [**Save**] to complete the update.
   - Click [**Close**] to exit without saving any changes.   - Click [**Close**] to exit without saving any changes.
  
  
  
bw2/global_connections.1612740256.txt.gz · Last modified: 2021/02/07 18:24 by akoehler

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