replicating domains
Hello,
We have a number of domains running on iPS v3.0sp3, and will be adding
more all the time (incidently, anyone run into any limits on the number
of domains iPS can support at one time?). All of these domains are
customized from the default setup (in terms of authentication
mechanisms, channels available, policy for channels, and roles), but
they're all pretty much the same.
Ideally, I'd like to customize one domain, and then copy it under a
different name, to ease the pain of creating a new domain. That way we
can have a template domain that we can just import.
So, I set up a domain (cleantemplate) just the way we'd like, and used
the ipsadmin command to export it to a xml file:
$ ipsadmin get domain cleantemplate > cleantemplate.xml
(This spits all the customized bits of cleantemplate to file--is there a
way I can use ipsadmin to see *all* of the attributes of the
cleantemplate domain?) Then I tried to import the file back into iPS:
$ ipsadmin create domain newdomain cleantemplate.xml
However, I get some weird behavior (basically, when you go to
http://portalserver/login?domain=newdomain you get the 'Domain doesn't
exist message'). Also, I can see 'newdomain' in the console tool when I
click 'manage domains' but I can't delete it--it simply says 'failed to
delete newdomain' when I try (I had to use the ldap console). I did an
ldif dump of the database and the differences between cleantemplate and
newdomain were minimal (timestamps, pretty much).
I also tried using the cleantemplate ldap entry and the ldif2db script,
but the ldif2db script apparently needs the directory server to be shut
down, and this isn't exactly feasible.
Has anyone looked at this problem? Is there some other ldap entry that
I need to be modifying, or does the 'create new domain' link on the
admin console do some heavy magic that I'd be better off avoiding?
Thanks for any help,
Dan
[2129 byte] By [
] at [2007-11-25 4:31:01]
Dan Moore wrote:
> Hello,
>
> We have a number of domains running on iPS v3.0sp3, and will be adding
> more all the time (incidently, anyone run into any limits on the number
> of domains iPS can support at one time?). All of these domains are
> customized from the default setup (in terms of authentication
> mechanisms, channels available, policy for channels, and roles), but
> they're all pretty much the same.
>
> Ideally, I'd like to customize one domain, and then copy it under a
> different name, to ease the pain of creating a new domain. That way we
> can have a template domain that we can just import.
>
> So, I set up a domain (cleantemplate) just the way we'd like, and used
> the ipsadmin command to export it to a xml file:
>
>$ ipsadmin get domain cleantemplate > cleantemplate.xml
>
> (This spits all the customized bits of cleantemplate to file--is there a
> way I can use ipsadmin to see *all* of the attributes of the
> cleantemplate domain?) Then I tried to import the file back into iPS:
>
>$ ipsadmin create domain newdomain cleantemplate.xml
>
> However, I get some weird behavior (basically, when you go to
> http://portalserver/login?domain=newdomain you get the 'Domain doesn't
> exist message'). Also, I can see 'newdomain' in the console tool when I
> click 'manage domains' but I can't delete it--it simply says 'failed to
> delete newdomain' when I try (I had to use the ldap console). I did an
> ldif dump of the database and the differences between cleantemplate and
> newdomain were minimal (timestamps, pretty much).
>
> I also tried using the cleantemplate ldap entry and the ldif2db script,
> but the ldif2db script apparently needs the directory server to be shut
> down, and this isn't exactly feasible.
>
> Has anyone looked at this problem? Is there some other ldap entry that
> I need to be modifying, or does the 'create new domain' link on the
> admin console do some heavy magic that I'd be better off avoiding?
>
> Thanks for any help,
> Dan
Hi folks,
In case anyone is ever interested in doing this again, here's the
answer, assuming that template is the template domain and copy is the
derived domain (gotten through experimentation and iPlanet support):
/info/ips/SUNWips/bin/ipsadmin get domain template > template.xml
/info/ips/SUNWips/bin/ipsadmin get role template/defaultRole >
templateRole.xml
edit both the .xml files, replacing text 'template' with text 'copy'.
/info/ips/SUNWips/bin/ipsadmin create domain copy template.xml
/info/ips/SUNWips/bin/ipsadmin create role copy/defaultRole templateRole.xml
Dan
at 2007-6-29 2:38:25 >
