Login or Register to Ask a Question and Join Our Community


Solaris

Sun Java Directory Server icon

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems Solaris Sun Java Directory Server icon
# 1  
Old 02-12-2013
Sun Java Directory Server icon
This probably is immensely trivial, but as the bank robber in the movie Dirty Harry says, "I gots to know."

In Sun Java Directory Server's (v 5.2) list of users and groups, there are several scores of usernames that have an icon that looks like a blue circle. Below that are scores of usernames with icons that look like human torsos. The torso icon is the one you see in documentation. The blue circle ones do not show up when you search for that username. What's the difference between the two?

---------- Post updated 02-12-13 at 02:41 PM ---------- Previous update was 02-11-13 at 03:32 PM ----------

For anyone interested, Sun Java Directory Server apparently gives a different icon to accounts that were created outside of JDS. Accounts created in JDS have two more entries than in the ones either imported into LDAP or created with other LDAP tools or migrated from NIS+. JDS won't search those accounts either.
Login or Register to Ask a Question

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Sun java app server

quick question: where can I download sun java application server that will run in java6? or both? I need to install sun java app server and java6. thanks ---------- Post updated at 09:20 AM ---------- Previous update was at 09:12 AM ---------- OS: solaris10 (0 Replies)
Discussion started by: lhareigh890
0 Replies

2. UNIX and Linux Applications

sun java application server 8.2

i had a confusion on the installed directory of my application server a. if I create a domain w/o putting in directory, the domain automatically goes to /var/appserver/domains directory. I need it to be under /opt/SUNWappserver/domains.. If I will include this in domain creation, may logs are... (0 Replies)
Discussion started by: lhareigh890
0 Replies

3. Solaris

Sun Java System Directory Server

Hi, Does anyone know if the Sun Java System Directory Server (now Oracle Directory Server) is freely available for download? Thanks (1 Reply)
Discussion started by: Mack1982
1 Replies
Login or Register to Ask a Question

LEARN ABOUT SUNOS

asmigrate

asmigrate(1m)						    Application Server Utility						     asmigrate(1m)

NAME

       asmigrate - automates migration of J2EE applications from other J2EE platforms to Sun Java System Application Server

SYNOPSIS

       asmigrate  [-h  |  --help]  [-v	|  --version]  [(-c  |--commandline)  |  (-u  --ui) ] [-q | --quiet] [-d | --debug][-s | --sourcedirectory
       source_directory] [-S | --sourceserver source_application_server] [-t |	--targetdirectory  target_directory]  [-T  |  --targetserver  tar-
       get_application_server]	[-n  |	--scan-native-apis-only  ]  [-p  | --scan-packages package_list] [-j | --java2db create-tables=true, drop-
       tables=true, db-vendor-name=dbVendorName]  [-m  |  --migrate-cmp  comment-pk-modifiers=true,  overwrite-conflicting-accessors=true]  [-f  |
       --file-filter  all-files=true,  html-files=true,  java-files=true,  jsp-files=true, xml-files=true, archive-files=true] [-a | --append-logs
       ][operands]

       Use the asmigrate utility to analyze your J2EE application and translate vendor specific settings to Sun JavaTMTM System Application Server
       specific settings making the application deployable on Sun's J2EE products.

       The following table identifies the supported J2EE product migrations:

       +--------------------------+--------------------------------+
       |  Source J2EE Platform	  |   Destination J2EE Platform    |
       +--------------------------+--------------------------------+
       |WebSphere    Application  |Sun ONE Application Server 6.5  |
       |Server 4.0		  |				   |
       |			  |				   |
       |WebLogic     Application  |				   |
       |Server 5.1		  |				   |
       +--------------------------+--------------------------------+
       |WebLogic     Application  |Sun ONE Application Server 7    |
       |Server 5.1, 6.0, 6.1	  |				   |
       |			  |				   |
       |WebSphere    Application  |				   |
       |Server 4.0		  |				   |
       |			  |				   |
       |JavaTMTM    2	Platform  |				   |
       |Enterprise Edition 1.3	  |				   |
       |			  |				   |
       |Sun   ONE    Application  |				   |
       |Server 6.x		  |				   |
       |			  |				   |
       |Sun ONE Web Server 6.0	  |				   |
       |			  |				   |
       |JBoss Application Server  |				   |
       |3.0			  |				   |
       |			  |				   |
       |Tomcat Web Server 4.1.12  |				   |
       +--------------------------+--------------------------------+
       |WebLogic     Application  |JavaTMTM 2 Platform, Enterprise |
       |Server 5.1, 6.0, 6.1	  |Edition 1.4 Application Server  |
       |			  |				   |
       |WebSphere    Application  |				   |
       |Server 4.0		  |				   |
       |			  |				   |
       |JavaTMTM   2	Platform  |				   |
       |Enterprise	 Edition  |				   |
       |1.3/1.4 		  |				   |
       |			  |				   |
       |Sun   ONE    Application  |				   |
       |Server 6.x		  |				   |
       |			  |				   |
       |Sun ONE Web Server 6.0	  |				   |
       |			  |				   |
       |JBoss Application Server  |				   |
       |3.0			  |				   |
       |			  |				   |
       |Tomcat Web Server 4.1.12  |				   |
       +--------------------------+--------------------------------+
       |WebLogic     Application  |Sun JavaTMTM System Application |
       |Server 5.1, 6.0, 6.1	  |Server Platform Edition 8	   |
       |			  |				   |
       |WebSphere    Application  |				   |
       |Server 4.0		  |				   |
       |			  |				   |
       |JavTMTMa    2	Platform  |				   |
       |Enterprise	 Edition  |				   |
       |1.3/1.4 		  |				   |
       |			  |				   |
       |Sun    ONE   Application  |				   |
       |Server 6.x		  |				   |
       |			  |				   |
       |Sun ONE Web Server 6.0	  |				   |
       |			  |				   |
       |JBoss Application Server  |				   |
       |3.0			  |				   |
       |			  |				   |
       |JBoss Application Server  |				   |
       |3.2			  |				   |
       |			  |				   |
       |Tomcat Web Server 4.1.12  |				   |
       +--------------------------+--------------------------------+

OPTIONS

       -h --help		displays the arguments for launching the MigrationTool.

       -v --version		displays the version of the MigrationTool.

       -u --ui			invokes the tool in user interface mode.

       -c --commandline 	invokes the tool in command-line mode.

       -q --quiet		launches the tool in quiet mode.

       -d --debug		launches the tool in debug mode.

       -s --sourcedirectory	identifes the directory where the source code to migrate or scan is present.

       -S --sourceserver	identifes the source application server of the applications to be migrated. Possible servers include:

				 o  wl51: WebLogic Application Server 5.1

				 o  wl60: WebLogic Application Server 6.0

				 o  wl61: WebLogic Application Server 6.1

				 o  as65: Sun ONE Application Server 6.5

				 o  as70: Sun ONE Application Server 7.0

				 o  ws40: WebSphere Application Server 4.0

				 o  ri13: JavaTMTM 2 Platform Enterprise Edition 1.3

				 o  ri14: JavaTMTM 2 Platform Enterprise Edition 1.3

				 o  s1ws: Sun ONE Web Server

				 o  jb30: JBoss Application Server 3.0

				 o  tc41: Tomcat Application Server 4.1

       -t --targetdirectory	target or output directory where the migrated application should be placed.

       -T --targetserver	target application server to which the application is to be migrated.

       -n --scan-native-apis-onlscans the source code only for the presence of application server specific proprietary APIs.

       -p --scan-packages	comma-separated list of Java packages to scan.

       -j --java2db		bypasses  the  creation of the sun-cmp-mapping.xml file. Instead, introduces the option argument into the sun-ejb-
			       jar.xml file. Option arguments are:

				 o  create-tables: if set to true (default), creates tables at deploy. If set to false tables are not created.

				 o  drop-tables: if set to true (default), tables are dropped at undeploy. If set to false tables are not dropped.

				 o  db-vendor-name: name of the database vendor for  the  application  to  be  migrated.  Supported  vendor  names
				    include: Oracle, Sybase, DB2, Generic SQL92, PointBase, MSSQL.

       -m --migrate-cmp 	migrates 1.1 compliant CMPs, if any, to 2.0. Option arguments are:

				 o  overwrite-conflicting-accessors:  if  set  to true (default), conflicting accessors are overwritten. If set to
				    false, conflicting accessors are not overwritten.

				 o  comment-pk-modifiers: if set to true (default), setters of primary key are commented. If set to false, setters
				    of primary key are not commented.

       -f --file-filter 	selects the type of files to migrate. Option arguments are:

				 o  all-files: if specified and set to true (default), migrates all types of files.

				 o  html-files: if specified and set to true (default), migrates HTML files.

				 o  java-files: if specified and set to true (default), migrates Java files.

				 o  jsp-files: if specified and set to true (default), migrates JSP type files.

				 o  archive-files: if specified and set to true (default), migrates jar/ear/war/rar file types.

       -a --append-logs 	if  specified,	appends  the  logging to the existing or previous logs without overwriting them. If not specified,
			       previous logs are overwritten.

       operands 		identifes the archive file (jar/ear/war/rar) to be migrated.

SEE ALSO

       asupgrade(1M)

J2EE 1.4 SDK							    March 2004							     asmigrate(1m)