Monday Jan 07, 2008

Sun Product Users: Can we talk?

If you have a comment or a question, docs.sun.com (DSC) gives you a direct link to the writers of Sun documentation.

To comment on a particular document, while looking at the document online (on DSC), click Send Comments (see "1" in the graphic below). This is the preferred method in most cases. However, for general comments, you can use the Submit panel at the bottom of the  DSC page (see "2" in the graphic below). In all cases, please be as specific and detailed in your comments as possible.

The information provided by DSC visitors is often quite useful to the writer and is very much appreciated. If you find that the documentation is incorrect or just confusing, please let us know. Currently, the process is not fully automated, so the author might not see the comment for a while.
   

Image of docs.sun.com page with  areas marked from which to make comments 

Thursday Jan 03, 2008

Issues with Agent for Sun Java System Application Server 8.2/9.0/9.1

What's spurring this blog entry is a couple of issues that have come up with Policy Agent 2.2 for Sun Java System Application Server 8.2/9.0/9.1 as such:

  1. The title of this agent was just changed to include the 8.2 part. There were mixed messages out there about which agent to use for Sun Java System Application Server 8.2. Now it's cleared up. If you want to install Policy Agent 2.2 on Sun Java System Application Server 8.2, use Policy Agent 2.2 for Sun Java System Application Server 8.2/9.0/9.1.
  2. Do not install the Application Server 8.2/9.0/9.1 agent and Access Manager on the same Application Server 8.2/9.0/9.1 instance.

The second point comes up from time to time in different ways. For example, it came up in this forum posting:

http://forum.java.sun.com/thread.jspa?forumID=760&threadID=5201914

Anyway, the documentation for this agent states that you cannot install this agent and Access Manager on the same Application Server 8.2/9.0/9.1 instance, as such:

http://docs.sun.com/app/docs/doc/820-2539/gbbir?a=view 

However, this point is often missed. For example, I'm assuming that this issue was missed when someone sent a query to the docs.sun.com website. The question was about the following property:

com.sun.identity.agents.config.location

The property allows a J2EE agent to coexist with Access Manager on the same application server. This option does not apply to Policy Agent 2.2 for Sun Java System Application Server 8.2/9.0/9.1. Therefore, the property is not mentioned in Sun Java System Access Manager Policy Agent 2.2 Guide for Sun Java System Application Server 8.2/9.0/9.1.

I bring this up here because this second point gets missed pretty often. I figure that somehow the documentation isn't clear enough. So, I want to add this info here to try to make it more clear.

By the way, I should say something about how you can send comments to us technical writers when you are looking at documents on docs.sun.com. The question that I talk about above about the com.sun.identity.agents.config.location property was sent directly to docs.sun.com and eventually forwarded to me. Okay, it's decided then. In my next entry, I'll talk about how you can get comments to the writer of a document that you are reading on docs.sun.com.

Wednesday Nov 21, 2007

Fast Docs - Sun's got 'em!

docs.sun.com (dsc): A document repository barely alive. We can rebuild it. We have the technology. We can make it better than it was. Better...stronger...faster.

We can, we did! I say "we," even though I didn't have anything to do with it, just trying to show my community frame of mind.

Check out http://docs.sun.com and see if it isn't faster and more searchable than ever. If you're familiar with dsc, you know it has been slow and difficult to navigate and search. Then, for a short period of time, it got better. Then, it got worse again. Now, it's good again, great in fact.

I brought in a crack team of scientist to fix the problem. I say "I" even though I didn't have anything to do with it. I also say "brought in" even though nobody was brought in. As I understand it, after dsc was improved, a new problem quickly arose that was causing poor performance. The dsc folks investigated thoroughly, found, and then fixed the problem. I could tell you what the problem was, but then I'd have to bore you into a coma with the details. I'd also need to understand what they did. Suffice to say, look for documents on http://docs.sun.com and tell me if it isn't better than before.

Monday Jul 30, 2007

Search heals all wounds!

I think the title of this entry might be a good goal. Most definitely, at this point in time, search does not heal all wounds. Some would argue that search adds salt to wounds and grinds it in with great glee. But darn it anyways, I'm driven to figure this search thing out at Sun. I want to figure out what search can do for us now and how we can make it even better. I see a world where Sun customers come to Sun Microsystems sites and search across media types and pages, finding exactly what they need and very quickly: be it in a document, blog, article, screencast, or what have you? I won't say I have a dream, but I have a vision, anyway.

My last entry, Searching for stuff on Sun sites, though brilliant, didn't cover the nitty gritty of performing searches at Sun. This entry isn't going to do that either. Truth is I don't know the nitty gritty. I have learned a thing or two since that last entry.

What have I learned about search at Sun? Well, by reading the help at the docs.sun.com (DSC) site and at the Sun Search site I learned that the two sites handle search pretty differently. The key difference is that the two searches use different Boolean methods as illustrated below:

  • Sun Search: Please note that the default search is based on a Boolean AND; that is, results that are returned contain all of the search terms you entered.
  • DSC: The search is based on a Boolean OR, meaning that any of the specified search terms can be present in the documents that are returned in the search results.

I'm sure there's great wisdom involved in why these two searches at Sun are using different methods. To me, the difference seems ridiculous, but that's because I'm rather simple and can't see the grand design of such matters. When the pure intelligence of it is revealed to me, I'll let you know, too.

Anyway, I think that Sun Search really is a great tool for searching across media types. I highly recommend it. And I am hopeful that we can make it even better.

Wednesday Jul 25, 2007

Searching for stuff on Sun sites

Fellow Sun identity writer Michael Teger, has just added a nice blog entry, Searching Collections on docs.sun.com.

This seems like a good time to point out some other search tricks. Hopefully, I can learn some, too, cuz I can just sense it: there's more to know about searching Sun sites than I've yet to learn.

The site http://docs.sun.com/ (DSC) is new and improved. It's faster anyway. In most ways the search is better, too. But as Michael points out, searching collections is not available in the same way it used to be. Now, it can be done as a workaround, which Michael provides. Also noteworthy is the fact that DSC provides a link to Search Tips.

There are few nuggets of information in the tips. For example, Michael provided this example for a search: "Access Manager 7.1" load balancer. You could type this instead: "Access Manager 7.1" | load balancer. The pipe symbol, "|" doesn't get you that much since the search results look exactly the same through several pages of the search results. However, the search with the pipe symbol has 206 results while the search without the pipe symbol has 43,085. The pipe symbol means that you are first searching for docs with "Access Manager 7.1," then you're working from those results to search for "load balancer." This might not matter since the first 20 pages or so of these two searches are probably giving the exact same results. However, it's nice to know that there are only 206 results that are relevant to your search instead of over 43,000.

A couple of other tricks are that you can search in titles only and you can use wildcards (\* and ?) in your search. For this information, check out the search tips in Chapter 2.

Better yet, you can search beyond docs.sun.com. You can search all of Sun. Sometimes, that's better and sometimes it's not. Anyway, this can be extremely useful information. Here it is: SunSearch.

Why is this important? Because with SunSearch you can also search forums, blogs, articles, etc. It's very powerful. If this information isn't in docs, it might still be somewhere within the various sun sites. Using the example that Michael provided, I want to search on SunSearch. However, I'll add the pipe symbol to see what happens: "Access Manager 7.1" | load balancer.

The results on SunSearch are not exactly clear to me. To me it doesn't seem that the pipe symbol works and the number of results seems quite low compared to searching DSC. However, the tabs shown at the top are very useful. The default tab is All Results, which might provide too much info. The Community tab is good because it searches blogs, forums, and articles. For this search, at this time, I see 7 results in the Community tab. Seven results is quite manageable. The following image shows this search. Notice the pipe symbol is included. I tried the search without the pipe symbol and the results were the same.

A screen shot of SunSearch: Okay, so I don't get all the nuances. If anyone understands these nuances, such as why the number of results is relatively low, please do explain. All the same, this seems to make it easier to search for a topic across media types and such all over Sun.


About

What does this box do?

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today