Procedure: How to Define a WebFOCUS Environment

1. 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.

2. Start Developer Studio from the Start menu by selecting Programs, Information
Builders, WebFOCUS 80 Developer Studio, and WebFOCUS Developer Studio.

3. If prompted to log on, log on to the WebFOCUS Reporting Server.

4. 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.

5. Select localhost and click Properties to edit the default settings.

The WebFOCUS Environment Properties window opens, as shown in the following image.
6. 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.

7. 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.

8. 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.

9. 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.

10. Click OK when you have set up the default environment.

If you wish to define additional WebFOCUS environments, click Add on the Environments
List.

11. Click OK on the Environments List when you have defined all your environments.

The Developer Studio Explorer opens.

12. If prompted to log on, log on to the WebFOCUS Reporting Server.

13. Ensure that the Developer Studio Explorer functions properly and that your WebFOCUS
environments are accessible.

14. 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.
Top of page
Setting Up Access to the Network Installation

How to:
 Set Up Network Shares
 Copy the WebFOCUS Environments File (wfscom.xml)
 Configure the Network Settings

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

1. How to Set Up Network Shares.

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

3. How to Configure the Network Settings.

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 DevStudio80 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:

1. Open Windows Explorer or My Computer on the Developer Studio machine.

2. Navigate to and right-click the ibi directory.

 3. Select Properties.

4. Click the Sharing tab, as shown in the following image.

5. Select Share this folder.

6. 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.

7. 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.

8. Click OK.
Top of page
Procedure: How to Copy the WebFOCUS Environments File (wfscom.xml)
Copy the WebFOCUS environment settings (wfscom.xml) into the DevStudio80\bin directory so they
are available to remote Developer Studio users.

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

drive:\Documents and Settings\userID\Application Data\

Information Builders\wfscom.xml

where:

userID
Is the user ID logged on to Windows.

For Windows 7:

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\DevStudio80\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 DevStudio80\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\DevStudio80\bin\runfocshell.dat

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

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

2. Find the following line:

REGSTRING:LastUsedServer=Name to be supplied by Administrator

3. 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.

4. Ensure that the correct host name, share name, and UNC directory path appears for
accessing the DevStudio80 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:

5. WFSCOM:\\hostname\Ibi\DevStudio80\bin\wfscom.xml

SHLPATH:\\hostname\Ibi\DevStudio80\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.

6. 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.
Top of page
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:

1. Open Windows Explorer or My Computer on the remote machine.

2. 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.

3. Navigate the shared directories to:

\\hostname\ibi\DevStudio80\Utilities\Local_setup

4. Run the setup.exe application to install Developer Studio shortcuts.

The installation wizard launches and a Welcome window appears.

5. Click Next at the Welcome window.

You are prompted to create shortcuts.

6. Select which shortcuts to create and click Next.

Shortcuts are created.

7. 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.
Top of page
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.

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 for Windows XP:

drive:\Documents and Settings\userID\Application Data\

Information Builders\wfscom.xml

where:

userID
Is the user ID logged on to Windows.

For Windows 7:

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\DevStudio80\bin\runfocshell.dat file are
loaded.
Top of page
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\DevStudio80\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.
Top of page
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.
Top of page
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\DevStudio80\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.
Top of page
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:

1. Create a text file containing:

 2. REGEDIT4

3. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp]

4. [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\ItssRestrictions]

"MaxAllowedZone"=dword:00000001

5. Save this file as chm.reg.

6. 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.

7. 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.

8. Choose Merge.

9. 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: