Installing and Starting Design Studio

The Design Studio application is provided with the CTE. The Design Studio CD-ROM also includes the Java 2 Runtime Environment (JRE).

Additional third-party components, not included on the Design Studio CD-ROM, can be used to preview the results of your transformations in PC-based simulators.

The following sections describe how to install Design Studio and the companion third-party applications and how to start Design Studio:

System Requirements

The network connection can be through a proxy server, which you specify when logging in to Design Studio.

Installing Design Studio

If auto-start is not enabled on your PC, double-click the drive icon for your CD-ROM and double-click CiscoCTEDesignStudio.exe.

You may be asked to restart your PC during the installation. After you restart your PC, the Design Studio installation wizard continues the installation.

By default, Design Studio is installed in C:\Program Files\Cisco\CTE\Design Studio\version.

For upgrade instructions, refer to the Release Notes for Cisco CTE 1400 Series and Design Studio.

Starting Design Studio

To start Design Studio, you need the following login information from the administrator who set up the CTE:

The default upload port is 9001. You might need to change the port number if your firewall redirects ports. Contact your CTE administrator if you do not know which port to use.

Step 5 If the computer on which Design Studio is installed is connected to the CTE through a proxy server, click Use Proxy and enter the host and port for HTTP and HTTPS connections.

If you cannot connect to a CTE, verify that your computer has a network connection to a running CTE. Contact your CTE administrator for help.

Changing your Password

Your password for Design Studio is set on the CTE. Contact your CTE administrator to change it.

Connecting to a Different CTE

When you log in to Design Studio, you connect to a specified CTE. You can later connect to a different CTE without leaving Design Studio. For example, you might need to switch between two CTEs used for testing.

If authentication fails, contact your CTE administrator. Either your username and password are not set in the CTE or you are not using the username and password set in the CTE.

Installing the Openwave Mobile Browser Simulator

The Openwave Mobile Browser Simulator enables you to view on your PC how your transformed web pages will appear on many wireless phones.

Step 4 After the download completes, double-click the .exe file you downloaded.

We recommend that you put a shortcut to the Openwave Simulator on your desktop for convenient access when you are using Design Studio.

Step 2 In the Openwave SDK window, choose Device Settings from the Simulator menu.

Installing the Go.Web Simulator

The Go.Web Simulator enables you to view on your PC how your transformed web pages will appear on RIM devices.

Step 5 After the download completes, double-click the .exe file you downloaded.

The last page of the installation wizard gives you the option of starting the Go.Web Simulator.

The Go.Web Simulator is ready for use with Design Studio. We recommend that you put a shortcut to the Go.Web Simulator on your desktop for convenient access when you are using Design Studio.

By default, that directory is C:\Program Files\GoAmerica\GoWebSimulator version.

Configuring Device Definitions

The CTE determines how to transcode a site for a particular device based on settings in a Device Definition File (DDF). For example, the CTE uses the specifications in a DDF to determine whether to use cHTML or WML for a device and how to handle the images it sends to a device. You can use Design Studio to tune those specifications, such as to define different display characteristics for various WAP phones.

Design Studio also enables you to import a DDF and either replace the current DDF or merge changes into it.

Table 2-1 describes the main keys and values contained in the DDF files. For more information, see the information provided in the Edit DDF window.

Table 2-1 Keys and Values in Device Definition Files

Key¹	Value²	Notes
name	A unique string of up to 127 characters.	Identifies the device in the Edit DDF window.
protocol	Must be one of the following: `chtml`, `html`, `iphone`, `palm`, `voxml`, `wml`	Determines which encoder the CTE uses to transcode data for the device. Unsupported values are ignored by the CTE.
useragent	Either the entire user agent string that the device presents in the HTTP protocol or a portion of that string represented with a regular expression.	Identifies the device to the CTE. A more general useragent key matches more devices. For example, the useragent "Phone" matches all devices that include "Phone" in their user agent string. The useragent "Phone123" matches only devices that include "Phone123" in their user agent string. Suppose that you want to define several models of "Phone" and all but one of the models ("Phone123") have the same device definition. To handle the models with the same definition, create the useragent "Phone" and include in its definition the filteragent "Phone123". The filteragent key excludes "Phone123" devices from the "Phone" definition. Create a useragent "Phone123" to define the specific settings for that device. Separate useragent values with the "\|" character.
filteragent	Either the entire user agent string that the device presents in the HTTP protocol or a portion of that string represented with a regular expression.	Identifies a particular device that is to be excluded from the devices that match a useragent key. To specify definitions for the excluded device, create a useragent key for the device, as described in the preceding example. Be sure to include "ICE" as a filteragent so that Design Studio browses correctly.
accept	Either the entire Accept tag that the device presents in the HTTP header or a portion of that string represented with a regular expression.	Enables the CTE to determine a match for unregistered devices that are not otherwise identified through the useragent or filteragent keys.
encoding	`ascii, plain, sjis, utf8`	Specifies the encoding format required by the device. Defaults to "plain"—ASCII characters 128 and above are converted into spaces; ASCII characters below 128 are passed through, except for the following: "&" is converted to & "<" is converted to < ">" is converted to >
specific	Subkeys and their values are described under "Notes."	The subkeys under the specific key vary based on device type. See the Edit DDF window for a list of specific subkeys that are available for a particular device. You can add subkeys, although the CTE may not recognize arbitrary data.
geometry	Subkeys and their values are described under "Notes."	The geometry subkeys include the following subkeys related to the display characteristics of a device: width and height, expressed in number of pixels. type (of image preferred for the device), such as "wbmp". If the application server returns a image type that the device type does not support, the CTE uses the type key to determine which format to use when transcoding images. enabled, either "yes" or "no". For WML devices only, determines whether images are transcoded for the device. colordepth, expressed as a number of colors. Use "1" to create monochrome images. localsrc, either "yes" or "no". For WML devices only, determines whether a device contains hard-coded images. max, expressed in bytes. Specifies for some protocols the maximum image size that a device can handle regardless of the image height or width.

1 You cannot edit or delete any of the keys listed in this column.

2 The value of the filteragent key is the only value that you can delete. You can edit all values.

Changing a Device Definition

You ordinarily will not need to change a DDF unless you want to make changes such as the following:

Step 2 In the left pane of the Edit DDF window, click the device type you want to change.

Step 3 In the right pane of the Edit DDF window, scroll to the value you want to change and right-click it.

Step 6 To save the DDF on your computer, choose Save DDF to Disk from the File menu.

Step 7 To publish the DDF to the CTE, choose Upload to Server from the File menu.

Step 8 To return to Design Studio, choose Return to Studio from the File menu.

Adding a Device Definition

You add a device definition to support a new device that is not included in the DDF or to uniquely define a device that is already listed in the useragent element for a device type. For example, the useragent element for WAP devices lists several types of devices. You could remove "Ericsson" from that list and create a device definition just for Ericsson.

Step 2 From the Edit menu in the Edit DDF window, choose Add New Device.

Step 3 In the right pane of the Edit DDF window, right-click the value New Device.

Step 5 In the Edit Value dialog box, type the name of the device and click OK.

Step 6 Scroll to a value you want to change, right-click it, and choose Edit Value from the shortcut menu.

Step 9 If you are defining a device that is already listed in the useragent element of another device type, select that device type in the left pane of the Edit DDF window and remove the device from the useragent element.

Step 10 To save the DDF on your computer, choose Save DDF to Disk from the File menu.

Step 11 To publish the DDF to the CTE, choose Upload to Server from the File menu.

Step 12 To return to Design Studio, choose Return to Studio from the File menu.

Table of Contents