|
WEBCASTS |
|
|
|
|
|
|
November 20, 2008 |
|
|
|
See Data Access
Studio live
|
|
|
|
|
|
|
|
|
UPCOMING EVENTS |
|
|
|
|
|
|
Nov 4-5, 2008 UK Users
Conference
|
|
|
|
Ascot Racecourse, Berkshire, UK
|
|
|
|
|
|
|
|
Nov 19, 2008 Southern
California Users Conference
|
|
|
|
Long Beach Grand Convention Center, Long
Beach, CA
|
|
|
|
|
|
|
|
| |
Web Server Install Instructions
Use Web Server configuration to deploy DataAccessStudio across a Wide Area
Network. This configuration is most generic way to deploy DAS as it will
work within your LAN and in your WAN.
- ReportsNow recommends that you use a dedicated machine to host Data
Access Studio. IMPORTANT! Do not use your deployment server
as the DAS Web server. This machine should be in close network
proximity to the E1/World database. Please refer to the
architecture diagram for the
network topology.
Step 1 - EnterpriseOne ONLY (if World skip to Step 2)
- On the dedicated server (hereafter referred as the DAS Web Server), you
need to install an EnterpriseOne Fat Client. The DAS Web server will share
this install with the clients that connect to the server. You will
update this Fat Client install with update packages/full E1 packages as they
become available. The advantage is that this is the only machine that
you will have to update for the DAS Web clients.
- Once you have an EnterpriseOne fat client installed, you need to install
Data Access Studio to the DAS Web Server. If you do not have a drive
mapped to your deployment server share, map a
drive to the <Dep Server Name>\B7333
- From your mapped drive, run: <Dep Server Name>\B7333\Data Access
Studio\Setup.exe
- If you do not have the .NET framework on your workstation, the setup
program will launch the .NET installer. When prompted to do so, install
the .NET framework to your workstation. This installation takes about 5
minutes. You only need to install the .NET Framework once.
- Once the .NET pre-requisite is installed, setup presents the installer
welcome screen:
- Click "Next".
- Pick the default location that the Installer provides. Select the "Everyone" radio button. Click
"Next".
- Click "Next" again to begin the installation.
- Once the installation is complete, press "Close".
- If the machine's MDAC level is below 2.8, setup.exe will invoke the MDAC
installer. This install is optional unless you intend to use the OLE DB
features of DAS. If you perform the MDAC install, then you will be
required to reboot this machine. To cancel the MDAC install, press
Cancel. Otherwise install the updated MDAC drivers.
Step 2 - Set up the Data Access Studio Web (E1 and World)
- Once the DAS client is installed on your server, open Start->Run and type:
"RunDASWebSetup". This converts the DAS workstation into a DAS
Web Server.
Fill in the fields as follows (or accept the defaults to test):
| Field |
Description |
| Channel |
Select http. |
| Formatter |
Select Binary. |
| Compress |
Check if you want to compress the network traffic. Check this
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. Select from the
following encryption algorithms: DES, TripleDES, RC5, and Rijndael.
Also select the key size you want for your encryption. Higher key
sizes correspond to higher security. |
| Listener Port |
The port for the DAS Server service. IMPORTANT! If you run a
firewall, make sure this port is open. |
| 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. |
| Lease Timeout |
The number of seconds a DASWorker 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 clients experience timeouts when
running DAS, try increasing the value of this parameter. |
| Signin 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. |
| Firewall Machine Name |
Leave blank. You can fill in this field with your
firewall name to troubleshoot WAN connection issues. |
| URL |
The IP or machine name of the DAS Web Server. |
| 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. |
- Once you have filled in the above fields, press "Setup Web":
You will see a report of the setup steps. These steps convert the
Data Access Studio workstation to a DAS Web Server. When you see the
"Setup Succeeded" message, that means the DAS Web server is running and ready
to take client requests. If a setup step fails, please follow the
recommended resolution in the report.
IMPORTANT: The Web Setup creates and starts a service named Data
Access Studio Server in your services. If the login for this service
does not have sufficient privileges to launch process (DASWorker.exe), then
the web server will give an error when users try to sign in.
NOTE. Once you RunDASWebSetup successfully, from that point
onward, every time you update Data Access Studio on the LAN server, the update
will automatically run RunDASWebSetup.
Enter an Alias such as "DASWeb". Click OK. This will create
a DASWeb virtual directory in IIS.
In IIS, allow anonymous access to the DASWeb folder.
Configure IIS to run HTTPS (encrypted HTTP) for your new virtual
directory. Please have a qualified IIS resource setup IIS security
to prevent unauthorized access to Data Access Studio.
- To run DAS from a browser, type: "http://<WebServerName>/DASWeb/DASWeb.exe".
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. You may place DASWeb.exe as a
hyperlink on a web page as well.
- If this is the first time that you run DAS in a WebBrowser, you need to run DASWebSecurity.msi once.
This sets up the correct .NET permissions for DataAccessStudio to run in thin
client mode.
Troubleshooting
If you are having trouble connecting from a client machine, use these steps
to determine where the difficulty lies:
- Run DataAccessStudio.exe directly from the shortcut on the DASWeb Server.
You should see a sign on screen which will let you sign in and access the
software.
- If this does not work, check you E1 Full Client install or jde.log.
- If this does work, then the problem lies in the IIS or network setup --
read on
- Click your DASWeb.exe link from a client browser. if you see the initial
Data Access Studio splash screen but then it disappears, chances are you need
to set "Anonymous" access in your IIS setup (see above).
- If you get the message cannot connect to Data Access Studio server, make
sure the Data Access Studio service is running on the DAS Web Server.
Also make sure that the server has the ports you specified open on your DAS
Server firewall. For instance if you chose the defaults: Start: 9000
with 30 connections, then you have to open ports 9000-9031.
- If you get the sign on screen that means the client can connect to the
start port and the Data Access Studio Service is running. If you sign in
and you get "Login failed" this could be due to the following:
- Log in was not valid - try retyping
- Log picked an environment that was not installed on the DAS Web server.
If you want to log into a particular environment, then the pathcode for that
environment must be installed on the DAS Web Server.
- The Data Access Studio service default login has insufficient privileges
to start a process. When a user logs in successfully, the Data Access
Studio service on the DAS Web server launches a DASWorker process. If
the service login rights do not have this permission, then the login will
fail. Try changing the login for the service to another account (such
as an admin account) that is likely to have this permission.
- The login will fail if the required port range is blocked by the DAS Web
Server firewall (see above).
- Ideally, your browser client should click the DASWeb.exe link and Data
Access Studio will run automatically. Sometimes, Internet Explorer can
disrupt this process and prompt the user to run first. One know plugin
that causes this disruption is McAfee Site Advisor. Consider disabling
this plugin in Internet explorer to avoid the prompting dialog box when you
click the DASWeb.exe hyperlink.
Back to Install
Instructions |
|
|
|
