Appendix E Extended Sun ONE Portal Server 3.0 Component Migration

This appendix describes the steps you need to take when migrating an extended Sun ONE Portal Server 3.0 component to a Sun™ ONE Portal Server 6.2 service.


Note	All instances of the Sun™ ONE Portal Server 3.0 product refer to what were formerly known as the iPlanet™ Portal Server 3.0, Service Pack 3a, iPlanet™ Portal Server 3.0, Service Pack 4 products, and iPlanet™ Portal Server 3.0, Service Pack 5 products.

Options For Making Manual Changes After Migration

The Sun ONE Portal Server 3.0 Migration Tool Suite retains the mapping between iwtUser and the amUser service. If, for example, you have extended iwtUser and attributes have been added, the migration tools do not migrate those attributes. After migration, you need to make manual changes using one of the two following options:

Option 1

This will ensure that all the extended attributes are now available in Sun ONE Portal Server 6.2.

Option 2

Code Example E-1 Sample Script to Convert Attributes

#!/usr/bin/perl

open(USERFILE,”/tmp/user.ldif”) || die “$!: Cannot open it”;

@attrsToAdd=(“test-attr-one-at”,”test-attr-to-add-at”);

#while(<USERFILE>){

while (@block=getBlock(\*USERFILE)){

$_=shift(@block);

#print “\n”;

foreach $attr(@attrsToAdd){

$j=0;

foreach $block_line(@block){

$position = index($block_line,$attr);

if($position >= 0){

@splitAttr=split(/:/,$block_line);

$reqAttr[$j]=$splitAttr[1];

$j++;

}

if($j > 0){

print “\n”;

print $_;

print “\nchangetype:modify”;

print “\nadd:”;

print $attr;$k=0;

while($k < $j){

print “\n$attr:$reqAttr[$k]”;

$k++;

}

print “\n”;

}

close USERFILE;

sub getBlock {

my ($fhref) = @_;

local ($curLine, $inBlock);

$inBlock=0;

while (!eof($fhref)){

$_=getLine($fhref);

# Not sure if I want to ignore this one yet

# if ($curLine =~ /0---iwt-Profile-Reversed---0/) {next;}

# Check for new block

if (/^dn: cn=(.+?),/) {

$user=$1;

# Reset user attribute array

@blockInfo=($_);

$inBlock=1;

next;

}

# Check for end of Block

if (/^$/){

if ($inBlock ==1){

return @blockInfo;

} else {

next;

}

# Regular data, push it on

push @blockInfo,$_;

}

if ($inBlock==1){

# Add last line

if ($_=getLine($fhref)){

push @blockInfo,$_;

}

return @blockInfo;

} else {

return ();

}

sub getLine {

my ($fhref) = @_;

while(<$fhref>) {

chop;

if (/^ (.+)/){

$lastLine.=$1;

# print “Line is now:\n$lastLine\n”;

} else {

$thisLine=$lastLine;

$lastLine=$_;

return $thisLine;

}

# Take care of that last line

if ($lastLine) {

$thisLine=$lastLine;

$lastLine=””;

return $thisLine;

}

return $lastLine;

}

Example of Adding Custom Sun ONE Identity Server Attributes for Sun ONE Portal Server 6.2

This example shows the steps necessary for adding timezone and department attributes to Sun ONE Identity Server for use with Sun ONE Portal Server 6.2. You must first use the admin console to add iplanetamuserservice as a required service for all users. This permits custom attributes to be populated properly from the Sun ONE Identity Server SDK.

In the admin console, from the top level (o=isp), select service management and for service name Sun ONE Identity Server Configuration, select the icon next to Administration.

Scroll down the list of settings to Required Services and add iplanetamuserservice.

Click Save.

Restart Sun ONE Identity Server. For example:

BaseDir/SUNWam/bin/amserver start

Add custom LDAP object class and attributes by adding the following to the /usr/ldap/slapd-host/config/schema/99user.ldif file using ldapmodify:

objectclasses: (examplePerson-oid NAME ‘examplePerson’ DESC ‘example Person Extensions’ SUP top AUXILIARY MAY (example-am-user-timezone $ example-am-user-deptno) )

attributetypes: ( example-am-user-timezone-oid NAME ‘example-am-user-timezone’ DESC ‘example User Timezone and Region’ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 X-ORIGIN (‘user defined’) )

attributetypes: ( example-am-user-deptno-oid NAME ‘example-am-user-deptno’ DESC ‘example User Department Number’ SYNTAX 1.3.6.1.4.1.1466.115.121.1.15 X-ORIGIN (‘user defined’) )

Note that the OID 1.3.6.1.4.1.1466.115.121.1.15 represents an LDAP string type.

Make of copy of the BaseDir/SUNWam/config/xml/amUser.xml file. If you want to add entries to the amUser.xml file, backup the original first.

Corresponding to the iwtUser extensions that you have made, add entries to the copy of the BaseDir/SUNWam/config/xml/amUser.xml file. These changes should be in accordance with the BaseDir/SUNWam/dtd/sms.dtd file. For more details, see the Sun ONE Identity Server Programmer’s Guide.

Add the following to the schema global description to refer to custom LDAP objectclass:

<Schema

serviceHierarchy=”/DSAMEConfig/iPlanetAMUserService”

i18nFileName=”amUser”

i18nKey=”iplanet-am-user-service-description”>

<AttributeSchema name=”serviceObjectClasses”

type=”list”

syntax=”string”

i18nKey=””>

<Value>iplanet-am-user-service</Value>

<Value>examplePerson</Value>

</DefaultValues>

</AttributeSchema>

</Global>

Add the following new custom attributes:

<AttributeSchema name=”example-am-user-timezone”

type=”single”

syntax=”string”

any=”display|optional|filter”

i18nKey=”u121”>

</AttributeSchema>

<AttributeSchema name=”example-am-user-deptno”

type=”single”

syntax=”string”

any=”display|optional|filter”

i18nKey=”u122”>

</AttributeSchema>

Using the amadmin utility, in BaseDir/SUNWam/bin, delete the existing user Service. For example:

./amadmin -u “uid=amadmin,ou=People,o=defaultorg,o=rootsuffix|dc=defaultorg,
dc=rootsuffix” -w password --deleteService iPlanetAMUserService

Load the new, modified user service. For example:

./amadmin -u “uid=amadmin,ou=People,o=defaultorg,o=rootsuffix|dc=defaultorg,
dc=rootsuffix” -w password --schema amUser.xml

Edit u121 and u122 strings in BaseDir/SUNWam/locale/amUser.properties.

Restart Sun ONE Portal Server,Sun ONE Identity Server, and Sun ONE Directory Server.

Shut down the LDAP server manually and start it again by issuing the following commands:

BaseDir/SUNWam/bin/amserver stop

/usr/ldap/slapd-host/stop-slapd

BaseDir/SUNWam/bin/amserver start



Note	You must shutdown the LDAP server manually for the new 99user.dif schema extensions to take effect.

Previous Contents Index Next
Sun Java System Portal Server 6 2004Q2 Migration Guide