Network Installation Steps

Ensuring Requirements Are Met

A network installation of Developer Studio can consist of three types of machines. Each machine has its own requirements.

WebFOCUS Machine Requirements
WebFOCUS requirements and installation steps are provided in the WebFOCUS and ReportCaster Installation and Configuration manual for your platform. To use Project-based development, the WebFOCUS environment must store both server files (FEX, MAS, ACX) and client files (HTML, GIF, CSS) in the same directory for each project. This means WebFOCUS Client and the WebFOCUS Reporting Server must use the same APPROOT directory on the same machine. For example:
```
C:\ibi\apps
```
Note: The release of WebFOCUS must be the same release number as Developer Studio.
Developer Studio (Shared) Machine Requirements
Developer Studio can be installed on the same machine as WebFOCUS or on a separate machine. The requirements for a network installation of Developer Studio are the same as those of a non-networked installation. See Installing Developer Studio for requirements.

Note: You must provide a license for a network edition.

Since this machine will be accessed by multiple users over the network, you should use a machine that supports multiple connections and frequent network access.
Developer Studio End User (Remote) Machine Requirements
Machines from which you run Developer Studio off the network should meet the following requirements:
- Windows 8, Windows 7 Enterprise, Professional, and Ultimate editions, Windows 2008, 2008 R2, 2012, and 2012 R2 Server editions.
  Note: Due to a change in the compiler used to build Developer Studio, you may need to update the client machines with newer Microsoft Visual C++ libraries. Most machines have the required libraries, however, when running the Network version from a client machine, if your system does not have the required updates to allow this application to run, you will receive the following message attempting to run DevStudioLaunch.exe:
```
This application has failed to start because the application configuration is incorrect.
```
```
Reinstalling the application may fix the problem.
```
  To correct this issue, download and install the Microsoft Visual C++ 2008 R1 Redistributable Package (x86) from www.microsoft.com.
- Microsoft Internet Explorer. Internet Explorer components are required for Developer Studio. Internet Explorer 11 32-bit, Internet Explorer 10 32-bit, and Internet Explorer 9 32-bit are certified for Developer Studio.
- Adobe Reader. Adobe Reader XI (11) and Adobe Reader X (10) are certified with Developer Studio.
- Administrator Rights. Administrator rights are required during the initial launch of the network version from the client PC to set up required registry entries in the local machine area.

Installing Developer Studio

Install Developer Studio as explained in Installing Developer Studio. Be aware that when providing a network installation license, you will not have the option to install, or configure Tomcat or other supported configurations.

You must install using the proper license code for a network installation.

Configuring Developer Studio

How to:

Define a WebFOCUS Environment

To configure a network installation of Developer Studio, you must set up access to instances of WebFOCUS that are installed on your network. You do this by defining WebFOCUS environments.

Top of page

Procedure: How to Define a WebFOCUS Environment

If WebFOCUS and Developer Studio are on the same machine, start the WebFOCUS Reporting Server and ensure that the web and/or application servers are started.
Start Developer Studio from the Start menu by selecting Programs, Information Builders, WebFOCUS 81 Developer Studio, and WebFOCUS Developer Studio.
If prompted to log on, log on to the WebFOCUS Reporting Server.
If the Developer Studio Explorer appears, click the File menu and then Show Environments to display the Environments List. In some environments, the Environments List appears by default.
The Environments List lets you define connections to WebFOCUS environments.

The following image shows the Environments List dialog box.

The Environments List shows all WebFOCUS environments defined for Developer Studio. If you had previously installed Developer Studio, WebFOCUS environments may already be defined. Otherwise, only the localhost environment displays.

Note: If you previously set up this machine for a Developer Studio network installation, select your development environment and click Set Development Environment. Then click OK and restart Developer Studio.
Select localhost and click Properties to edit the default settings.
The WebFOCUS Environment Properties window opens, as shown in the following image.
Change the Description field to a name end users should see when they launch Developer Studio from remote machines. The name localhost will be misleading since they will be on their local machines.
Change the Host Name and port to access the web server where WebFOCUS is configured. Do not use localhost for the host name even if WebFOCUS is installed on the same machine as Developer Studio. When end users launch Developer Studio, localhost will resolve to the end users machine, and not the Developer Studio machine.
Optionally, you can specify the connection timeout, in seconds. You can specify a connection timeout between 120 seconds and 240 seconds if you are experiencing connection failure because of timeouts. The default connection timeout is 60 seconds.
Click through the panes of the WebFOCUS Environment Properties window to change any default options that are customized in your environment.
For additional information on defining environments, see Configuring the Local Reporting Server Security.
Click OK when you have set up the default environment.
If you wish to define additional WebFOCUS environments, click Add on the Environments List.
Click OK on the Environments List when you have defined all your environments.
The Developer Studio Explorer opens.
If prompted to log on, log on to the WebFOCUS Reporting Server.
Ensure that the Developer Studio Explorer functions properly and that your WebFOCUS environments are accessible.
Stop and start the product again to ensure that you can reconnect to the environment and to confirm operability.

Note: The WebFOCUS Reporting Server in the WebFOCUS environment should not be the WebFOCUS Reporting Server installed as part of Developer Studio. The WebFOCUS Reporting Server installed as part of Developer Studio supports a very limited number of users (agents) at one time.

Setting Up Access to the Network Installation

How to:

For developers to run Developer Studio off the network, you must complete the following on the Developer Studio machine:

Top of page

Procedure: How to Set Up Network Shares

You must set up a network share before launching Developer Studio from another machine. You can do this by turning the ibi directory where Developer Studio is installed, into a network share. If this is not practical for security reasons, then turn the DevStudio81 directory into a network share.

Note: If the share name is different from ibi, ensure that the new share name is used in the runfocshell.dat configuration file, as described in How to Configure the Network Settings.

To turn the ibi directory into a network share:

Open Windows Explorer or My Computer on the Developer Studio machine.
Navigate to and right-click the ibi directory.
Select Properties.
Click the Sharing tab, as shown in the following image.
Select Share this folder.
Click the Security tab and set permissions for the ibi share directory to Read & Execute and set permissions for the Developer Studio temp folder (install_directory\ibi\DevStudionn\temp) to Write access.
where:

install_directory

Is the directory in which Developer Studio is installed.

nn

Is the Developer Studio release number.
Grant access to the share locations for users accessing the network install. You can add users individually or you can add users to a group. A group is easier to maintain, and you can grant the required privileges to the group.
Click OK.

Top of page

Procedure: How to Copy the WebFOCUS Environments File (wfscom.xml)

Copy the WebFOCUS environment settings (wfscom.xml) into the DevStudio81\bin directory so they are available to remote Developer Studio users.

When you define WebFOCUS environments, settings are stored in the following file:

drive:\Users\user_id\AppData\
Information Builders\Roaming\wfscom.xml

where:

user_id: Is your Windows user ID.

Note: This file and directory may not be visible by default. To see this directory, open Windows Explorer, click Tools, choose Folder Options, and select the View tab. Then select Show hidden files and folders and click OK.

For remote machines to access the wfscom.xml file, you must copy it to a shared directory. The default location to use is:

drive:\ibi\DevStudio81\bin

When running Developer Studio off the network, a developer can use settings in this file or settings stored on the developer machine. The first time Developer Studio is run off the network, the settings in this file are used. When settings in this file are used, this wfscom.xml file is placed in the end user /Application Data/Information Builders/ directory on the remote machine each time Developer Studio is run off the network. If all developers use the settings in this file, they always see the same WebFOCUS environments.

Caution:

If a previous copy of wfscom.xml or wfscom.wfs is on a remote users machine, it is overwritten.
It is recommended that you run the network version of Developer Studio on client machines that do not have an existing installation of the product.
If a remote user changes WebFOCUS environment settings while accessing Developer Studio from the network, those changes are only saved to the end users machine. They will not be available to other users. They will also be overwritten the next time Developer Studio is launched, unless the user chooses not to update the environments from the network as explained in Customizing WebFOCUS Environments.
To change WebFOCUS environment settings for all users, you must change them on the shared Developer Studio machine and not from a remote machine. Then, you must recopy the wfscom.xml file to the DevStudio81\bin directory so it is available when Developer Studio is run from a remote machine.

Top of page

Procedure: How to Configure the Network Settings

Settings for when Developer Studio is launched off the network are in the following file:

drive:\ibi\DevStudio81\bin\runfocshell.dat

You must edit this file before launching Developer Studio from another machine.

Open the runfocshell.dat file in a text editor, such as Notepad.

Find the following line:

REGSTRING:LastUsedServer=Name to be supplied by Administrator

Change this line to specify the name of the default WebFOCUS environment. For example:
```
REGSTRING:LastUsedServer=WFEnvironment 
```
You should have set up this environment as explained in How to Define a WebFOCUS Environment.
Ensure that the correct host name, share name, and UNC directory path appears for accessing the DevStudio81 directory. The host name is set by the install, but you should confirm it and ensure that the share name is correct. Several lines contain this. For example:
```
WFSCOM:\\hostname\Ibi\DevStudio81\bin\wfscom.xml
SHLPATH:\\hostname\Ibi\DevStudio81\bin
```
If the host name is incorrect or you changed the share name, update all lines where the host name appears.
Be aware that the WFSCOM value specifies where remote machines look for the wfscom.xml file. You can change the name and location of this file if needed, but the file name must end in.xml. The file specified is copied to a remote users /Application Data/Information Builders/ directory on the remote machine. The file name on the remote machine will always be wfscom.xml regardless of the file specified by the WFSCOM value.
Save and exit the file.

Most of the settings in this file are created by the installation and should not be edited unless directed by Customer Support.

Warning: The DLL and OCX files listed in runfocshell.dat are loaded on remote machines when Developer Studio is loaded on those machines.

Installing Developer Studio Network Shortcuts

How to:

Install Developer Studio Network Shortcuts

An installation program is provided to create shortcuts to launch Developer Studio. Since no disk space is needed on the remote machine, this is referred to as a Zero Footprint WebFOCUS Developer Studio deployment.

Note: A Java JDK must be installed and you should be an administrator to the remote machine.

Top of page

Procedure: How to Install Developer Studio Network Shortcuts

To install shortcuts, perform the following on machines from which you wish to run Developer Studio off the network:

Open Windows Explorer or My Computer on the remote machine.
In the Address bar, type the host name of the machine where Developer Studio is installed using the Universal Naming Convention (UNC). This has the form:
```
\\hostname 
```
where:
hostname
Is the host name or IP address of the machine where Developer Studio is installed.
You should see a list of shared directories including the ibi and java shared directories you created.

Navigate the shared directories to:

\\hostname\ibi\DevStudio81\Utilities\Local_setup

Run the setup.exe application to install Developer Studio shortcuts.
The installation wizard launches and a Welcome window appears.
Click Next at the Welcome window.
You are prompted to create shortcuts.
Select which shortcuts to create and click Next.
Shortcuts are created.
Click Finish.

Note: To remove the shortcuts from the remote machine, use the Add/Remove Programs option in the Windows Control Panel. The shortcuts appear as Zero-Footprint WebFOCUS Developer Studio. Be aware that this does not remove the registry settings or files described in Network Developer Studio Settings on Remote Machines.

Launching Developer Studio

Reference:

Network Developer Studio Settings on Remote Machines

After installing the Developer Studio shortcuts, you can start Developer Studio off the network by selecting Programs from the Start menu, and then Zero-Footprint WebFOCUS Developer Studio.

Note: The first time that you launch Developer Studio from a machine, you must right-click the Zero-Footprint WebFOCUS Developer Studio shortcut, and then click Run as administrator.

If the WebFOCUS Reporting Server runs with security OPSYS, you may be prompted to log on.

If you receive other errors, review the steps in Setting Up Access to the Network Installation and ensure that WFSCOM is defined correctly in runfocshell.dat.

Top of page

Reference: Network Developer Studio Settings on Remote Machines

The first time you launch Developer Studio on a remote machine, the wfscom.xml file is copied from the shared networked machine to the remote machine. The file is normally placed in the following location:

drive:\Users\user_id\AppData\
Information Builders\Roaming\wfscom.xml

where:

user_id: Is your Windows user ID.

Other files are also created in this directory. This directory may not be visible by default. To see this directory, open Windows Explorer, click Tools, choose Folder Options, and select the View tab. Then select Show hidden files and folders and click OK.

When you launch Developer Studio on a remote machine, registry settings are created under:

HKEY_LOCAL_MACHINE\SOFTWARE\Information Builders

HKEY_CURRENT_USER\SOFTWARE\Information Builders

In addition, DLL and OCX files listed in the \\hostname\ibi\DevStudio81\bin\runfocshell.dat file are loaded.

Customizing WebFOCUS Environments

There are two ways to handle WebFOCUS environment settings when running Developer Studio off the network. Developers can use the common settings on the network or use settings specific to the developer machine.

Option 1: Use the common WebFOCUS environment settings on the network (default).
With this option, whenever a developer launches Developer Studio, the wfscom.xml file on the network installation is copied to the developers machine from the following location.
```
\\hostname\ibi\DevStudio81\bin\wfscom.xml
```
where:
hostname
Is the host name or IP address of the machine where Developer Studio is installed.
This means all developers who launch Developer Studio from this network location use the same environment settings. It also means that any WebFOCUS environment settings that developers change on their machines will not appear the next time they launch Developer Studio.
Option 2: Use customized WebFOCUS environment settings on a developers local machine.
With this option, the first time a developer launches Developer Studio, the wfscom.xml file is copied from the network to the developers machine. However, after Developer Studio is started on the developer machine, you can allow the developer to prevent the wfscom.xml file from being copied over in the future. By default, developers have the option to choose whether to copy over wfscom.xml or not.

On a developers machine, after Developer Studio has started:
1. Click Windows on the menu bar.
2. Click Options.
3. On the General tab, under Other Settings, clear the Remote Update Server Environment from Network check box.
This creates a registry setting on that machine that tells Developer Studio not to copy over wfscom.xml when Developer Studio is launched from the network.

You can control whether the Remote Update Server Environment from Network appears and whether wfscom.xml is automatically copied by editing the runfocshell.dat file. This file was introduced in How to Configure the Network Settings. The runfocshell.dat file specifies registry entries that great created on developer machines. The registry entries are created each time a developer launches Developer Studio off the network and will overwrite any previous entries.

By default the following lines appear:

REGISTRY:HKEY_CURRENT_USER\SOFTWARE\Information Builders\ DeveloperStudio REGDWORD:IsRemote=1: With these lines, wfscom.xml is copied and developers can choose whether or not to continue copying the file in the future.

You can choose not to show the option by changing the lines to:

REGISTRY:HKEY_CURRENT_USER\SOFTWARE\Information Builders\DeveloperStudio REGDWORD:IsRemote=0: With these lines, wfscom.xml is always copied and developers do not have the option to change this behavior.

You can add the following line if you want to force the copying of wfscom.xml regardless of what a developer has chosen in the past:

REGISTRY:HKEY_CURRENT_USER\SOFTWARE\Information Builders\DeveloperStudio REGDWORD:IsRemote=0 REGDWORD:BypassWFSUpdate=0: With these lines, wfscom.xml is always copied, even if a developer has chosen not to copy it in the past. This is a good way to force all developers to use a new version of wfscom.xml if you make a major change in the environment settings.

If you never want wfscom.xml to be copied from the network, use the following line:

REGISTRY:HKEY_CURRENT_USER\SOFTWARE\Information Builders\DeveloperStudio REGDWORD:IsRemote=0 REGDWORD:BypassWFSUpdate=1: With these lines wfscom.xml is never copied and developers do not have the option to change this.

Accessing Multiple Networked Developer Studio Installations

The shortcuts provide an easy way to run Developer Studio off the network. However, installing the shortcuts is not required. You can manually run Developer Studio off the network by executing the following file:

\\hostname\ibi\DevStudio\bin\DevStudioLaunch.exe

where:

hostname: Is the host name or IP address of the machine where Developer Studio is installed.

When this is launched, files and registry settings are created as described in Network Developer Studio Settings on Remote Machines.

If developers need to launch Developer Studio from multiple machines, you can create an HTML page containing links that point to the appropriate DevStudioLaunch.exe file of each network install.

Limiting Access to Developer Studio

There are several ways to limit access to Developer Studio.

You can restrict access to the file system of the Developer Studio machine by setting NTFS permissions on the shared directory.

or

You can specify which user IDs can run Developer Studio by editing the following file on the Developer Studio machine:
```
drive:\ibi\DevStudio81\bin\devstdpw.dat
```
By default, this file contains an asterisk (*) indicating that any user ID can run Developer Studio. If you wish to restrict which user IDs can run Developer Studio, remove the asterisk (*). Then specify each user ID that is allowed to run Developer Studio. Each user ID should be entered on a single line (one line per user ID). These are the user IDs used to log on to Windows. This file is case-sensitive. Do not enter the domain as part of your user ID.

Accessing the Developer Studio Help System

On some machines, the Developer Studio help system may not be accessible when running Developer Studio off the network. This is due to a Microsoft security change that takes place when you apply certain Windows service packs, as explained in:

http://support.microsoft.com/kb/896358

http://support.microsoft.com/kb/896054

If you cannot access the help system on certain machines, you can create registry entries on those machines that allow Windows to access the help system. One way to do this is to:

Create a text file containing:

REGEDIT4
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp]
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\ItssRestrictions]
"MaxAllowedZone"=dword:00000001

Save this file as chm.reg.
Place the chm.reg file on the machine that cannot access the help system or on a network location that is accessible to that machine.
On the machine that cannot access the help system, use Windows Explorer or My Computer to navigate to and right-click the chm.reg file.
Choose Merge.
Close Developer Studio if it is open.

The required values are added to the registry.

If you still cannot access the help system, edit the registry and try setting the MaxAllowedZone value to 4. (If you do this through the text file use dword:00000004.) The MaxAllowedZone values are discussed in:

http://support.microsoft.com/kb/896054

Creating Developer Studio Traces From a Client PC in Developer Studio Network Edition

For the network version of Developer Studio, the Developer Studio trace utility can be used to trace requests from a client PC. To accomplish this, copy the Developer Studio communications layer trace utility (install_directory\Devstudio81\bin\wfscomtrace.exe) from the network PC to any location on the client PC. Run this utility prior to performing the task that is having issues and needs to be analyzed by Information Builders. From the trace utility, enable traces and specify location of trace files.