E1 Install Guide
This Data Access Studio (DAS) guide provides comprehensive information for installing and licensing DAS. This manual describes downloading DAS from the Download Center of the ReportsNow website and installing it to your dedicated DAS server. These instructions apply to the following JDE E1 releases:
- E1 8.9
- E1 8.10
- E1 8.11
- E1 8.12
- E1 9.0
- E1 9.1
- E1 9.2+
To successfully install and run Data Access Studio, your system must meet the following minimum requirements.
Data Access Studio Server
- Windows Server 2008 SP2, or greater
- 2 processor cores per 20 clients (1 processor core per 20 users
- Automator requires at a minimum 1.5 additional processor cores per queue
- 4 GB RAM per 20 clients (2GB per 20 users minimum)
- Use of server-side summarization requires a minimum 4 GB RAM per 20 clients
- Automator requires a minimum of 2GB additional memory per queue
- .NET Framework v4.6 or greater
- Internet Information Services (IIS) 7.0 or greater
- Full EnterpriseOne client install Xe or higher
For External Data sources:
- Appropriate 32-bit or 64-bit drivers for the targeted databases
Microsoft Excel 2013, 2016, 2019, or 2021. Excel Office 365 not supported.
Some of these Excel versions also require a minimum OS level) Please see the current knowledge base article regarding Excel certification.
Data Access Studio Client
- Windows 7 or greater
- 4 GB RAM (2 GB Minimum)
- .NET Framework v4.6 or greater
- Microsoft Excel 2013, 2016, 2019, 2021, or Office 365
- Browser Support
- Microsoft Edge (version 87 or later)
- Internet Explorer
The following browsers are not supported, however have been known to work with appropriate Microsoft ClickOnce plug-ins:
- Mozilla Firefox
Downloading and Installing/Upgrading DAS
Follow these steps to download the latest version of Data Access Studio.
Download DASUpdate.exe from our Download Center to the DAS server by clicking the Download DAS8 button.
If this is just an upgrade, and you have a Web deployment, please stop the DAS Automator and Data Access Studio services, then kill any DASWorker.exe processes before continuing. If you are a DAS mobie customer and have DAS mobie hosted on the same server as your DAS web server, please also download the MOBIEPortal.zip file (click the Download Mobie button) to the same directory as DASupdate.exe so that the installer can detect it during the installation.
Run the DASUpdate.exe you just downloaded to your DAS server and click Setup.
Please review the End User License Agreement, and if you accept the terms please click the “I Accept the Agreement” option and click Next.
Sign into JDE EnterpriseOne using an environment that is part of the EnterpriseOne client installation on the DAS server (for example, DV920 or PD920).
If this is the first time you are installing Data Access Studio, the JDE User ID provided here must have permissions to create and generate the “FDASPROP” table in your system data source.
Sign into JDEdwards.
If you do not see the EnterpriseOne (E1) sign in, you either do not have the JDE E1 dev client installed or you are a JDE World customer. If you are on JDE World, please refer to the Data Access Studio install guide for JDE World customers
Select the Advanced checkbox only if you wish to unzip the setup files to a directory; otherwise the files will be placed in the user’s temp directory. If you intend to install DAS software on other additional servers (e.g. a dedicated Automator server, or multiple DAS servers) or a Citrix deployment, then select “Advanced” and specify a network share location to make it easier to install on the other servers.
The FDASPROP table is the main storage table for Data Access Studio. This is the table where DAS stores layouts, published reports, user preferences, etc. DASUpdate.exe creates this table in your system data source to ensure that DAS users have access to FDASPROP regardless of the environment selected when signing into DAS.
Because there is only one FDASPROP table for your entire enterprise, you do not have to worry about environments promotion (e.g. DV->PY->PD). After DASUpdate.exe creates FDASPROP, it then creates an OCM mapping for FDASPROP. This way DAS will always know where FDASPROP is located regardless of the signed-in environment.
If you are applying an update/upgrade, the installer will skip the FDASPROP generation screen as it will detect that this table already exists. In this case you will see the following window:
The summarized installation plan is displayed. Click Next.
If the JDE User ID failed to create this table, you will be prompted to enter database credentials. Please enter the database credentials to create the table and click Next.
The installer will generate the search item cache. This step could take several minutes.
Click Next once the search completes and you see the Deployment installation succeeded window.
Once you have created the FDASPROP table, you may deploy DAS in one or more of the following ways:
Web - Your users are located in a Wide Area Network (WAN). Users run DAS from a web page link hosted by IIS (Internet Information Services). DAS consumes resources on the DAS Web server, the user’s workstation and the database.
Citrix - In Citrix deployment, your users do not have a JDE E1 Full client and are typically located on a WAN. Once installed and published on Citrix, your users access the Citrix server and run DAS. DAS consumes resources from the Citrix server and database.
Web Install Procedure
Use Web Server configuration to deploy Data Access Studio across a Wide Area Network. This configuration is the most generic way to deploy DAS as it will work within your local area network (LAN) and in your WAN. ReportsNow recommends that you use a dedicated machine to host Data Access Studio.
Do not use your JD Edwards deployment server as the DAS Web server. The DAS Web Server should be in close network proximity to the E1 database.
Once you click Next at the install summary window, you will see this window with “Launch Data Access Studio setup on this machine” selected. Click Finish.
After you click Finish, you will see the installer welcome screen. Click Next.
Accept the License Agreement and click Next.
Click Install to begin the installation.
Once the installation is complete, click Finish.
After DAS is installed on your web server, you need to run a script to convert it from a Workstation/Standalone mode to a Web mode. Go to the directory where DAS is installed Step 4 and run WebSetup.exe. The script will automatically configure IIS.
If this is an upgrade, it will automatically prompt you to run Web Setup. Click Yes to continue.
The default setting is for 20 connections. To accommodate more users, increase Maximum Connections. For example, if you have a total of 50 licenses, you may want to change that to 55. For more information on all the settings, please review the table below. Click Setup Web when finished.
Field Description Channel Select http. Compress This is checked by default and it helps if you are running over a slow network connection or WAN. Encrypt Check to encrypt the network traffic. Check this if you are running over an unsecured network. Start Port The port that the DAS Server service will start with to assign client connections Maximum Connections The maximum number of allowed client connections. Use this setting to limit the number of users per server as you see fit. IMPORTANT! If you run a firewall, make sure the range of Start Port to Start Port + Maximum Connections is open. The default setting is 20. Increase this value to be at least the number of licenses you purchased. Lease Timeout The number of seconds a DASWorker process will stay alive after a client session has disconnected. When the client session ends abnormally, this timeout ensures that the corresponding server executable gets cleaned up. Using the default timeout is recommended. IMPORTANT! If your users experience timeouts when running DAS, try increasing the value of this parameter. Sign-in Timeout Once a user signs in, this is the number of seconds the server has to create a session for the user. If users have trouble signing in, try increasing this value. Otherwise, the default timeout is recommended. Idle Timeout If set to a non-zero amount, this will set the number of minutes the software will allow the client to run before automatically shutting it down. For instance, if this is set to 30 minutes, then if the web client is idle for 30 minutes, the software will issue a 20 second idle warning and then shutdown the client -- thereby freeing the concurrent license and any system resources the client held. This will not disconnect any users with unsaved work. DAS Web Server IP or Machine Name The IP or machine name of the DAS Web Server that is known by the client machines that will connect to it. Firewall Machine Name Leave blank. Populate this field with the name the server is known by from client machines only in cases where the server has multiple NICs that serve different IP’s or if the IP address the machine is communicating over is different server name or IP than the client knows the server by. Reinstall Services When you press Setup Web on the menu bar and this field is checked, the setup program will display a message box that warns you that you are about to setup the Web Server. Any DAS client that is connected to the existing Web server will be disconnected. Prompt before setup When you press Setup Web on the menu bar and this field is checked, the setup program will display a message box that warns you that you are about to setup the Web Server. Any DAS client that is connected to the existing Web server will be disconnected. Mixed-case password Check this box if you are using LDAP security or other login authentication that accepts passwords that are not all uppercase.
You will be prompted with the following window. We recommend changing the service accounts from Local System to an account that is a member of the machine’s Administrators group. This could be a domain account user but must be part of the local admin group.
If this is an upgrade, you will not be prompted for this. It will continue to use the existing service account.
When the install is complete you will see “Setup Succeeded”.
(For mobie customers and mobie Upgrades only): If you are a DAS mobie customer and mobie is hosted on the DAS web server, and you initially downloaded the DASUpdate.exe and MOBIEPortal.zip file in the same directory, it will bring up the following window. The WebSetup and mobie configuration windows may both come up at the same time. It does not matter which order they are configured. If the MobiePortal.zip is not in the same directory as DASUpdate.exe then you will need to select it. Click the visual assist (…) for the installation zip file location and pick the MOBIEPortal.zip file you downloaded, then click Configure.
To run DAS from a browser, type: "http://<WebServerName>/DASWeb/ " . If you have a slow connection, DAS may take up to a minute to load. Once DAS is loaded, the browser will cache the downloaded information so that future sign-ons go faster.
Citrix Install Procedure
There are two primary variations on how to install DAS in a Citrix environment:
Citrix-only approach: Install DAS completely on the Citrix server with all of its necessary prerequisites (in particular, the JDE client install).
Hybrid approach: Install DAS on a web server (see Web Install Procedure), and then install the client on the Citrix server to connect to the DAS web server.
Citrix-only approach procedure:
Perform the Citrix install for each server where you want DAS. The Citrix server must have a full JDE E1 client install.
Prior to installing DAS, it is necessary to change the server to install mode by running “change user /install” from the command prompt. After the installation, you must run “change user /execute” to bring it out of install mode.
Once you click Next at the install summary window, you will see this window. Click Finish.
Accept the License Agreement term and click Next.
Click Install to begin the installation.
Once the installation is complete, click Finish.
You can now publish Data Access Studio to your users.
The executable location is the location from Step 4:
C:\Program Files (x86)\ReportsNow\Data Access Studio\DataAccessStudio.exe
Hybrid approach procedure
Installing DAS on Citrix using the hybrid approach assumes that you have already completed a normal DAS Web client installation on another server. In this configuration, the Citrix server acts very much like a Web client with one important difference. The difference is that the DAS client should be installed and published on the Citrix server as opposed to publishing the Web link that Web client users would use when accessing the DAS Web server. Publishing the Web link on the Citrix server has couple of problems:
Citrix on Windows operating systems prior to Windows Server 2012 R2 do not support Microsoft .NET ClickOnce deployment, which is what is used by DAS when connecting via the Web URL.
Resource consumption is much higher, because each user has their own copy of the DAS application as opposed to using one shared installation.
To install the DAS client on the Citrix server using the Hybrid approach, you must first copy the installation/setup files from the DAS Web server to the Citrix server. The location of the install files will be in the directory that you specified in Step 7 (under Downloading and Installing/Upgrading DAS section).
Once you have copied over the installation files, it is necessary to change the server to install mode by running “change user /install” from the command prompt. After the installation, you must run “change user /execute” to bring it out of install mode. Run Setup.exe and install DAS.
Lastly, copy the file called Remoting.txt that can be found in the DAS installation directory on your DAS Web server (typically C:\Program Files (x86)\ReportsNow\Data Access Studio\Remoting.txt) to the DAS installation directory on your Citrix server.
At this point, you will want to publish the DataAccessStudio.exe application on the Citrix server to your Citrix users.
Maintenance Considerations for Hybrid approach
To maintain this installation, the version of DAS installed on the Web server must be kept in sync with the version installed on the Citrix server. Any time an updated installation is performed on the DAS Web server, the Citrix server should also be updated using the mechanism described above.
Similarly, the Remoting.txt file should also be kept in sync. If any changes to configuration options in the DAS WebSetup utility are made on the DAS Web server, these will result in changes to the Remoting.txt file and the Remoting.txt file should again be copied to the Citrix server.
Some customers opt to simply copy the complete DAS Web server’s installation directory to a known, stable location on the Citrix server rather than use the Setup.exe to install. This mechanism also works fine, though DAS will then not appear with its current version number as an installed application on the Citrix server.
Requesting and Importing License Key
Sign into Data Access Studio as DAS Administrator.
If you are a new customer, you will be prompted to Request License, Import License, or Cancel.
Click on Request License.
Copy and paste the information and email it to email@example.com
Once we receive the request, ReportsNow will generate a 30-day key and email you the license file. Upon receipt, save the file to a local folder and click Import License to import the file.
As of 7.0.52 and greater, for new installs, you no longer need to create a DASADMIN user in JDE to access the Data Access Studio as an administrator. The JDE user ID that was used to install DAS will automatically be designated to be the new DAS administrator. You can now assign other users to be a DAS Administrator as well by giving them the “DAS Administrator” permission under Work With Security.
Setting up DAS Automator
DAS allows authorized users to schedule reports to run on defined Automator servers. The output of these reports can be emailed, saved to the file system, or even saved to a database (via our mobie® product). Please verify that Excel is installed on the DAS web server.
Sign into DAS as DAS Administrator
Click Admin > Email Providers
Click New Provider and configure it to reference your email system.
Click Test Email. This should send out a test email (to the email address listed in the ‘From Email’ field. If it is setup correctly, it will display a dialog box saying it was successful sending the email.
Click OK > Save > Close
Click Admin > Automator to bring up the Automator Server control.
Click Add Server. This will bring up the Server Setup window.
Server Name: Name of the server
Network Address: Network identification of the server with the two ‘//’ in front. Usually, this is the same name as the server, but it can be an IP address.
Run Limit: Inherit (uses the Run Limit specified in Global Settings).
Check the Enabled box and click OK.
Click Add Queue button.
Give a name for your Queue and check the Enabled box.
Click the Start button under the Server section.
If you get any errors, try restarting the DAS Automator service in the Windows Services.