Q: Where can I find log files generated by the common installer?
A:
Java ES Common installer logs can be found at Q: What are the most common sources of problems during Java ES installation? A: The most common sources of installation errors occur in the following order:
Q: How do I know if my product is partially installed?
A:
If the product of your choice is grayed out in the Product Selection Panel of the Java ES Installer, this indicates that your product is either currently installed on the system or is partially installed. To check if the installation is partial, use the Q: How do I bring the system to a consistent state?
A:
A partially installed product can be corrected by bringing the ProductRegistry and package database to a consistent state using the Q: I found this in Sun Java Enterprise System 2005Q4 Release Notes: "Solaris 10 SPARC and x86 including Zones Support (installation on a SPARC file system local zone is not supported)." Does it mean that I can't install JES05Q4 in a local zone on the Solaris OS for SPARC platforms, and local zones are only supported on x86 platforms? A: Zones support in Java ES is architecture agnostic: It is identical for the Solaris OS on SPARC platforms and the Solaris OS on x86 platforms. You may install Java ES 2005 Q4 on non-global zones, provided the zone is not a sparse-root non-global zone. Q: We continually struggle with integration issues between JES applications... An example is the use of an entry's LDAP cn. Since cn is multi-valued, Messenger Express/Communications Express uses the first cn value returned, but Access Manager uses the last value returned. In my opinion, both should use displayName as the preferred attribute since it is single-valued. We also face integration issues with third-party (externally developed or home-grown) applications where the JES products expect the directory to be completely theirs and don't handle error cases without seg faulting. Is there a user integration panel where JES licensees can work with Sun on JES product integration?A: Thanks for bringing this up. Starting with Java ES 2005Q4, an architectural forum has been set up to handle integration issues with JES products. Currently, the forum is handling (admittedly mundane) issues such as below:
As to your question, we are planning to address integration issues in the next Java ES release using Directory Server 6.0. We will treat the issue you mentioned as an RFE. Until further notice, please continue to use this forum for requests/RFEs. Q: I am new to the Sun Java Enterprise System. Is it better to install this software on Sun or Windows platforms, and which are the advantages and disadvantages on both platforms? A: The choice of platform depends on your particular need. The JES products themselves are cross-platform (with exceptions such as Sun Cluster) and are functionally similar. As to the installation and configuration experience, the Windows Installer currently supports simplified configuration options compared to the Solaris OS. The products on the Solaris platform can take advantage of specific features of that platform, especially for the Solaris 10 release. This directly impacts scalability, performance, and serviceability. A less generic answer can be provided after determining the product or suite that you are interested in. Q: For SunOS 5.8 and 5.9: What is the maximum number of files a directory (folder) can hold in a given file system? Is this configurable? What is the configuration I need to have 3 million files in a directory, file size=15Kb? A: In case you haven't found out already, there is no hard limit to the number of files in a single directory. Limits on the number of directories do exist, however. But performance (finding, opening, creating, and deleting files) is affected as the number of entries in the directory goes into the tens of thousands. All this changes if you decide to move to ZFS, Sun's next-generation file system, which is now available from the OpenSolaris Community. Q: I have Sun Java Enterprise System Directory Server 2005Q4 configured with idsconfig for naming authentication, i.e., providing a replacement for the NIS environment. What's the procedure to install Messaging Server 20A: Please browse the Java Enterprise System 2005Q4 Deployment Collection regarding typical messaging server deployment on an existing directory server. For example, see these examples and technical notes on docs.sun.com. |
 | |||
 | |
