SYSPRO 8 Espresso Service
Exploring
This web service is used to power the SYSPRO Espresso mobile application and SYSPRO Espresso from the browser. It generates the user interface for SYSPRO Espresso and controls the flow of data and business logic from SYSPRO Espresso to the core SYSPRO product.
Also installed with SYSPRO Espresso is the SYSPRO 8 Espresso File Service which controls the self-healing of components from SYSPRO into the SYSPRO 8 Espresso Service (required when applications in Espresso are updated and the SYSPRO 8 Espresso Service is installed on a separate server).
This service is used by:
- SYSPRO Espresso
Starting
-
Microsoft .NET Framework 4.6
-
SYSPRO 8 Service Upgrade Manager
-
SYSPRO 8 e.net Communications Load Balancer
A valid endpoint must be configured in the Setup Options program of SYSPRO 8.
-
SYSPRO 8 Espresso Notification Service
-
Internet Information Services (IIS)
-
SSL Certificate
A valid SSL certificate is required to run the Espresso application and connect to an IP address on an Android device.
-
Multi-Factor Authentication and SSO using Active Directory are not currently supported with SYSPRO Espresso.
-
This service is installed using the SYSPRO Installer Application.
Solving
You can debug this service by editing the associated config file in elevated mode (i.e. with administrator privileges).
The Web.config file is located in the folder to which you installed the service and defaults to: C:\inetpub\wwwroot\SYSPRO8Espresso.
You can view monitoring and troubleshooting messages about this service using the Event Viewer function in Windows:
(Control Panel > System and Security Administrative Tools > Event Viewer > Applications and Service Logs)
This service outputs an event log to the SYSPROEFS file.
You can start, stop, restart and configure this service using the Services function in Windows:
(Control Panel > System and Security Administrative Tools > Services)
Service operators are created by SYSPRO and are used by SYSPRO services to obtain information about SYSPRO.
The service operator code starts with a double underscore to differentiate them from other operators. A default company code must be assigned to each service operator within the Operator Maintenance program, as we use the company code to log in the service operator via e.net .
The following is a list of service operators and their function within SYSPRO:
-
The __ADSYNC service operator is used by the SYSPRO 8 Active Directory Sync Service to push Microsoft Active Directory (AD) information into SYSPRO for Active Directory managed operators.
-
The __BOT service operator is used by the SYSPRO 8 Bot Service.
-
The __DFM service operator is used by the SYSPRO 8 Document Flow Manager Folder Poller and SYSPRO 8 Document Flow Manager Queue Poller to monitor folders, send files to the queue and process files.
-
The __ESP service operator is used by the following services:
-
SYSPRO 8 Espresso Service,
-
SYSPRO 8 Espresso Notification Service,
-
SYSPRO Espresso Development Plugin and the
- SYSPRO Avanti Web Service to obtain information for the password reset and forgot password functionality.
-
-
The __POS service operator is used by the SYSPRO 8 Point of Sale Services to determine and validate the setup options and required credentials at start up, update the required databases and post to SYSPRO (if the Point of Sale operator doesn't have access to SYSPRO).
-
The __RUL service operator is used by the SYSPRO 8 Rules Engine Service and the SYSPRO 8 Rules Data Service.
-
The __SA service operator is used by the SYSPRO 8 Analytics service to make business object calls.
-
The __SAI service operator is used by the SYSPRO 8 Machine Learning service.
-
The __SRS service operator is used by the SYSPRO 8 Reporting Host Service and the SYSPRO 8 Cognitive Service to manage client-side report printing.
-
Only specific services use service operators to log in via e.net.
-
SYSPRO creates service operators by copying the ADMIN operator. If the ADMIN operator record doesn't exist (i.e. it may have been deleted), then the current operator is used when saving system details from the Setup Options program.
Service operators are signed in by a SYSPRO service and are used for any functionality that is required by the service to obtain information about SYSPRO.
Normal operators sign in to SYSPRO with a username and password. They access certain programs and functions to perform specific tasks.
For example:
the __SRS service operator is used by the SYSPRO 8 Reporting Host Service to obtain information about the companies in an environment, but it isn't used by the business object to retrieve the data for a report, as that would be the specific normal operator that submits the request for the report.
Referencing
You should only update this file for temporary debugging purposes (i.e. not as a method to update values for the service).
Any temporary changes made to the configuration files are reset to their original installation values when this application is next updated. Because these temporary changes are not carried forward, forgetting that you made them could hamper troubleshooting efforts if unexpected issues arise.
Key | Description |
---|---|
Debug mode |
<add key="debugmode" value="true"/> This flag puts the Espresso service into debug mode. Components that are currently in debug mode can be used inside Espresso applications. Logging is also performed both inside the web browser console as well as on the server itself. The log file for the Espresso web service is written to the temporary folder from which Espresso runs (typically c:\windows\temp). |
Menu tile refresh rate |
<add key="menutilerefreshrate" value="10000" /> The menu tile refresh rate determines how often live tiles are refreshed in Espresso menus. The value is set in milliseconds and should be set after considering the types of live tiles in use, along with the data they require. |
Attempt relogon |
<add key="attemptrelogon" value="true" /> When this key is set to true, Espresso tries to log operators back into the SYSPRO e.net layer if they are unexpectedly logged off by the system. This provides a more seamless experience inside Espresso. This should be set to false if users shouldn't be logged back onto e.net if logged off. |
Session expiry duration |
<add key="sessionexpiryduration" value="0.02:00:00" /> This field defines how long an Espresso session can be idle before the session expires and you need to login again. |
Enable translation |
<add key="enabletranslation" value="false" /> When set to true it enables translation throughout the Espresso product. This has a significant performance effect on Espresso when applications are loaded for the first time, because the translation for the application must also be loaded. This should only be set to true on sites that use translation. |
Administrator contact details |
<add key="adminname" value="Jo Soap" /> <add key="adminnumber" value="0114611000" /> <add key="adminemail" value="jo.soap@suds.com" /> These define the system administrator's contact details that will be displayed in the Account Details tab of the Espresso menu. |
Base dir |
<add key="basedir" value="0"/> This defines the SYSPRO base directory number to use on the SYSPRO Application Server for this install of the Espresso service. |
Espresso server external name |
<add key="espressoserverexternalname" value="http://localhost" /> This must be set to the external IP or DSN name of the Espresso server. If images are not displayed in Espresso, then this address may be incorrect. |
Local storage roll over percentage |
<add key="OpenSessionsCacheFileName " value="" /> This sets the name of the Espresso Open Session Cache file. This defaults to the temporary folder from which the Espresso Web App is run (typically c:\windows\temp\EspressoOpenSessionsCache.dat). This is useful when multiple versions of the Espresso Web Application are installed on the server. |
Open sessions cache filename |
<add key="compressofflinedata" value="false" /> This specifies whether data cached on the device should be compressed. This allows for more data to be stored on devices, but may have an affect on the performance of the device. It also makes debugging of issues more difficult and should be turned off for debugging purposes. |
Server calls timeout |
<add key="servercallstimeout" value="120000" /> This sets the timeout value in milliseconds for calls to the Espresso server. The connectivity environment in which SYSPRO Espresso is used, as well as the speed of the server, should be considered when this is set. |
Application Redirect |
<add key="applicationredirect" value="Suppliers" /> This redirects SYSPRO Espresso to a specific application every time a user logs in, instead of displaying the normal logon screen. |
Application Redirect Session Data |
<add key="applicationredirectsessiondata" value="" /> This sets the Espresso session data when a user logs on (for every user). This can be used with Application Redirect to open a specific supplier or stock code when the relevant application is opened automatically. |
- Additional application settings within the file:
Key | Description |
---|---|
Workflow Service |
<add key="workflowservice" value="net.tcp://localhost:90/SWS" /> This indicates the SOAP address of the SYSPRO 8 Workflow Service to use when calling workflows. This only has an effect if the workflow is called explicitly from an Espresso Application. |
Enable Global Barcoding |
<add key="enableglobalbarcoding" value="true" /> This enables/disables global barcoding. If true then all browsable and tracking fields will use the associated barcoding setup. If false then only fields marked by developers as barcoded will use associated barcoding. If disabled, then all barcoding is disabled in Espresso. |
Disable Scrolling Override |
<add key="disablescrollingoverride" value="false" /> This lets you disable the scrolling override in Espresso. It defines whether the scrolling and tab workaround should be used to fix scrolling issues in Espresso. This is set to false by default, but can be turned off by setting it to true for customers who don't experience scrolling issues. This depends on the types of applications that are used. |
Post Media Type |
<add key="postmediatype" value="PNG" /> This sets the multimedia type to save images from Espresso to another device, like the signature pad or a native device camera. It defaults to PNG if left blank. If you have problems using the image then try setting this to JPG. |
- There are also client settings which relate to connectivity between SYSPRO Espresso and SYSPRO ERP via SYSPRO WCF. These are described below:
Key | Description |
---|---|
SYSPRO WCF net.tcp endpoint address |
The first endpoint is for the SYSPROWCFServiceReference.ISYSPROWCFServiceSoap contract. This contract is the WCF net.tcp address on which SYSPRO Espresso communicates. It defaults to net.tcp://localhost:31001/SYSPROWCFService. |
SYSPRO Espresso notification service endpoint address |
The second endpoint is the pointer to the EspressoNotificationService.IEspressoNotification contract. This contract is the net.tcp address that SYSPRO Espresso uses for notifications that will be sent out via SYSPRO ERP via the SYSPRO 8 Espresso Notification Service. It defaults to net.tcp://localhost:30180/SYSPROEspressoNotificationService. |
SYSPRO Espresso file server endpoint address |
The third endpoint is the pointer to the EspressoFileService.IEspressoFileService contract. This contract is the pointer to the SYSPRO 8 Espresso File Service that is used for copying files from the SYSPRO folders to the SYSPRO Espresso folder in c:\inetpub\wwwroot. It defaults to net.tcp://localhost:30181/EspressoFileService. |
Copyright © 2024 SYSPRO PTY Ltd.