|
|
A remote upgrade system has been implemented. Upon startup (provided you have the appropriate access level), Internet Script Editor notifies you if a newer version of the software is available for download. If you decide to upgrade, Internet Script Editor downloads the new version of itself and applies the upgrade.
Internet Script Editor is installed by connecting to the web server on the distributor and clicking on a link that downloads the Internet Script Editor as a self-extracting archive.
The program group setup creates:
Step 2 Enter XXX\install\iscripteditor.htm where XXX is the address of the host machine where the iscripted.htm executable is located (normally the ICM server).
Step 3 Click Enter.
Step 4 Enter your User Name and Password, then click OK.
Step 5 Click Download Internet Script Editor.
Step 6 Navigate to the directory where you want iscripteditor.exe to be downloaded to.
Step 7 Click Save to begin the download.
Step 8 When the download is complete, close the browser.
Step 9 Navigate to iscripteditor.exe and execute the file.
Step 10 When the InstallShield Wizard for Internet Script Editor starts, click Next to continue.
Step 11 Select the default Destination Folder by clicking Next; or use Browse to navigate to the desired Destination Folder, and then click Next.
Step 12 When the InstallShield Wizard indicates the installation is complete, click Finish.
A shortcut for Internet Script Editor (IScriptEditor) appears on the desktop.
Internet Script Editor gets services from various processes on the ICM software distributor. These services are exposed through the web server (IIS) so that Internet Script Editor can access them using HTTP.
To start Internet Script Editor, you first provide/confirm the connection information (the server address, port, and ICM software instance), then log in to the web server (IIS) using your user name and password.
Step 2 Click Connection.
Step 3 Enter the correct Address, Port, Side (Database), and ICM Instance information. Click OK.
Step 4 Enter your User name and Password. Click OK.
Step 5 Upgrade Internet Script Editor as necessary (see Upgrades).
The Internet Script Editor upgrade process is invoked each time you log on and start the Internet Script Editor. Once you are authenticated, Internet Script Editor determines if a software upgrade is available. If an upgrade is available, you have the option to automatically download and install the upgrade.
Some upgrades will be optional, especially those that fix minor GUI bugs. However, a protocol change, or a database schema change will force a mandatory upgrade. If you refuses a mandatory upgrade, Internet Script Editor will not allow you to connect and do any work.
When you accept a software upgrade, Internet Script Editor starts a separate process to download and apply the upgrade. The upgrade process sends a message (WM_CLOSE) to all instances of the Internet Script Editor and does not proceed until all instances are closed. The upgrade process then downloads a new self-extracting archive from the web server and executes it.
You are not able to do any work during the upgrade.
On startup, Internet Script Editor needs to load the ICM configuration database into memory. Internet Script Editor communications with the server have been minimized. A single message is sent to the server, asking for the entire ICM configuration. The server responds by sending back the entire configuration database.
In addition to loading the configuration database, the Internet Script Editor needs to load scripts and perform other kinds of database reads. This is accomplished using a service that allows the Internet Script Editor to fetch objects from the database by sending a request to the web server. Request messages are wrapped in an HTTP package (following the standard request-response pattern used by the ICM software) before sending them.
Internet Script Editor and ICM Script Editor GUI are essentially the same. The menus, toolbars, palette, and work space are utilized in the same manner in both applications. The differences between the two occur primarily in the method by which each application communicates with the ICM software.
The Script Editor Log In dialog has a Connection button that requires ICM server and Proxy server information.
The Status Bar contains three new elements:
If you are associated with a single ICM customer, Script Explorer only displays scripts for that customer. The same applies for business entities.
The Select Customer is hidden from you if you are associated with a single ICM customer. The Select Customer option is only available if you are associated with multiple customers (administrators, etc.).
The Script Locks screen in Internet Script Editor only reveals locks in the same customer and/or business entity of the logged on user. As a result, you are only permitted to break locks for scripts within your customer or business entity.
Internet Script Editor modifies the database just as the ICM Script Editor does. Typical modifications include saving scripts, acquiring script locks, and deleting scripts.
Internet Script Editor sends messages describing the changes to a process on the ICM router machine called dbagent. Internet Script Editor sends a multi-part message to the web server describing the changes to the database. The web server then forwards these messages to dbagent.
The client needs to express request this service using an HTTP request. HTTP provides a mechanism called a multi-part POST. This mechanism allows Internet Script Editor to send a sequence of messages as parts of a single operation.
As with the ICM Script Editor, the Internet Script Editor maintains an in-memory copy of the configuration database. Whenever the configuration database changes, Internet Script Editor modifies its in-memory copy to keep it synchronized.
The ICM Script Editor maintains a constant connection to the updateaw process on the ICM distributor. It subscribes to a feed of config change messages. Whenever the physical database changes, updateaw sends Script Editor messages that describe these changes.
To emulate this behavior in the web server world, Internet Script Editor polls the server at regular intervals for changes to the config database. The server sends all the database changes needed to synchronize Script Editor with the physical database.
Internet Script Editor forwards tracing and event information to the updateaw process for troubleshooting purposes (see Troubleshooting). This information is stored in EMS log files. Updateaw is responsible for logging these messages in a persistent way. This uses a simple request-response protocol. Database changes are simply wrapped in an HTTP POST message. The server then forwards the information to updateaw.
Today, the ICM software provides a very primitive mechanism for controlling what features are available to users of Script Editor and Web View.
For Script Editor, the concept of a "limited AW" is used. A limited AW excludes certain items from the Script Editor palette.
For Web View, Configure ICM lets you control which users can QuickEdit various script nodes.
For Internet Script Editor, you have more granular control over what users can do. An administrative tool ("Feature Control") has been devised to control what Script Editing features available to the user.
ICM administrators can to define what is called a class of service. A class of service is a collection of features and privileges. The administrator can associate a class of service with an ICM customer.
User privileges are controlled on the server. These options cannot be configured in the client setup.
Administrators control the behavior of Internet Script Editor using the programs in Table 8-1.
| Program name | Executable name | Functionality |
|---|---|---|
Microsoft Internet Service Manager | Inetmgr.exe | Start/stop IIS. Check status of IIS. Control access to virtual directories. |
Key Manager (Microsoft) | Keyring.exe | Install encryption keys for IIS. |
Configure ICM | Awconfig.exe | Add/remove users.Control user privileges with respect to ICM objects. |
User Manager for Domains (Microsoft) | Usrmgr.exe | Change user passwords. |
Internet Script Editor writes to EMS logs and purges old logs on startup just as ICM Script Editor does. These logs are located in:
C:\winnt\Prifiles\Administrator\Application Data\Cisco Systems\iScriptEditor\logfiles
These files are accessed using the Dumplog utility.
Internet Script Editor is built without symbol tables to keep it small. This makes Dr. Watson output more difficult to debug.
Since the client runs on hardware completely outside our control, no support for remote control debugging is provided.
IIS logs its activity to system event log or to an ODBC data source.
ISAPI DLL generates trace output on the distributor. System administrators can use the Dumplog utility to display the contents of the logs.
Posted: Tue Jun 25 08:41:37 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.