Sun Microsystems 819468310 manuel d'utilisation
- Voir en ligne ou télécharger le manuel d’utilisation
- 36 pages
- 0.59 mb
Aller à la page of
Les manuels d’utilisation similaires
-
Computer Accessories
Sun Microsystems SL500
436 pages 6.54 mb -
Computer Accessories
Sun Microsystems 3.0.0
259 pages 3.99 mb -
Computer Accessories
Sun Microsystems Computer Accessories
78 pages 0.68 mb -
Computer Accessories
Sun Microsystems VIRTUALBOX 3.0.0
259 pages 4.18 mb -
Computer Accessories
Sun Microsystems X4150
12 pages 0.38 mb -
Computer Accessories
Sun Microsystems 819468310
36 pages 0.59 mb -
Computer Accessories
Sun Microsystems EC000066
64 pages 3.4 mb -
Computer Accessories
Sun Microsystems 1800
90 pages 3.07 mb
Un bon manuel d’utilisation
Les règles imposent au revendeur l'obligation de fournir à l'acheteur, avec des marchandises, le manuel d’utilisation Sun Microsystems 819468310. Le manque du manuel d’utilisation ou les informations incorrectes fournies au consommateur sont à la base d'une plainte pour non-conformité du dispositif avec le contrat. Conformément à la loi, l’inclusion du manuel d’utilisation sous une forme autre que le papier est autorisée, ce qui est souvent utilisé récemment, en incluant la forme graphique ou électronique du manuel Sun Microsystems 819468310 ou les vidéos d'instruction pour les utilisateurs. La condition est son caractère lisible et compréhensible.
Qu'est ce que le manuel d’utilisation?
Le mot vient du latin "Instructio", à savoir organiser. Ainsi, le manuel d’utilisation Sun Microsystems 819468310 décrit les étapes de la procédure. Le but du manuel d’utilisation est d’instruire, de faciliter le démarrage, l'utilisation de l'équipement ou l'exécution des actions spécifiques. Le manuel d’utilisation est une collection d'informations sur l'objet/service, une indice.
Malheureusement, peu d'utilisateurs prennent le temps de lire le manuel d’utilisation, et un bon manuel permet non seulement d’apprendre à connaître un certain nombre de fonctionnalités supplémentaires du dispositif acheté, mais aussi éviter la majorité des défaillances.
Donc, ce qui devrait contenir le manuel parfait?
Tout d'abord, le manuel d’utilisation Sun Microsystems 819468310 devrait contenir:
- informations sur les caractéristiques techniques du dispositif Sun Microsystems 819468310
- nom du fabricant et année de fabrication Sun Microsystems 819468310
- instructions d'utilisation, de réglage et d’entretien de l'équipement Sun Microsystems 819468310
- signes de sécurité et attestations confirmant la conformité avec les normes pertinentes
Pourquoi nous ne lisons pas les manuels d’utilisation?
Habituellement, cela est dû au manque de temps et de certitude quant à la fonctionnalité spécifique de l'équipement acheté. Malheureusement, la connexion et le démarrage Sun Microsystems 819468310 ne suffisent pas. Le manuel d’utilisation contient un certain nombre de lignes directrices concernant les fonctionnalités spécifiques, la sécurité, les méthodes d'entretien (même les moyens qui doivent être utilisés), les défauts possibles Sun Microsystems 819468310 et les moyens de résoudre des problèmes communs lors de l'utilisation. Enfin, le manuel contient les coordonnées du service Sun Microsystems en l'absence de l'efficacité des solutions proposées. Actuellement, les manuels d’utilisation sous la forme d'animations intéressantes et de vidéos pédagogiques qui sont meilleurs que la brochure, sont très populaires. Ce type de manuel permet à l'utilisateur de voir toute la vidéo d'instruction sans sauter les spécifications et les descriptions techniques compliquées Sun Microsystems 819468310, comme c’est le cas pour la version papier.
Pourquoi lire le manuel d’utilisation?
Tout d'abord, il contient la réponse sur la structure, les possibilités du dispositif Sun Microsystems 819468310, l'utilisation de divers accessoires et une gamme d'informations pour profiter pleinement de toutes les fonctionnalités et commodités.
Après un achat réussi de l’équipement/dispositif, prenez un moment pour vous familiariser avec toutes les parties du manuel d'utilisation Sun Microsystems 819468310. À l'heure actuelle, ils sont soigneusement préparés et traduits pour qu'ils soient non seulement compréhensibles pour les utilisateurs, mais pour qu’ils remplissent leur fonction de base de l'information et d’aide.
Table des matières du manuel d’utilisation
-
Page 1
Sun Ja va S y stem A c cess Manager 7.1 Release Notes Sun Microsystems, Inc. 4150 Network Circle Santa Clara, CA 95054 U.S.A. Part N o: 819–4683–10 March 2007[...]
-
Page 2
Copyright 2007 Sun Microsystems, Inc. 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved. Sun Microsystems, Inc. has intellectual property rights relating to technology embodied in the product that is described in this document. I n particular, and without limitation, these intellectual property rights may include one or more U.S[...]
-
Page 3
Cont ents Sun Java S ystem A ccess Manager 7.1 Release Notes .......................................................................5 Revision History .....................................................................................................................................6 A bout Sun Java System A ccess Manager 7.1 .....................[...]
-
Page 4
AMSDK I ssues .............................................................................................................................. 27 SSL Issue ........................................................................................................................................ 28 Samples Issue ..........................................[...]
-
Page 5
Sun Java S ystem Ac cess Manager 7.1 Release Not es March 2007 Part N umber 819-4683-10 The Sun J ava TM System Access M anager 7.1 Release Notes contain important information available for the Sun J ava Enterprise System ( J ava ES) release, including new Access M anager features and known issues with workarounds, if available. Read this document [...]
-
Page 6
Revision History The following table shows the A ccess Manager 7.1 Release N otes revision history. T ABLE 1 Revision History Date Description of Changes J uly 2006 Beta release. March 2007 Java Enterprise System 5 release About Sun Ja va S yst em Ac cess Manager 7.1 Sun J ava System Access M anager is part of the Sun Identity M anagement infrastru[...]
-
Page 7
devices, applications, and service-driven networks. Typical uses of the JMX technology include: consulting and changing application conguration, accumulating statistics about application behavior, notication of state changes and erroneous behaviors. Data is delivered to centralized monitoring console. A ccess Manager 7.1 uses the J ava ES Mon[...]
-
Page 8
■ N umber of successful authentications ■ N umber of failed authentications ■ N umber of successful logout operations ■ N umber of failed logout operations ■ Transaction time for each module if possible (running and waiting states) 2. Sessions ■ Size of the session table (hence maximum number of sessions) ■ N umber of active sessions [...]
-
Page 9
■ A new policy condition AuthenticateToRealmCondition added, to enforce the user is authenticated to a specic realm. ■ A new policy condition LDAPFilterCondition is added, to enforce the user matches the specied ldap lter. ■ Support for one level wild card compare to facilitate protecting the contents of the directory without protect[...]
-
Page 10
■ Support JCE Based SecureLogHelper - making it possible to use JCE (in addition to JSS) as a security provider for Secure Logging implementation Deprecation Notication and Announcement Sun J ava(TM) System Access M anager 7.1 identity management APIs and XML templates enable system administrators to create, delete, and manage identity entries[...]
-
Page 11
T ABLE 2 Hardware and Software Requirements Component Requirement Operating system (OS) ■ Solaris TM 10 on SP ARC, x86, and x64 based systems, including support for whole root local and sparse root zones. ■ Solaris 9 on SP ARC and x86 based systems. ■ Red Hat TM Enterprise Linux 3 and 4, all updates Advanced Server (32 and 64–bit versions) [...]
-
Page 12
T ABLE 2 Hardware and Software Requirements (Continued) Component Requirement Web containers Sun Java System Web Server 7.0 On supported platform/OS combinations you may elect to run the Web Server instance in a 64 bit JVM. Support platforms: Solaris 9/SP ARC, Solaris 10/SP ARC, Solaris 10/AMD64, Red Hat AS or ES 3.0/AMD64, Red H at AS or ES 4.0/AM[...]
-
Page 13
T ABLE 3 Supported Browsers (Continued) Browser Platf orm Mozilla TM 1.7.12 Solaris OS, versions 9 and 10 Windows XP Windows 2000 Red Hat Linux 3 and 4 M a cO SX Netscape TM Communicator 8.0.4 Windows XP Windows 2000 Netscape Communicator 7.1 Solaris OS, versions 9 and 10 General C ompatibility Inf ormation ■ “AMSDK intersystem incompatibility [...]
-
Page 14
Ac cess Manager Legacy Mode If you are installing A ccess Manager with any of the following products, you must select the A ccess Manager Legacy (6.x) mode: ■ Sun J ava System Portal Server ■ Sun J ava System Communications Services servers, including Messaging Server, Calendar Server, Instant M essaging, or Delegated Administrator You select t[...]
-
Page 15
“ Congur e Later” Installa tion Option If you ran the J ava ES Installer with the “Congure Later“ option, you must run the amconfig script to congure A ccess Manager after installation. To select Legacy (6.x) mode, set the following parameter in your conguration script input le ( amsamplesilent ): ... AM_REALM=disabled ... Fo[...]
-
Page 16
Known Issues and Limita tions This section describes the following known issues and workarounds, if available, at the time of the A ccess Manager 7.1 release. ■ “Installation I ssues” on page 16 ■ “Upgrade Issues” on page 16 ■ “Compatibility Issues” on page 16 ■ “Conguration Issues” on page 19 ■ “A ccess Manager Conso[...]
-
Page 17
■ “Incompatibilities exist in core authentication module for legacy mode (6305840)” on page 18 ■ “Delegated Administrator commadmin utility does not create a user (6294603)” on page 18 ■ “Delegated Administrator commadmin utility does not create an organization (6292104)” on page 18 Ac cess Manager Single Sign-On fails on Universa[...]
-
Page 18
Incompatibilities e xist in core authentication module f or legac y mode (6305840) A ccess Manager 7.1 legacy mode has the following incompatibilities in the core authentication module from A ccess Manager 6 2005Q1: ■ Organization A uthentication M odules are removed in legacy mode. ■ The presentation of the “A dministrator A uthentication Co[...]
-
Page 19
C onguration Issues ■ “Notication URL needs to be updated for A ccess Manager SDK installation without web container (6491977)” on page 19 ■ “Password Reset service reports notication errors when a password is changed (6455079)” on page 19 ■ “Platform server list and FQDN alias attribute are not updated (6309259, 6308649)?[...]
-
Page 20
Platform server list and FQDN alias a ttribute are not updated (6309259, 6308649) In a multiple server deployment, the platform server list and FQD N alias attribute are not updated if you install A ccess Manager on the second (and subsequent) servers. Workaround: A dd the Realm/DNS aliases and platform server list entries manually. For the steps, [...]
-
Page 21
Default Ac cess Manager mode is realm in the congur ation state le templat e (6280844) By default, the A ccess Manager mode (AM_REALM variable) is enabled in the conguration state le template. Workaround: To install or congure A ccess Manager in Legacy mode, reset the variable in the state le: AM_REALM = disabled Ac cess Manager C[...]
-
Page 22
Console does not r eturn the results set from Directory S er ver after reaching the resour ce limit (6239724) Install Directory Server and then A ccess Manager with the existing D IT option. Login to the A ccess Manager Console and create a group. Edit the users in the group. For example, add users with the lter uid=*999* . The resulting list bo[...]
-
Page 23
5. Click Save. SDK and Client Issues ■ “Clients do not get notications after the server restarts (6309161)” on page 23 ■ “SDK clients need to restart after service schema change (6292616)” on page 23 Clients do not get notications after the ser ver restarts (6309161) A pplications written using the client SDK ( amclientsdk.jar ) d[...]
-
Page 24
2. In Directory Server console , add the following A CI. dn:ou=1.0,ou=SunAMClientData,ou=ClientData,<ROOT_SUFFIX> changetype:modifyadd:aci aci: (target="ldap:///ou=1.0,ou=SunAMClientData,ou=ClientData,<ROOT_SUFFIX>") (targetattr = "*"(version 3.0; acl "SunAM client data anonymous access"; allow (read, searc[...]
-
Page 25
List. If you create two new organizations with the same name, the operation fails, but A ccess Manager displays the “organization already exists” message rather than the expected “attribute uniqueness violated” message. Workaround: None. I gnore the incorrect message. Access Manager is functioning correctly. Session and SSO Issues ■ “Sy[...]
-
Page 26
if you are using a third-party web container (IBM WebSphere or BEA WebLogic Server) and the optional HttpSession , you might need to limit the web container's maximum HttpSession time limit to avoid performance problems. P olic y Issues ■ “Deletion of dynamic attributes in P olicy C onguration Service causing issues in editing of polici[...]
-
Page 27
AMSDK Issues ■ “Error displayed when performing AMI dentity.modifyService (6506448)” on page 27 ■ “Group members don't show up in selected list (6459598)” on page 27 ■ “A ccess Manager Login URL Returns Message " N o such Organization found " (6430874)” on page 28 ■ “Sub-org creation not possible from A ccess Ma[...]
-
Page 28
Ac cess Manager Login URL Returns Message " No such Organiza tion found " (6430874) The problem may be due to the use of mixed-case (both uppercase and lowercase) characters in the fully qualied domain name (FQDN). Example: HostName.PRC.Example.COM Workaround : After installation, do not use the default A ccess Manager login URL. Inste[...]
-
Page 29
The amcong script fails when SSL c er ticate is expir ed. (6488777) If the A ccess Manager container is running in SSL mode, and the container SSL certicate is expired, amconfig fails and may cause classpath corruption. Workaround: If you have already run amconfig with an expired certicate, and the classpath is corrupted, rst obtain [...]
-
Page 30
JVM problems occur when running A ccess Manager on Application Ser ver (6223676) If you are running A pplication Server 8.1 on Red Hat Linux, the stack size of the threads created by the Red Hat OS for A pplication Server is 10 Mbytes, which can cause JVM resource problems when the number of A ccess Manager user sessions reaches 200. Workaround: Se[...]
-
Page 31
F ederation fails when using Artifac t prole (6324056) If you setup an identity provider (IDP) and a service provider (SP), change the communication protocol to use the browser Artifact prole, and then try to federate users between the IDP and SP , the federation fails. Workaround: None. Logout error oc curs in F ederation (6291744) In realm [...]
-
Page 32
P olic y condition date must be specied ac cording to English cust om (6390856) P olicy condition date format labels under the Chinese locale are not displayed according to Chinese customs. Labels are proposing a date format like English date format. Related elds also accept English date format values. Workaround: For each eld, follow the [...]
-
Page 33
Documentation Issues ■ “Document the roles and ltered roles support for LD APv3 plug-in (6365196)” on page 33 ■ “Document unused properties in the AMConfig.properties le (6344530)” on page 33 ■ “Document how to enable XML encryption (6275563)” on page 33 Document the roles and lter ed roles suppor t for LD APv3 plug-in (6[...]
-
Page 34
5. If you are using a JDK version earlier than JD K 1.5, edit the jdk_root /jre/lib/security/java.security le and add Bouncy C astle as one of the providers. For example: security.provider.6=org.bouncycastle.jce.provider.BouncyCastleProvider 6. Set the following property in the AMConfig.properties le to true: com.sun.identity.jss.donotInstall[...]
-
Page 35
How t o Repor t Problems and Pr ovide F eedback If you have problems with A ccess Manager or Sun J ava Enterprise System, contact Sun customer support using one of the following mechanisms: ■ Sun Support Resources (SunSolve) services at http://sunsolve.sun.com/ . This site has links to the Knowledge Base, Online Support Center, and ProductTracker[...]
-
Page 36
Ac cessibility F eatures for P eople W ith Disabilities To obtain accessibility features that have been released since the publishing of this media, consult Section 508 product assessments available from Sun upon request to determine which versions are best suited for deploying accessible solutions. Updated versions of applications can be found at [...]