A monitoring framework based on the Java Dynamic Management Kit (JDMK) was introduced in OpenSSO Express Build 8. Access to OpenSSO's monitoring data may be via the HTTP, SNMP (Simple Network Management Protocol), or RMI (Remote Method Invocation) interfaces.
In OpenSSO Express Build 9 (and currently available in the nightly build), access to the Monitoring Service's HTTP interface has been modified to require authentication to access OpenSSO monitoring data through the HTTP interface. (An HTML Protocol Adaptor comes with the JDMK and is used to authenticate. See The HTML Protocol Adaptor for more information.)
The opensso_mon_auth file contains the name and password of the user (or users) with permission to log in and see the OpenSSO monitoring data. It is located in the /ConfigurationDirectory/install-URI/ directory created during the OpenSSO installation; by default, /opensso/opensso/opensso_mon_auth. The file initially contains the user demo with an encrypted value equal to the password changeit. This user can be replaced or additional users added to the file. Type any user identifier followed by a space and the encrypted value of the user's password. The user name is case-sensitive and the password must be encrypted using the ampassword command line tool. It is located in the ssoAdminTools.zip which is in the tools directory of the expanded opensso.zip. For more information see Installing the OpenSSO Enterprise Utilities and Scripts.
NOTE: The user in this file is not tied in any respect to the OpenSSO user data store. Authentication to the monitoring data using the HTML Protocol Adaptor is a separate authentication process from that of OpenSSO.
Now just a little wish from ABBA (and me, by proxy) for all to enjoy the new year and decade. Happy New Year from the Super Trouper LP - an acronym from many new years ago.
If you are one of the many who have been caught up this summer with ABBA fever due to the release of Mamma Mia!, you just might find it interesting. There's pix, history, videos, music, links galore, and even a short clip of me performing. Enjoy.
For those NOT interested and so your visit to this entry is not a total loss, how about a number from another film musical. Here's Doris Day singing I'm Not At All In Love from The Pajama Game.
An affiliation (referenced by an affiliationID) is a grouping of entity providers configured using OpenSSO and maintained by an affiliation owner who chooses the members without regard to the boundaries of any circles of trust which might also include the entity providers as members. Affiliation-based federation is indicated by a boolean flag at the service provider and uses the affiliationID defined for the remote provider (since a local provider can participate in more than one affiliation). If enabled, the authentication request will be sent with the affiliation flag set to true.
Affiliation data is part of the provider metadata. A service provider request denotes whether the request is being made as part of an affiliation or not. If services are invoked as an affiliation member, a service provider might issue an authentication request for a user on behalf of the affiliation. When authentication is secured, the user can achieve single sign-on with all members of the affiliation.
And for those who don't know - I have an affiliation with ABBA. In honor of the upcoming release of Mamma Mia here's the group's music video for the title tune (mysteriously aped in Muriel's Wedding for Muriel and Rhonda's karaoke performance of...Waterloo?).
And here's the trailer for the film. Meryl Streep (sounding great), Julie Walters and an uncredited (?) Christine Baranski - what a trio!!
Hot off the digital press - a new manual has been added to the Access Manager 7.1 set of documentation:
Sun Java System Access Manager Localization Guide
The Localization Guide (published as a Technical Note although the notes I usually read don't run to 26 paginas) describes the organization of localized Access Manager software resource files. It also explains how to add a new language to the list of supported languages and how to customize an existing language's resource files.
In other words, name that language!
Internationalization (numeronym: I18N) refers to the planning and implementation of a software framework for multiple language support. This framework can then be easily adapted for region-specific languages and cultures. You can refer to a product as being internationalized if it has been developed to meet most of the needs of an international community, but not yet customized (see localization) to a specific region. This might include:
Allowing space in user interfaces for translation
Developing with products that support international character sets
Creating graphics and images with text labels that can be translated inexpensively
Using written examples with global meaning
Ensuring data space so that messages can be translated from languages with single-byte character codes (such as English) into languages requiring multiple-byte character codes
Localization (numeronym: L10N) is the process of creating content (input and output data) for a region-specific culture and language.
Globalization (numeronym: G11N) refers to a program or application that is usable across multiple cultures and regions, irrespective of the language and regional differences. Sounds like I18N to me.
Glocalization (oh, brother) is a term that was invented to emphasize that the globalization of a product is more likely to succeed when the product or service is adapted specifically to each locality or culture in which it is marketed. The term combines the words globalization and localization.
For example, this German language video by super-singing sensation ABBA was internationalized when the original English lyrics were written simply for easy translation. It was localized when the lyrics were translated into German, Spanish, French, and Swedish. It was globalized when all versions were released worldwide, simultaneously, and it became a shining example of glocalization (oh, brother) when the song became a HUUGGGEEE hit.
(UPDATE: See Nico's comments for more precise (and certainly less facetious) information on the differences between the -izations.)