This action might not be possible to undo. Are you sure you want to continue?
Please read this information after you install, but before you use Jaguar. Note: The latest version of the Jaguar CTS Release Notes for Windows NT is included in the file Readme.htm, in the Jaguar installation directory on your EAServer CD. Copy Readme.htm and template.css from the CD to the \html\docs directory under your Jaguar installation to ensure you have to most current release notes available. The information in this chapter is organized into these categories: o o o o o o o o o o o o o o o o o o System Requirements Jaguar Client Runtime Installation Configuring Open Client and ODBC Jaguar Manager Issues Web Browser Issues Running jagdemo.db and the Sample Application Jaguar/PowerJ Compatibility Issues Jaguar/PowerSite Compatibility Issues Jaguar/PowerBuilder Compatibility Issues SSL Security Issues CORBA ActiveX Clients C Component Coding Issues Client Development Issues Troubleshooting the Server Troubleshooting Java Client Applets and Applications Renamed Open Client and Open Server Libraries New Features in this Release Closed and System Problem Reports
System Requirements o o Operating systems: Windows NT
Warning! Your display and video card must support 256 or more colors in order
you will need an ActiveX enabled IDE such as PowerBuilder.0.1 or later.exe must support the /tlb command-line option. or Microsoft Visual Basic. o Server development tools Java server components must be compiled with JDK 1.1 Jaguar includes an installation of both JDK 1. You can run Adaptive Server Anywhere on the same machine as Jaguar. and driver manager DLL.0.1. import libraries. The JDK 1.1. You must have Adaptive Server Anywhere running on your system to run the sample Jaguar applications.com).x interpreter.0. You need a C or C++ development environment to create Jaguar "C" components. Jaguar provides runtime classes that are compatible with both JDK versions.dll) must be in your system PATH setting.x or with a compiler that is compatible with the JDK 1. The ODBC driver manager DLL (odbc32. you need Microsoft's ODBC header files.1.microsoft. .0. you need an IDE that can create ActiveX/OLE automation DLLs (we recommend PowerBuilder 6. To create C++ clients. o Java Developer's Kit (JDK) versions 1. Jaguar does not require a database server to run.0. you need a C++ development environment such as Powersoft Power++ or Microsoft Visual C++. Powersoft Power++ 2. You may download PowerJ? from the Powersoft Web site (www. or MS Visua l Basic). o ODBC developer files To use ODBC calls in components.2 and 1. o Database software: Jaguar comes bundled with Adaptive Server Anywhere. These are included with Microsoft Visual C++. you can also download them from Microsoft's Web site (http://www.0 or later.sybase.1.x.2 or 1. The file midl. MS Visual C++. To create ActiveX components on NT. Power++. Adaptive Server Anywhere is provided for the purpose of running the sample application. JDK 1.x version is located in the EAServer shared directory is required to run the Jaguar server.x. o Client development tools JDK release 1.2 and JDK 1.2 is required to compile and run client applets that must run in a JDK1.com).to run Jaguar Manager. PowerJ is a Java rapid application development environment.1. To use ActiveX clients.2-compatible Web browser. See "Using Connection Management" in the Jaguar CTS Programmer's Guide for information on connecting Jaguar components to other data sources.
you may have selected a different directory for shared components when installing Enterprise Application Studio. copy the installer file. The client runtime also includes standalone versions of the Jaguar Manager and Security Manager tools. Configuring Open Client and ODBC Jaguar and PowerDynamo do not require Open Client and ODBC to run. If you run Jaguar CTS or PowerDynamo as an NT Service. However. Open Client is installed in this directory: C:\Program Files\SYBASE\Shared\Open Client However. You can delete the copy of JagClient. you must set these variables in the System Environment Variables list: . Setting the PATH and SYBASE Environment Variables Set these environment variables as described below. you must configure the environment for Open Client and ODBC for use with Jaguar if you will use either of the following features: o o Run PowerDynamo or other Jaguar MASP client applications on the Jaguar server Define ODBC connection caches that use the Sybase/Intersolv Sybase ODBC driver that is included with Enterprise Application Studio.exe. You must perform them yourself after completing the installation. JagClient. The Enterprise Application Studio and Enterprise Application Server installation programs do not perform these steps. By default. To install the client runtime. using the System dialog in Windows NT Control Panel.exe after the installation is complete.Jaguar Client Runtime Installation The Java and C++ client runtime files for Jaguar CTS can be installed independently of Jaguar server on client workstations. Do not perform these steps if you have Sybase Adaptive Server Enterprise installed on the same machine as Enterprise Application Studio or Enterprise Application Server. from the client subdirectory of your Jaguar server installation into a temporary director y on the client workstation. Configuring Open Client To configure Open Client you must modify the PATH and SYBASE environment variables to include the location of the Open Client software. The environment settings required for this beta may conflict with those for Adaptive Server Enterprise. then define network addresses in the Open Client sql. then run it.ini file.
Changes to system environment variables take effect when you restart Windows NT.INI file user is a valid user name for the Jaguar or database server password is the password that accompanies the user name If isql displays a command prompt (and not an error message).INI if it does not already exist.1 Set the SYBASE environment variable to the full path of the Enterprise Application Studio or Enterprise Application Server shared Open Client directory. host. do not restart your computer now.INI file The SQL. so if you plan to configure ODBC as well.INI file in a text editor and add an entry in this format: [server_name] master=TCP. Open the SQL. Editing the SQL. For example: C:\Program Files\SYBASE\Shared\Open Client 2 Add the Open Client DLL subdirectory to the PATH environment variable.INI file in the Open Client INI subdirectory defines server names and addresses. Configuring ODBC Enterprise Application Studio includes ODBC drivers for ODBC version 3. tds_port query=TCP. and the underscore character host is the server machine's host name or IP address tds_port is the Jaguar or database server's TDS listener port number Testing Open Client You can run the Open Client isql tool to verify the configuration: %SYBASE%\BIN\ISQL -S server_name -U user -P password where: o o o server_name is the server name that you defined in the SQL. ODBC configuration may also require a restart. digits. . tds_port where o o o server_name is a logical name for the server. 1 2 Create the file %SYBASE5/INI/SQL.5. composed of letters. You must add an entry for each Jaguar or database server that you intend to connect to. host. the connection is successful.
The JRE interpreter will hang if the display supports less than 256 colors. run the program mdac_min. Jaguar Manager may crash with a memory error immediately after starting. Running Jaguar Manager On Hewlett Packard Windows NT Server machines. Data sources used by Jaguar CTS or PowerDynamo must be system data sources. all of which are included with Microsoft Data Access Components (MDAC). ODBC installation instructions ODBC installation instructions are described in the EAServer Installation Guide. Jaguar Manager runs in the Java Runtime Environment (JRE) interpreter. you can run the Windows NT ODBC Administrator to define data sources that use the PowerBuilder/Sybase 32-bit driver installed with Enterprise Application Server. The MDAC installation requires you to reboot your computer. insert the following line: cd "%JRE_LATEST%\bin" In the "%JRE_LATEST%\bin\jre" line. Afterwards. To install MDAC.0. including: o o o System Display Issues Scroll Bar Does not Always Display Running Jaguar Manager System Display Issues Your display and video card must support 256 or more colors in order to run Jaguar Manager. Find the line that begins: "%JRE_LATEST%\bin\jre" Above this line.These drivers require a new version of the ODBC Driver Manager and related utilities. replace the text: "%JRE_LATEST%\bin\jre" . edit the file html/classes/jagmanager. To work around this problem. The ODBC installation instructions that appear in the Jaguar CTS Programmer s Gui de are incorrect.bat in the Jaguar installation directory. Jaguar Manager Issues This section includes late-breaking information about Jaguar Manager that is not in Jaguar CTS Getting Started. not user data sources.exe located in the support subdirectory of your Enterprise Application Server CD. version 2.
add the full path of the copied file to the CLASSPATH setting.JaguarProvider Scroll Bar Does not Always Display The scroll bar in the left pane of the Sybase Central window does not always display when it should. you may need to create a batch file and shortcut to start netscape. Before starting the browser.0. which offers enhanced integration with Jaguar CTS 3.MainController \ com. If you expand a folder and cause the tree view to expand past the bottom of the window. Instructions for running the Sybase Virtual University sample application can be found in the sample's README file.x to run Jaguar client applets. Double-click on the jagdemo shortcut to start the sample database.controller.%CLASSPATH% \ sybase.jar. This issue does not occur with earlier versions of Netscape Navigator. If it does not. launch the README shortcut in the Jaguar CTS program window to view the file. highlight any icon in the tree view and and the scroll bar will display.0 or later.0. In jagmanager. your Web server must include the Jaguar Java classes in the class tree specified by the applet's codebase parameter.with jre. To achieve better applet performance. Web Browser Issues To run Java applets that connect to a Jaguar server.scp.bat it must be one line): cd "%JRE_LATEST%\bin" jre -DJAGUAR="%JAGUAR%" -cp \ %JRE_LATEST%\lib\rt. Jaguar/PowerJ Compatibility Issues Enterprise Application Studio includes PowerJ 3.db database must be running before you can run the Sybase Virtual University (SVU) sample. then use your Web browser to connect to the Jaguar server as described in the README. Running jagdemo.jaguar. you must download all classes.0. If you run Netscape 4.management.exe with CLASSPATH unset. Note: When you are running Jaguar client applets in Netscape 4. you should have two lines that look like this.db and the Sample Application The Adaptive Server Anywhere jagdemo. Make sure both the jagdemo database and the Jaguar server are running.JaguarProvider. If you get a message that says "jagdemo. Otherwise you may get SecurityException errors.log from the Sample folder within your Jaguar installation directory then start jagdemo again. Make sure that CLASSPATH is not set before you start Netscape 4.zip from %JAGUAR%\html\classes to the local browser machine. (The second line is broken here with backslashes for clarity. the scroll bar should display.scf. you can copy the file jaguar.sybase.log is an older version. When you are done. ." delete the file jagdemo.0 on your Jaguar server machine.
5\ Shared Debugging Jaguar Components with PowerJ In Jaguar version 3. Display the Debug tab. Jaguar/PowerSite Compatibility Issues This release of Enterprise Application Studio includes PowerSite 2.Deploying Java Components from PowerJ PowerJ 3. Jaguar disables this feature automatically when it installs the JDK.dll However. Start Jaguar Manager. Jaguar/PowerBuilder Compatibility Issues . Restart the debug server. To enable remote debugging: 1 2 3 4 5 Start the debug server. the file is installed in C:\Program Files\Sybase\Shared\Sun\JDK116\bin\symcjit. delete or rename the symcjit.0. You no longer need to log into Jaguar Manager to install components that are developed with PowerJ. You can confirm the path to the Sybase shared components folder by viewing the following Registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Sybase\PowerStudio\1.htm) for important information on connecting to Jaguar from PowerSite. you must enable remote Java debugging explicitly before you can debug Jaguar components remotely with PowerJ. you must disable JIT to run Jaguar server.0 allows you to create projects that will install Jaguar components from within PowerJ.6 installation.0.dll file in the Sun\JDK116\bin subdirectory in your Sybase shared components folder. To disable the JIT compiler. if you install PowerJ it may be reenabled. See the PowerJ 3. Disabling the JIT Compiler Jaguar and PowerJ share a JDK version 1.0 documentation for more information on this feature. Highlight the icon for your server. then choose File | Properties. Jaguar is incompatible with the Just-in-Time (JIT) Java compiler feature. However. By default. which has been enhanced to allow management of Jaguar components. then select the Enable Java Debugging checkbox.1. See the PowerSite release notes (readme20. you may have specified a different folder for Sybase shared components when you first ran the PowerStudio installer. PowerJ interacts directly with the Jaguar repository to install and configure Java components.
Remote debugging of Jaguar components in PowerBuilder requires that you install a helper component in your Jaguar server. you must upgrade to the domestic version of CipherSuites. Browser Hangs If RSA Is Not Enabled You must log in to the communicator DB before connecting to the Jaguar server. contact Sybase Technical Support and request the CD-ROM that contains the upgrd128 utility.04 or 4. and are not logged in to the browser's certificate DB. If you intend to use SS L security domestically (United States or Canada). To solve this problem: 1 From your browser. If testing in an environment with multiple Jaguar servers. Restart Navigator. Since all Jaguar Servers use the same distinguished name for the test CA. your browser may hang. To upgrade.0. If you try to connect to a Jaguar listener that requires client authentication f rom Netscape Navigator version 4.This release of Enterprise Application Studio includes PowerBuilder 7. 2 3 Supporting Multiple CA Certificates Some browsers may not support more than one CA certificate with the same distinguished name (X509 v3 extension authorityKeyID may not be supported). Upgrading From International To Domestic CipherSuites Jaguar ships with the international set of CipherSuites. use only one Jaguar Server as the signing test CA. other Jaguar Servers can generate certificate requests to be signed by this test CA. select Security | Cryptographic Modules | Netscape Internal PKCS #11 Module | View/Edit | Communicator Certificate DB | Config Enable the check box titled "RSA" and click OK. C Component Coding Issues The Jaguar CTS Programmer's Guide describes a process for attaching to the . and want to use stronger domestic encryption. SSL Security Issues This section lists late-breaking information regarding SSL security and Jaguar.05. See the PowerBuilder README file for more information. which allows you to deploy PowerBuilder objects to Jaguar to be run as Jaguar components. OK and OK.
You can issue this command to see the options that your midl.When called on any numeric datatype column in a ResultSet returned by a Jaguar method. you may get dialogs that refe to a non-existent jagsrv.pdb file (click OK to skip) and to Jaguar produ Client Development Issues o of the Win32 SDK.exe version supports: midl /? Many tools from other vendors include a redistribution of the Win32 SDK. You can ignore these messages and skip through the dialogs. o When the server initially comes up in the debugger.com/developer/sdk/sdktools. midl.cc").exe. The file midl.server with a debugger and setting breakpoints in order to debug components. When you start the server in the debugger. Troubleshooting the Server This section offers troubleshooting tips if you are having problems with your Jaguar installation. you can serialize and deserialize component proxy references with the same restrictions as for Java clients. it may stop at autogenerated breakpoints (for example "_DbgBreakPoint@0"). This exception should be a SQLWarning.microsoft.htm o o For C++ clients.2 or higher contain the correct version of midl.exe is distributed by Microsoft as part of their development tools and as part Known problem in Java Stubs . including: o o o o o o Logging Errors Server Startup Problems Problems Connecting to the Server Running the Debuggable Version of the Server Problems Importing Java Components Problems Invoking Java Components .exe from the Microsoft Developer Network Web site: http://msdn. Note the following: o r ct source files (for example "Please enter the path for SRVHANDLERS. Power++ 2. You can also download midl. You must continue execution before the server can accept connections.0 or greater and Visual C++ 4.exe must support the /tlb command-line option. g etInt throws a SQLException due to loss of precision.
under the Debug/Trace tab.log in the Jaguar bin directory. (The log file name is specified in the Server Properties dialog. If you don't have the file.) The server may exit immediately without logging errors if there are errors in the Jaguar configuration. The location of the JDK 1.com).1 Java interpreter (%JDK_LATEST%\bin\java. See "Running the Debuggable Version of the Server" on page 62 for more information. Make sure your JAGUAR variable is correct (error message is "unable to find localization files" or "unable to find interfaces file"). in this case. After you start the server. This file is usually located in the system subdirectory of the Windows NT installation directory. you can download the latest ODBC version from the Microsoft Web site (http://www. For information on listeners refer to Jaguar CTS Getti ng Started for NT.o Problems Invoking C or C++ Components Logging Errors Errors that occur during server execution are recorded in the server log file. Through Jaguar Manager you can view and modify listener entries. If you cannot determine the cause of the error by looking at the log or the server console window. . s Jaguar Manager and connect to the server (initially. Directories in the system-level PATH variable are searched before those in the user-level PATH variable. the server prints error messages to the shell window (console) where it was started.dll. Make sure your PATH environment variable includes the following (%JAGUAR% represents the Jaguar installation directory): %JAGUAR%\dll The location of your system's ODBC driver DLL. You can change the log file name for each new server that you create. o Note: The Jaguar setup program adds directories to the user-level PATH variable. odbc32.microsoft. check for the following errors: o 't o o o o Make sure you don't already have a server running (error message is "can start network listener"). "localhost" is the machine name). T he preconfigured Jaguar server writes messages to srv. Server Startup Problems If you are having trouble starting your server. run the debug version of the server. o tart Verify the listener entry for your server.exe).
Problems Importing Java Components .o o Make sure the server you are running exists in Jaguar Manager's Servers folder. o ons If you have trouble connecting with Java clients. Initially. For information on changing the machine name refer to "Preconfigured Listeners" in Jaguar CTS Getting Started for NT. Sybase recommends that you modify this initial setting to the actual machine name or IP address after installation. and clients must use "localhost" to connect. o ather than the DNS host name. Problems Connecting to the Server If you have trouble connecting to a Jaguar server: o than ng on the same machine. Note: The debuggable version of the server aborts with a failed assertion when a zero-length value is received for an INOUT string parameter. o Check for errors in the server's log file. change the server listeners to use the actual network name rather than "localhost". You must use "localhost" to connect to the server. Make sure you are connecting to the correct machine name and port number when you run Jaguar Manager. See the Jaguar CTS Programmer's Guide for more information on debugging your components. rather the actual network host address.bat You can also run a debuggable server instance using the Jaguar Server (dev) icon in the Jaguar CTS program folder. Some clients may have trouble resolving DNS host names to IP addresses. This is a known issue. Jaguar uses the default setting of "localhost" as the machine name. You can run it from the command line or by double-clicking on this file in NT Explorer: %JAGUAR%\devbin\serverstart_dev. In this case. In ord er to connect from other machines. change the server's listeners to use the host IP address r If your server's listeners use "localhost" for the machine name. See "Troubleshooting Java Client Applets and Applications" on page 64 for details on solving this problem. check for Java excepti related to Java class loading. you can only connect from clients runni Running the Debuggable Version of the Server The following batch file runs the debuggable version of the server.
<object>Holder class. "Creating Java Components" in the Jaguar CTS Programmer's Guide. Verify that the location of the JDK 1. add the paths to these classes to the CLASSPATH environment variable. The server searches dire Troubleshooting Java Client Applets and Applications This section offers tips for: o Applet Troubleshooting . o r Make sure that the component's class file is properly specified in Jagua Manager. If necessary. make sure that the C++ class name for the component is specified correctly.jaguar. Doing so can crash the server. o Do not assign new objects to the object references passed to a Java component method. You must log out of Security Manager and then log in to Jaguar Manager to use the importer. For C++ components. (inout and out parameters are passed as an instance of a com.) For more information on debugging Java components. Problems Invoking Java Components If you have trouble invoking a Java component: o o Check the server's log file to see what errors were recorded there. see "Chapter 6. Any other classes required by the component (for example JDBC driver classes) must also be in CLASSPATH. the server searches the directories specified in the PATH environment variable. The location of the component's class file must be specified in CLASSPATH (as set in the shell where the server is started).1 bin subdirectory is in your PATH setting.The Java importer does not work if you are logged into Security Manager.sybase.util. Use the holder object's value field to pass output values for the parameter. then restart the server. Problems Invoking C or C++ Components If you have trouble invoking a C or C++ component: o o o ctories in the order shown below: o o The directory specified as the server's "Library Directory:" setting If the library is still not found. Check the server's log file to see what errors were recorded there. Make sure that your DLL name is correctly specified in Jaguar Manager and that it exists in the server's search path.
such as the generated stub class.dll libcs.zip (or a copy of this file). make sure the necessary classes are locally available and specified in the CLASSPATH environment variable. Make sure that: o r u use JDK 1.o o Application Troubleshooting General Troubleshooting Applet Troubleshooting If you have trouble connecting to the Jaguar server with a Java applet.dll libjcs. Many current browsers require that yo CLASSPATH must also include the locations of any additional classes that are required by your application. To include the Jaguar client classes. or %JAGUAR%\html\classes (for applications that are run on the Server host machine).0.2-compatible stubs. "Creating CORBA-compatible Java Clients" in the Jaguar CTS Programmer's Guide lists the classes required for applet deployment. check your Web browser's Java console for error messages.dll libjcomn. you must change the makefile to compile with the Jaguar libraries. See "Troubleshooting the Server" on page 60 for more information. You are using a browser that is compliant with the target JDK version fo the generated Jaguar stub classes. If you use the old names in existing makefiles.dll . o The required Jaguar classes are accessible under the applet's code base. Application Troubleshooting To run Java applications. Renamed Open Client and Open Server Libraries The Open Client and Open Server libraries that are installed with Jaguar have been renamed to avoid conflicts with other Open Client or Open Server installations on the same machine. CLASSPATH must include one of the following: o o %JAGUAR%\html\classes\jaguar. General Troubleshooting You may also encounter problems on the client that are caused by component-loading problems on the server. The following table lists the new names: Renamed Open Client and Open Server libraries Old Name New Name --------------------------libcomn.
libct.dll libintl. Your connections should now succeed. redefine the DSN as a "System DSN".0.dll libjsrv. If you set the transaction model to Microsoft DTC in version 1.0 for a list of new features in this release. if you create a ODBC connection cache for a data source which is declared as a "User DSN" in the Windows NT ODBC Administrator. o o .dll libjintl.dll libjtml. Visual Basic ActiveX components in different DLLs cause clients to freeze after about 10 method invocations. then the help page displays with unreadable text in the right frame of the help window.0 and migrate your Jaguar server to version 3.dll libtcl.dll libsrv.0. If you run into this situation. Trying to Ping the connection cache will also fail. o In Jaguar Manager. The following are known issues: o he o If you try to run the Sybase Virtual University sample without running t SVU sample database. Please note the DSN for the EAS Demo DB is created as a "User DSN". you may not be able to use this connection cache. o If you did not use the uninstall program to remove Jaguar 2. In Jaguar Manager. the SVU sample might fail because duplicate connection cache information (two ODBC registry entries) resides in the registry. if you click on node "Role Membership" and select Help | Jaguar Manager. the Jaguar server may abend.0 before installing Jaguar 3.dll libjtcl. see the files in the html/docs/ProblemReports subdirectory of your Jaguar installation.dll libjct.0 or 2. Closed and System Problem Reports For lists of problem reports that were fixed in this release and a list of known current problems.dll libtml. the transaction model is changed to shared connection and method parameter descriptions are not migrated.dll New Features in this Release See What's New in Jaguar CTS 3.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.