|
|||||||
|
|||||||
|
|
|
|
|
|
|
|
 |
 |
 |
 |
|
Tools >> OpenSpirit Launcher
Why did the OpenSpirit launcher "openspirit", fail to start my UserServer? When the OpenSpirit launcher activates your User Server, it actually
spawns a separate process. In some instances (e.g., insufficient memory),
the launcher will not be able to tell why the User Server fails. You
must check the User Server log to find out why it fails. If the launcher
attempts to activate the User Server on UNIX, the log file can be found
in $OSP_HOME/logs/UserServers/
The OpenSpirit launcher depends on the Data Store Descriptors (DSD) to list the data store types and data store information. The Launcher will not show a data store type if its DSD is missing. Check the status of the Data Store Descriptor processes, the Trader, and the OAD. The Launcher uses the Trader to find the Data Store Descriptors and it depends on the OAD to start the Data Store Descriptors if they are not already active.
Currently there is not an easy way to alter a user password independent of Project Set and Session. If you see the invalid password message from the GeoFrame server, the recommended way to update the password is through the OpenSpirit launcher. If you have a session that is associated with the Project Set which includes the GeoFrame project with the questionable password, edit the session that uses the Launcher. If you don't already have that kind of a session, you can create one now. There is a "Password" button on the session edit screen which allows you to modify the project password(s).
How do I get rid of all these font error messages? If you get a lot of messages about missing fonts when you start the Launcher on a Sun machine running Solaris 2.6, it's only because the fonts are actually missing! Sun "strongly recommends" that the "SUNWi1of" font package be installed for Java 1.2 (or higher) applications, and this font package will provide the missing fonts. These fonts are contained in the SUNWi1 font package. You will find more information at the Java Developer Connection Bug Database (you must be a member to view it, but membership is free). If your UNIX console is actually a PC running Exceed, you have more work to do since Exceed (versions 6.2 and 7.0) doesn't have all the necessary fonts in its font database, either. The missing fonts include "zapfdingbats" and "symbol". To remedy this situation, according to Exceed support, you must use the UNIX font files and the 'makebdf' command to generate input files for the Exceed font compiler. Then you must compile the fonts, add them to the database, make one font size 'scalable,' and create an alias to that special font so Exceed will recognize it as such. Don't worry -- we'll walk you through it. First we must tell you that this information comes from Exceed support. We are merely relaying information, albeit with a little more detail than we were given. If you have problems with this process that you can't solve, please call Exceed support, not us! First, locate your UNIX font files (*.f3b). On Solaris they are usually in /usr/openwin/lib/X11/fonts/F3. Copy ZapfDingbats.f3b and Symbol.f3b to a directory in which you have write permission. Next, use the UNIX makebdf command to generate *.bdf files. The commands are: makebdf -v -M -x -4,5,6,7,8,9,10,11,12,14, makebdf -v -M -x -4,5,6,7,8,9,10,11,12,14, This should create lots of BDF files in the same directory. Transfer these files to your PC disk (we have had problems with Samba mounted disks - the Exceed application doesn't "see" all the BDF files thru Samba). Now go into the Exceed Configuration and start the Font configuration application. This is what it looks like: 
You want to "Compile Fonts...", which brings up the next dialog: 
Note that at the bottom of the dialog you can cause the compiler to put the fonts into several different directories. We aren't sure what's best: Some have left them in the "user" directory and some have added them to the "misc" directory. Both work. Either way, you need to change the input directory to wherever you put the BDF files. Then click "Select All" and "Compile". If you left the output as "user", it will add that directory to the font database automatically. Click "Close" and go to the "Font Database...". That looks like: 
Now select the directory you compiled the fonts into and click "Font List for Directory..." at the bottom. You'll see: 
Now we're going to make a scalable font that can be used if none of the other fonts precisely match, and create an alias so Exceed can find it. Select one of the Symbol fonts. (We selected symbol10 above.) Click "Make Scalable". Then find that new scalable font, select it, and click "Edit Logical..." You'll see: 
Type Ctrl-C to copy the logical name to the clipboard, then click "Cancel". Then click "Make Alias" on the Font List dialog and click Paste. Edit the name to change the numbers "72" to "0". You should now see: 
Click "OK" and do the same for the zapfdingbat font, creating a scalable font and an alias for it. Click "OK" and "Done" until you get out of the dialogs, then stop, restart Exceed, and try things out. Like we said before, this all comes from Exceed support, so if you have problems or questions about it, please contact them- they know a lot more about their product than we do...
Why does the Launcher look strange when I display it on a PC? If you are running the Launcher on UNIX and setting the DISPLAY to a PC running Hummingbird's Exceed, Exceed may not display it properly (particularly older versions of Exceed may have problems; the problems are minimal using Exceed 7.0.0.3). Other PC X server implementations may work fine. The Java GUI components originally caused several PC X server implementations problems- check your X server vendor for more recent versions or updates.
Why do some of my Java GUI applications crash using Exceed 7.0? Various problems have been reported when using the Hummingbird Exceed product as a PC X-Server. Here are some of the reported problems and possible workarounds. Setting the Exceed Window Manager We have had the best results setting the Exceed window manager to "Native" instead of "Default to Native" (under Tools|Configuration|Screen Definition). Running Exceed on Windows 2000 The latest version of Exceed has intermittent problems with Java GUI programs when running under Windows 2000. The frequency of these problems seems to depend on the installation, with a few installations experiencing total failure and others have no problems at all.The symptom is that when you run, for instance, the TabSelector, it crashes with a SIGSEGV or SIGBUS in some font-loading method in the JVM (look for the string "initCompositeFonts" in the stack trace). The problem has been communicated to Hummingbird, and their Technical Support Representative has confirmed that other developers are seeing the same problem. The case number is QA 27451, and their R&D department is looking at the problem to develop a patch. Hummingbird has supplied us with a patch that seems to correct this problem. The version (via Help|About Exceed) is 7.0.0.3 (instead of 7.0.0.0). Contact Hummingbird for more information. Running Java GUI Applications on Solaris via Exceed Another problem has been noted in reference to running Java GUI applications on Solaris 2.8- displaying them back to a PC thru Exceed. Usually a crash will occur in sun.awt.motif.X11Graphics.X11LockViewResources. If so, try setting the environment variable NO_J2D_DGA to 1 before starting any OpenSpirit GUI client. You can find out more about this problem at
Are you logging into your PC with the same userid? Or did your windows user id change from "john" to "John"? Or it may be a case where you can log into Windows with john, John, JOHN or any combination and it works. The problem is that you need to run OpenSpirit as the same user that you originally logged in as and registered, the solution to this is to log into your PC using a consistent casing if you plan on running OpenSpirit.
|
|
|
|||||||||||||||||||||||||||||||||||
