Registering ds 5.2 on dscc

hi!
im trying to register a DS 5.2 in a fresh DSCC but it complains about the DSCC agent port. DS and DSCC are running on different machines.
im i missing something on the DS side? i can't find anything in the docs.
regards.

Hi,
DSCC is the console for Directory Server Enterprise Edition 6 and doesn't know how to manage DS5.x
So you cannot register an instance of 5.2 in it.
This is mentioned in the release notes, as far as I remember.
Regards,
Ludovic.

Similar Messages

DSCC showing DS as 636 disabled, unexpected error,err=1 and 80

Dear All,
Am adding new DS on an existing DSEE 6.3 environment. Up to now, created a new DS instance remotely from the DSCC server, copied configuration settings from an existing DS server. After that stage, dscc was showing remote DS server as 636 (disabled} and unexpected error. This was expected due to SSL certs are not added in the DS. Today we have added the SSL cert and Root CA. And restarted the DS, and unregistered and registered back the DS on DSCC. But still the DS status on DSCC showing as 636 disabled, unexpected error
On more investigation, able to see like ldapsearch on secure port on local DS giving result, but when doing remotely from the DSCC server to DS server, result as below
bash-3.00$ sudo ./ldapsearch -D "cn=directory manager" -w xxx -h remote-host -p 636 -Z -P /opt/SUNWdsee/AAAinst/alias/slapd-cert8.db -b "" -s base objectclass=
ldap_simple_bind: Can't contact LDAP server
SSL error -8156 (Issuer certificate is invalid.)
Please advise me here,
Below are the logs am able to see from DS access and error log, please help.
[12/Sep/2011:19:31:24 +1000] conn=233 op=0 msgId=1 - EXT oid="1.3.6.1.4.1.1466.20037"
[12/Sep/2011:19:31:24 +1000] conn=233 op=0 msgId=1 - RESULT err=0 tag=120 nentries=0 etime=0, Start TLS request accepted.Server willing to negotiate SSL.
[12/Sep/2011:19:31:24 +1000] conn=233 op=-1 msgId=-1 - SSL 128-bit RC4
[12/Sep/2011:19:31:24 +1000] conn=233 op=1 msgId=2 - BIND dn="cn=admin,cn=Administrators,cn=dscc" method=128 version=3
[12/Sep/2011:19:31:25 +1000] conn=233 op=1 msgId=2 - RESULT err=1 tag=97 nentries=0 etime=1, Can't connect to the LDAP server
[12/Sep/2011:19:31:25 +1000] conn=234 op=-1 msgId=-1 - fd=26 slot=26 LDAP connection from 58.163.116.188:64087 to 172.17.67.235
[12/Sep/2011:19:31:25 +1000] conn=234 op=0 msgId=1 - BIND dn="cn=admin,cn=Administrators,cn=dscc" method=128 version=3
[12/Sep/2011:19:31:25 +1000] conn=234 op=0 msgId=1 - RESULT err=1 tag=97 nentries=0 etime=0, Can't connect to the LDAP server
[12/Sep/2011:19:31:25 +1000] conn=234 op=1 msgId=0 - RESULT err=80 tag=120 nentries=0 etime=0
[12/Sep/2011:19:31:25 +1000] conn=234 op=-1 msgId=-1 - closing from 58.163.116.188:64087 - A1 - Client aborted connection -
[12/Sep/2011:19:31:25 +1000] conn=234 op=-1 msgId=-1 - closed.
[12/Sep/2011:19:31:25 +1000] conn=235 op=-1 msgId=-1 - fd=26 slot=26 LDAPS connection from 58.163.116.188:64088 to 172.17.67.235
[12/Sep/2011:19:31:25 +1000] conn=235 op=-1 msgId=-1 - SSL 128-bit RC4
error
12/Sep/2011:19:38:44 +1000] - ERROR<53761> - Plugins - conn=-1 op=-1 msgId=-1 - Connection Bind through PTA failed (91).
[12/Sep/2011:19:38:44 +1000] - ERROR<53761> - Plugins - conn=-1 op=-1 msgId=-1 - Connection Bind through PTA failed (91). Retrying...
[12/Sep/2011:19:38:44 +1000] - ERROR<53761> - Plugins - conn=-1 op=-1 msgId=-1 - Connection Bind through PTA failed (91).
Thanks,
Edited by: user1175091 on Sep 12, 2011 4:34 AM

Dear All,
We were able to find the root cause for the above issue, the DSEE still using the default certificate instead of new SSL host certificate.
ssl-enabled : on
ssl-rsa-cert-name : defaultCert
Could you guide me the commands for changing this to new SSL certificate, through DSCC due to environmental problem we are not able to achieve this.

DSEE 7 lacks webconsole administration, dscc agent problems

I recently reinstalled one of my Sun Sparc (V210) servers with the latest Solaris 10 release.
Solaris 10 10/09 s10s_u8wos_08a SPARC
Previously I had DSEE 6.3 installed. Didn't have the original downloads handy (my bad) so went to download them again. The oracle download liinks are currently brokem (thanks oracle.) It was fine last week. As per previous post was able to download DSEE 7 packages. Could not download DSEE 6 packages. Installed DSEE 7. Created my database instances and suffixes and restored from LDIF files
server1# dsadm create ...
server1# dsconf create-suffix ...
server1# dsadm import ...
I can not get the DSCC webconsole module to work.
Did the following
server1# /opt/SUNWdsee7/bin/dsccsetup initialize
server1# svcadm restart webconsole
server1# /usr/sbin/cacaoadm enable
server1# /usr/sbin/cacaoadm start
start: server (pid 7270) already running
server1# ./dsccsetup cacao-reg
DSCC Agent is already registered
Can login to the server webconsole with no problem, but the dscc app is not listed.
If I try to manage the ldap server on this server (e.g. server1) from web console on another machine (e.g. server2) , I get the warning that the dscc agent is not running on the server1.. Which it clearly is.

I have installed Sun web server 7.0 on my server. When prompted, I specified /usr/java (ie. java jdk 1.5.0_25-b03) for the java path.) Web server wanted 1.5._09 or later.
jdk 1.5.0_25-b03 is the default java install on the system.
# java -version
java version "1.5.0_25"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_25-b03)
Java HotSpot(TM) Server VM (build 1.5.0_25-b03, mixed mode)
jdk1.6.0_21 is also installed but is not the default.
It seems that something than runs with java 1.5 is not necessarily guaranteed to run with java 1.6 so I figured.
I editted the admin server magnus.conf file as per the install docn.
"dsccsetup initialize" seemed to finally run without leaving messages in /var/adm/messages about java problems.
I deployed the WAR file in the web server. If I click the option to enable JSP precompiliation I get the message
ADMIN3320: JSP Compilation Error: file:/opt/sun/webserver7/admin-server/config-store/xxxxxxxxxxxxxx/dscc7/jsp/ProxyInstanceNotImplemented.jsp(51,0) PWC6305: The end tag "</cc:pagetitle" is unbalanced
If I deploy with out enabled JSP precompilation it seems to deploy OK. When I connect (from Firefox 3 on linux) to
http://myserver.domain.com /dscc7 I get redirected to
http://myserver.domain.com/dscc7/dcc7Module/DCC
with the messages
Error reading installation configuration
An unexpected error occurred while checking the status of Sun Directory Service Control Center.
Show Details
Hide Details
Install Error Code: 3
Stack:
com.sun.directory.common.slapx.AdmCmdErrorException: /opt/SUNWdsee7/bin/dsadm info all separator = /var/opt/SUNWdsee7/dcc/ads [exitCode=60]
com.sun.directory.common.slapx.AdmCmd.run(AdmCmd.java:94)
com.sun.directory.common.slapx.AdmCmd.run(AdmCmd.java:56)
This aside, I can still not register this server in the dscc console on any of the other directory servers (they are running DSEE 6.3.) Those servers report that cacao is not running on this server. It clearly is running tho.
# cacaoadm status
default instance is ENABLED at system startup.
Smf monitoring process:
1200
1201
Uptime: 2 day(s), 17:25
Are these two issues related? Are they both symptoms of a java problem (I didn't think cacao used java)?
Are they both symptoms of cacao not responding to queries?
Are they both sympoms of a problem with dscc agent not working properly?
The port dscc agent port is open to other machiens
telnet xxxx 11162Trying xxxx...
Connected to xxx.
Escape character is '^]'.
��sr5javax.management.remote.message.HandshakeBeginMessage�,���6profilestLjava/lang/String;Lversionq~xptTLS SASL/PLAINt1.0^CConnection closed by foreign host.

Register DS and DPS 6.3.1 in DSCC7 fails

I'm currently running DSCC7 in my environment and it manages both DSEE 6.3.1 and 7.0 proxy servers and directory servers. I have a need to add an additional 6.3.1 proxy server and directory server to my configuration. I've installed the 6.3.1 software on both hosts however when I attempt to add the new servers in DSCC I get the following message:
The DSCC agent module is not registered on host dps05.domain.com. Verify that the agent module is installed using the command dsccsetup status on host linopsdps05.mgnt.endeca.com.
If the agent module is installed register it using the command dsccsetup cacao-reg.However cacaoadm is running and the agent is registered.
# ./dsccsetup status
DSCC Application is not installed
DSCC Agent is registered in Cacao
DSCC Registry cannot be created (dsadm is not installed)
***I looked at the logs for cacaoadm and noticed these messages at the times I was attempting to add the server to DSCC:
Feb 25, 2011 9:55:03 AM com.sun.cacao.agent.auth.CacaoCallbackHandler handle
FINE: Unrecognised mechanism: com.sun.directory.dscc7I was under the impression that DSCC7 was fully capable of managing and compatible with DSEE 6.3.x hosts. Has anyone else experienced this issue? Is there a workaround or some configurating I can change to get it to work?
Edited by: enetops on Feb 25, 2011 7:00 AM

DSCC 7 is not able to create or register instances using DSCC agent 6.x. However it is able to manage 6.x instances as soon as they are already registered in the 7.x DSCC registry.
So a workaround is to create the servers using 6.x CLIs (dsadm/dpadm) and use 'dscc6/bin/dsccreg add-server' to register them in the 7.x DSCC registry.

Problems with ODSCC 11.1.1.5.0...

I am testing upgrading from DSEE 6.3.1.1 to ODSEE 11.1.1.5.0 in my lab. I am running into issues with registering existing proxy servers (that have been upgraded) to the ODSCC. There are directory servers on the same boxes as the proxy servers and they register just fine. Here is what I am seeing:
History: DPS servers were 6.3.1.1 upgraded to 11.1.1.5.0, and the DS servers were 6.3.1.1 upgraded to 11.1.1.5.0. The servers function fine, and the upgrade was successful. ODSCC is also upgraded from DSCC 6.3.1.1 to 11.1.1.5.0, and it is running on the latest version of Glassfish 3.1.
- After registering an existing proxy server using the ODSCC console, the proxy shows up in the ODSCC console with "Unexpected Error" as the "Operational Status".
     Ran the following command on the DPS server to register it:
     /opt/dsee7/bin/dsccreg add-server -h <dscc_server_name> -p 3998 /opt/dsee/<local_ds_instance_name>
The command returns the following and looks successful:
Enter DSCC administrator's password:
     /opt/dsee/<proxy_instance>/ is an instance of DPS
     Enter password of "cn=Proxy Manager" for /opt/dsee/<proxy_instance>/:
     Connecting to /opt/dsee/<proxy_instance> (using ldap://127.0.0.1:389)
     Enabling DSCC access to /opt/dsee/<proxy_instance>
     Registering /opt/dsee/<proxy_instance> in DSCC on <dscc_server_name>.
     If you click on the proxy server in the ODSCC console it goes to the management page for that server. (as it should)
     You are able to stop, start and restart the server with the buttons on the management page.
     But if you click on any of the tabs on the management page, it goes to a page that asks for the "Directory Service Manager Authentication" with admin in the username field for "Directory Service Manager"
     After you enter the correct password it returns you to the "Common Tasks" page. (no errors, it just redirects the main page and the popup window closes)
     If you click on the "Proxy Servers" tab, it still shows "Unexpected Error" for the proxy.
     If you try to unregister the proxy server through the ODSCC console you get the following error:
          Error communicating with server tdprfdsm1:389. The error is java.lang.IllegalArgumentException: console-administration-server-urls
          However, it does remove it from the ODSCC console.
     Also, if you try registering an existing proxy server through the ODSCC web console you get the same error as above:
          Error communicating with server tdprfdsm1:389. The error is java.lang.IllegalArgumentException: console-administration-server-urls
          However, the server is not added to the ODSCC.
     This is happening on all of my servers I am testing on. The proxy servers also have a directory server on the same physical box, and the directory servers register fine, from both the command line and from the ODSCC console.
     I have also tried registering existing proxy servers with the ODSCC without importing the old DSCC6.X registry (starting with a fresh ads database), and get the same results.
Any help would be much appreciated.
Thank you!

Please let us know if you make progress on this.
I'm seeing a similar issue with Tomcat 5.5. I'm able to browse most of the directory, but some sections, when I try to bring up the details on an entry, it will prompt me for the "Directory Service Manager Authentication" and upon entering that, get booted to the common tasks screen. I've noticed that if I go to Server Operation->Error Logs (or Access and Audit Logs), there will be a warning saying "An authentication is required to connect to ldaptest. Click here to enter user ID and password". Clicking on the link and entering the root credentials for the server will then let me see the logs. After doing that once, I was able for a short time to browse the LDAP entries I previously couldn't, so I suspect this is some type of permission issue.

Error registering server to DSCC

Hi Guys
On a fresh ODSEE install I am trying to run the following command
"dsccreg add-server -h HOSTNAME -p 3998 /server/dsee7/odseeserver"
I get the following error
Enter DSCC administrator's password:
/server/dsee7/odseeserver is an instance of DS
Enter password of "cn=Directory Manager" for /server/dsee7/odseeserver:
This operation will restart /server/dsee7/odseeserver.
Do you want to continue ? (y/n) y
Connecting to /server/dsee7/odseeserver (using ldap://127.0.0.1:389)
Failed to connect to /server/dsee7/odseeserver
*Server replied : [LDAP: error code 32 - No Such Object]*
*/server/dsee7/odseeserver has not been registered in DSCC on HOSTNAME.*
Any ideas?
The port is running
bash-3.00$ netstat -an | grep 389
*.389 *.* 0 0 49152 0 LISTEN
*.389 *.* 0 0 49152 0 LISTEN
svcs command shows the server is running
the DSCC is on another server which I can access and see that it is active

cn=Directory Manager is a special user that does not exist anywhere on your DIT. Also, when you create the instance, the suffix is not automatically created, thus you cannot create an admin user under a suffix that does not exist yet even if you are just creating a seperate admin account that just happen to have a similar name as the directory manager name.
The ADS root tree entry is cn=dscc so all your DSCC admin users are by default created under cn=Administrators,cn=dscc
Hope this clarifies it.

Registering Existing Server on new ODSEE 11.1.1.7 DSCC

The DSCC from 11.1.1.5 allowed you to register existing servers and gave you the option to add a new host and use a different port. I am running DSCC on one machine and would like to register and monitor all my servers from this one DSCC GUI. It makes it really easy to verify that all my servers are up and running by looking at the list of all my local and remote directory servers. I just installed 11.1.1.7 and went to register an existing server. It only defaults to the local host and port 3779 and you cannot change it or add a new remote host. Does this mean with 11.1.1.7, you can only create and register servers on the local host that DSCC is running? If there is a new way to do it, I could not find it in the documentation. Any help would be appreciated.

Multiple DSCC environment is possible.
I did it in this way:
1) Unzip the binaries on both HOST_A and HOST_B
2) Create the DSCC registry on HOST_A
3) Create the DSCC agent on HOST_A and register it on DSCC on HOST_A
4) Create the DSCC agent on HOST_B and register it on DSCC on HOST_A (use the -h option)
5) Start the agent on HOST_A
6) Start the agent on HOST_B
7) Create dscc7.war on HOST_A
8) Deploy DSCC on a WebContainer on HOST_A
9) Create the DSCC registry on HOST_B
10) Create the DSCC agent on HOST_B and register it on DSCC on HOST_B (it will use a different port)
11) Create the DSCC agent on HOST_A and register it on DSCC on HOST_B (use the -h option)
12) Start the new agent on HOST_A
13) Start the new agent on HOST_B
14) Create dscc7.war on HOST_B
15) Deploy DSCC on a WebContainer on HOST_B
My config looks like this:
HOST_A
bash-3.00# /opt/dsee7/bin/dsccreg list-agents
Enter DSCC administrator's password:
Hostname      Port Certificate Type        Owner Flags iPath                     Description
opensso-dev1 3997 undefined    DSCC_AGENT root   -      /opt/dsee7/var/dcc/agent -
opensso-dev2 3997 undefined    DSCC_AGENT root   -      /opt/dsee7/var/dcc/agent -
2 agent(s) displayed
bash-3.00#
HOST_B
bash-3.00# /opt/dsee7/bin/dsccreg list-agents
Enter DSCC administrator's password:
Hostname      Port Certificate Type        Owner Flags iPath                      Description
opensso-dev1 7995 undefined    DSCC_AGENT root   -      /opt/dsee7/var/dcc/agent2 -
opensso-dev2 7995 undefined    DSCC_AGENT root   -      /opt/dsee7/var/dcc/agent2 -
2 agent(s) displayed
bash-3.00#

Could not contact the DSCC agent on ldap-dj (my testing host)

Hi,
I have installed dsee7 "Oracle Directory Serivce Control"
When I am attempting to register a server. I receive the following error message
Additionally having problems to enable cacaoadm.... any recommendations?
Your help is greatly appreciated.
Thanks.
D.J.
"Could not contact the DSCC agent on ldap-dj. Use the cacaoadm to check that the DSCC agent is installed and running on port 11162
[oracle@ldap-dj bin]$ dsccsetup status
DSCC Agent is registered in Cacao
Cacao is down. Start it using:
/u01/dsee7/ext/cacao_2/cacao2/bin/cacaoadm start
Cacao uses a custom port number (21162)
DSCC Registry has been created
Path of DSCC registry is /u01/dsee7/var/dcc/ads
Port of DSCC registry is 3998
[oracle@ldap-dj bin]$
[oracle@ldap-dj bin]$ id
uid=501(oracle) gid=502(oinstall) groups=502(oinstall),503(dba),504(oper),505(asmadmin)
[oracle@ldap-dj bin]$
[oracle@ldap-dj bin]$ dsccreg list-servers -h 3998
Enter DSCC administrator's password:
Failed to connect to ldap://3998:3998
3998:3998
[oracle@ldap-dj bin]$ dsccreg add-server -h localhost -p 3998 /u01/dsee7/var/local/dsInst/
Enter DSCC administrator's password:
/u01/dsee7/var/local/dsInst/ is an instance of DS
Enter password of "cn=Directory Manager" for /u01/dsee7/var/local/dsInst/:
This operation will restart /u01/dsee7/var/local/dsInst/.
Do you want to continue ? (y/n) y
Connecting to /u01/dsee7/var/local/dsInst (using ldap://127.0.0.1:1389)
Enabling DSCC access to /u01/dsee7/var/local/dsInst
Restarting /u01/dsee7/var/local/dsInst
Registering /u01/dsee7/var/local/dsInst in DSCC on localhost.
[oracle@ldap-dj bin]$ dsccreg list-servers -h 3998
Enter DSCC administrator's password:
Failed to connect to ldap://3998:3998
3998:3998
[oracle@ldap-dj bin]$
[oracle@ldap-dj bin]$
[oracle@ldap-dj bin]$ cacaoadm status
default instance is DISABLED at system startup.
default instance is not running.
[oracle@ldap-dj bin]$
[oracle@ldap-dj bin]$ cacaoadm enable
This action cannot be performed by a non privileged user.
[oracle@ldap-dj bin]$
[oracle@ldap-dj bin]$ cacaoadm start
[oracle@ldap-dj bin]$ cacaoadm status
default instance is DISABLED at system startup.
Current retries count : 3/4
Processes:
16433
Daemon is running but not available. Try again as it might be starting.
[oracle@ldap-dj bin]$

As you can see, the ODSEE cacao instance is running on custom port 21162, while the DSCC tries to contact it on port 11162... which is not available.
also, the error you have here:
[oracle@ldap-dj bin]$ dsccreg list-servers -h 3998
Enter DSCC administrator's password:
Failed to connect to ldap://3998:3998
3998:3998
[oracle@ldap-dj bin]$
is pretty trivial: you're trying to connect to a host (-h parameter) called 3998 ... which I guess is not correct; try -h ldap-dj instead

BUG: registered servers missing when password contains non-alphanumeric

I have a fresh installation of DS7 using Sun Java Web Server 7 to host DSCC7. Using DSCC7 web interface I click New Server and the procedure appears to complete successfully (no errors during creation, registration successful). However in the web interface the new server is not listed.
From the command line the new server is listed.
$ /opt/SUNWdsee7/bin/dsccreg list-servers
Hostname Port sPort Type Owner Flags iPath Description
www-c-directory 389 636 DS nobody /var/opt/SUNWdsee7/internal
Cause: the DSCC administrator's password contained non-alphanumeric characters (e.g. a left-angle bracket plus a few other punctuation characters) with about 10 characters in total.
Solution: from the web interface I navigated to Settings, Directory Service Managers, and changed the password for "admin" to a simpler password containing only alphanumeric characters.
Resolution: the registered servers now appear in the DSCC7 web interface as well as the command line. Oddly I can now return the password back to its original value and the servers still appear in the web interface.
Edited by: nhand42 on Jan 10, 2010 4:53 PM

English / C 7-bit ASCII.
The software has been installed inside a Whole Container, and the container was manually sysidcfg'd after the zone's installation (before the software installation) using zlogin -C.
Edited by: nhand42 on Jan 11, 2010 2:31 PM

DSCC: application error - unknown error (NPE)

HI,
just trying to test DSEE 7. However, as soon as I have setup the DS, almost every task in the DSCC web app gets an unknown application error (as long as DS was not active everything was fine - empty).
Actually I don't know, what should be wrong: 'bin/dsadm info' and 'bin/dsccsetup status' look ok, connecting to the ldap servers with Apache Directory Studio (ports 389 and 3998) is also ok.
So webapp bug or did I something wrong?
Here is my proto install sheet, i.e. what I did:
# http://docs.sun.com/app/docs/doc/820-4807/install-dsee?a=view
setenv SRCDIR /local/scratch/downloads/sun
setenv LC_CTYPE en_US.ISO8859-15
# for testing we put the admin GUI stuff on the server as well
setenv adminhost localhost
setenv serverhost localhost
# + is actually a link to /usr/bin/pfexec (for lazy admins and tribute to
#   Tom Pritlove's root tool aka + ;-))
# DS EE 7 software "installieren" - ca. 300M
mkdir /var/tmp/x ; cd /var/tmp/x
gtar xzf $SRCDIR/DSEE/DSEE.7.0.Solaris10-X86-zip.tar.gz
+ mkdir /opt/dsee7 ; + chown dsadm:staff /opt/dsee7
unzip -qq DSEE_ZIP_Distribution/sun-dsee7.zip -d /opt
cp -p DSEE_ZIP_Distribution/idsktune /opt/dsee7/bin/
cd /opt/dsee7/
rm -rf /var/tmp/x
# no need for an old JRE - ca. 134M
rm -rf jre
ln -s /usr/jdk/instances/jdk1.6.0/jre
# system tuning - should be run in the global zone and adjustments made
+ bin/idsktune >/var/tmp/dsee7-tuning-tips.txt
# optional: DS ControlCenter (DSCC) setup
# create var/dscc7.war file to be deployed later on the WebAppServer@$adminhost
bin/dsccsetup war-file-create
# configure Common Agent Container (cacao) for and register DSCC Agent
# DEFAULT: $serverhost:11162
bin/dsccsetup cacao-reg
# Create DSCC registry (DS instance for DSCC to store config data)
# NOTE: password must have at least 8 characters, otherwise:
#       /opt/dsee7/bin/dsadm exited with unexpected error code 11
# DEFAULT: $serverhost:3998 (ldap) , $serverhost:3999 (ldaps), DN suffix:cn=dscc
bin/dsccsetup ads-create
# check status (whether DSCC has been registered with cacao)
bin/dsccsetup status
    # Install Glassfish v3 (GF) or Sun GlassFish Enterprise Server (GF-ES),
    # on your $adminhost, if not already done (GFv2 and Sun Java System
    # Application Server (SJSAS) 9.x should be ok as well):
    + mkdir /opt/glassfishv3 ; + chown dsadm:staff /opt/glassfishv3
    # for reproduceable result we use no GUI but an answer file
    cat>/tmp/answer<<EOF
        License.license.ACCEPT_LICENSE=0
        InstallHome.directory.INSTALL_HOME=/opt/glassfishv3
        glassfish.Administration.HTTP_PORT=8080
        glassfish.Administration.ADMIN_PORT=4848
        glassfish.Administration.ADMIN_USER=admin
        glassfish.Administration.ADMIN_PASSWORD=12345678
        updatetool.Configuration.ALLOW_UPDATE_CHECK=true
        updatetool.Configuration.BOOTSTRAP_UPDATETOOL=true
        JDKSelection.directory.JDK_TYPED_IN_CHOICE=true
        JDKSelection.directory.JDK_TYPE_IN=/usr/jdk/instances/jdk1.6.0
EOF
    # adjust /tmp/answer for your needs (e.g. password), than
    sh $SRCDIR/GF-ESv3/sges-v3-unix.sh -s -a /tmp/answer
    rm /tmp/answer
    # create an app server instance if you have none yet or want a separate one
    + mkdir -p /var/data/glassfishv3 ; + chown dsadm:staff /var/data/glassfishv3
    /opt/glassfishv3/bin/asadmin create-domain \
        --domaindir /var/data/glassfishv3 \
        --portbase 9000 --user admin dscc7
    cat>>/var/data/glassfishv3/dscc7/config/server.policy<<EOF
// Permissions for Directory Service Control Center (DSCC 7)
grant codeBase
    "file:\${com.sun.aas.instanceRoot}/applications/j2ee-modules/dscc7/-"
    permission java.security.AllPermission;
EOF
    # start the app server
    /opt/glassfishv3/bin/asadmin start-domain \
        --domaindir /var/data/glassfishv3 \
        --user admin dscc7
    # login to the admin web console and register your AppServer
    http://$adminhost:9048/
    # deploy the dscc web app archive via web console or hotdeploy and check
    cp var/dscc7.war /var/data/glassfishv3/dscc7/autodeploy/
    http://$adminhost:9080/dscc7
# DS setup on $serverhost
+ mkdir -p /var/data/ds ; + chown dsadm:staff /var/data/ds
bin/dsadm create -p 389 -P 636 /var/data/ds/dsee7
    # dsadm's priviliges default to 'basic'
+ ppriv -s EI+net_privaddr bin/dsadm start /var/data/ds/dsee7
bin/dsadm info --all --separator = /var/data/ds/dsee7
    # create an empty prefix - as defined above - e.g. 12345678
bin/dsconf create-suffix -p 389 -e dc=example,dc=com
    # register server instance with DSCC web app on dscc-host=localhost and
    # dscc-registry-port=3998 (see 'bin/dsccsetup status')
bin/dsccreg add-server -h $serverhost -p 3998 /var/data/ds/dsee7
# NOTE: To see it immediately in the DSCC, one may need to restart the
#       DSCC web app instance on the $adminhost
# Check with eclipse Apache LDAP-Browser plugin
# update-site to add in eclipse: http://directory.apache.org/studio/update/1.x/
Menu: Window | Open Perspective | Other | LDAP
# DS
Connection Tab: New Connection
        Network-Parameters:
            Connection Name: DSEE 7
            Hostname: $servername
            Port: 389
            Encryption Method: none
        Authentification:
            Authentification Method: simple authentication
            Bind DN or User: cn=Directory Manager
            Bind Password: 12345678
# DS Registry
Connection Tab: New Connection
        Network-Parameters:
            Connection Name: DSEE 7 Registry
            Hostname: $servername
            Port: 3998
            Encryption Method: none
        Authentification:
            Authentification Method: simple authentication
            Bind DN or User: cn=Directory Manager
            Bind Password: 12345678Exception for the 'Directory Server' tab e.g.
java.lang.NullPointerException
     com.sun.web.admin.directory.dcc.GlobalViewBean.getServerGroups(GlobalViewBean.java:543)
     com.sun.web.admin.directory.dcc.ServersViewBean.createTableFilters(ServersViewBean.java:297)
     com.sun.web.admin.directory.dcc.DirectoryServersViewBean.createTableModel(DirectoryServersViewBean.java:120)
     com.sun.web.admin.directory.dcc.DirectoryServersViewBean.getTableModel(DirectoryServersViewBean.java:99)
     com.sun.web.admin.directory.dcc.GlobalViewBean.registerChildren(GlobalViewBean.java:289)
     com.sun.web.admin.directory.dcc.ServersViewBean.registerChildren(ServersViewBean.java:341)
     com.sun.web.admin.directory.dcc.GlobalViewBean.(GlobalViewBean.java:128)
     com.sun.web.admin.directory.dcc.ServersViewBean.(ServersViewBean.java:42)
...Any ideas?
Thanx,
jel.

Thanks for the answears and good Monday.
No, the problem is still here. Today in the Event Viewer there's another error immediately after the original:
Type event:
Error
Source:
Application Error
Category:
Nessuno
ID event:
1001
Date:
28/09/2012
Time:
14.54.18
User:
N/D
Computer:
WKSXXX
Description:
Bucket -1548073178 errato.For further information, ....
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 42 75 63 6b 65 74 3a 20   Bucket:
0008: 2d 31 35 34 38 30 37 33   -1548073
0010: 31 37 38 0d 0a            178..
@Bill Hunt I checked the Event viewer System Tab and the only errors are when power on the PC:
1. Adfs service can't start:Impossible find the specified file.This I don't know what it is.
2. Google Update service can't start: Impossible find the specified file. I removed the software.
Warnings:
1.Event: 20 Source: Print Description:The driver of a network printer (HP LJ P3005)for Windows NT x86 Version-3 was add or updated.
2. Event: 4226 Source: Tcpip Description:TCP/IP has reached the security limit imposed on the number of concurrent (incomplete) TCP connect attempts.
In the Application Tab there's no warnings or errors.
Any other ideas?

Help DSCC agent not communicating with AppServer or Tomcat?!

Installing Directory Server Enterprise Edition 6.3 From Zip Distribution on system running Solaris10 11/08.
Cannot get DSCC to work with either AppServer or Tomcat.
Both AppServer & Tomcat deploy DSEE WAR file and I can look at things that I have manually registered via command line. Cacao agent is running it is just not communicating with AppServer or Tomcat so it cannot commit any actions such as starting and stopping directory instances or creating new directories instances within the web app.
Is this a bug that occurs only when doing a new install using the Zip Distribution?
The Error message I get regardless if Appserver or Tomcat is:
"Could not contact the DSCC agent on <server>. Use the command cacaoadm to check that the DSCC agent is installed and running on port 11169."
I changed to port 11169 because it had a conflict on default port 11162.
Output from cacaoadm & dsccsetup commands is follows:
root@dsee:/ $ /local/dsee6/cacao_2/usr/lib/cacao/bin/cacaoadm status
default instance is DISABLED at system startup.
Smf monitoring process:
8423
8424
Uptime: 0 day(s), 0:47
root@dsee:/ $ /local/dsee6/cacao_2/usr/lib/cacao/bin/cacaoadm list-params
snmp-adaptor-port=11161
snmp-adaptor-trap-port=11162
jmxmp-connector-port=11169
commandstream-adaptor-port=11163
rmi-registry-port=11164
secure-webserver-port=11165
java-flags=-Xms4M -Xmx128M -Dcom.sun.management.jmxremote -Dfile.encoding=utf-8
java-home=/local/jre
jdmk-home=/local/dsee6/private
nss-lib-home=/local/dsee6/private/lib
nss-tools-home=/local/dsee6/bin
retries=4
enable-instrumentation=false
network-bind-address=0.0.0.0
root@dsee:/ $ /local/dscc6/bin/dsccsetup status -v
## /local/webconsole/usr/sbin/smreg/smreg is MISSING
## /local/webconsole/usr/sbin/smcwebserver/smcwebserver is MISSING
## /local/dscc6/dccapp is present
Sun Java (TM) Web Console is not installed
## /local/dsee6/cacao_2/usr/lib/cacao/bin/cacaoadm is present
## /local/dsee6/cacao_2/.configured is present
## /local/dscc6/lib/jar/nquickmodule.jar is present
## Running /local/dsee6/cacao_2/usr/lib/cacao/bin/cacaoadm list-modules -r
DSCC Agent is registered in Cacao
## Running /local/dsee6/cacao_2/usr/lib/cacao/bin/cacaoadm status
## Running /local/dsee6/cacao_2/usr/lib/cacao/bin/cacaoadm list-modules
## Running /local/dsee6/cacao_2/usr/lib/cacao/bin/cacaoadm get-param network-bind-address
## Running /local/dsee6/cacao_2/usr/lib/cacao/bin/cacaoadm get-param jmxmp-connector-port
Cacao uses a custom port number (11169)
## /local/ds6/bin/dsadm is present
DSCC Registry has been created
Path of DSCC registry is /local/var/dscc6/dcc/ads
Port of DSCC registry is 3998
Any work around or ideas on how to get DSCC working?
Thanks!

I started over and installed Glassfish and everything just worked. After the fact I think the real problem was related to the server.policy file. I think this was the problem because using the default appserver 8.2 that comes with Solaris has a different path and I got this same error when tried using tomcat also. When installing glassfish it uses this default path as in the server.policy example as follows so it just worked.
Add the following lines in the {install-dir}/domains/domain1/config/server.policy file
// Permissions for Directory Service Control Center
grant codeBase "file:${com.sun.aas.instanceRoot}/applications/j2ee-modules/DSCC/-"
permission java.security.AllPermission;
Hope this helps some as I was really stuck and confused at the time and just started playing with the stuff. Growing pains. Thanks to those that replied.
Thanks!
Wences

ODSEE 11gR1: DS server instances displayed twice in DSCC console

I recently migrated some DSEE 6.x DS instances to ODSEE 11gR1 (dsconf : 11.1.1.5.0 B2011.0517.2145) on RHEL 5.7 x64 .
When running "./dsccreg list-servers -aC" on the DSCC host, I can see all my ODSEE instances.
However, in the DSCC console, some instances appear twice, in the "Directory Servers" -> "Servers" sub-tab, and some others appear
only once, normally.
For the instances appearing twice, I have the following in the "Server" column:
server shortname:389 (server not registered)
server FQDN:389
I'd like to know how to remove the "server not registered" lines. I don't know how does DSCC build this server list, but I've checked it's
not defined under th cn=dscc tree.
The problem with that wrong display, is that for example in the replication agreements tab, some replication agreements are displayed twice too,
which is confusing.
DSCC runs in a Tomcat 6.0.35 container, and my java version is as follows:
java version "1.6.0_20"
OpenJDK Runtime Environment (IcedTea6 1.9.10) (rhel-1.23.1.9.10.el5_7-x86_64)
OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode)
Any idea ?

I did what you suggested. Both commands worked fine and produced no errors but the problem remains in the DSCC GUI.
When running ./dsccreg list-servers, it still works fine, I see all servers only once.
Also, I noticed that if I look at the GUI between the remove-server and the add-server command, each server appears
twice with the following comment between brackets: (server not registered).
After registering the server again, one the "(server not registered)" comment 's been removed but the other instance
with the comment remains.
So, the remove-server command doesn't prevent an instance from being displayed in the DSCC GUI. This is what I'd like.

DSCC Registry Not Running

Glad to see u all back again
Im trying to open GUI cosnole of LDAP 6.3. It is asking me to DSCC registry but when i have done that its giving below error.(I have logged in as a root in the browser)
starting DSCC Registry. Logs:++
Warning: instance '/var/opt/SUNWdsee/dscc6/dcc/ads' is registered in SMF.
Only root can run this command Only root can run this command Starting DSCC Registry. Logs:
Warning: instance '/var/opt/SUNWdsee/dscc6/dcc/ads' is registered in SMF.
And below is the output of DSCC status (may be it will help u to find the cause)
bash-3.00# ./dsccsetup status
DSCC Application is registered in Sun Java (TM) Web Console
DSCC Agent is registered in Cacao
DSCC Registry has been created
Path of DSCC registry is /var/opt/SUNWdsee/dscc6/dcc/ads
Port of DSCC registry is 3998
DSCC registry is not running. You may start it using:
/opt/SUNWdsee/ds6/bin/dsadm start /var/opt/SUNWdsee/dscc6/dcc/ads
Thanks for look into it :P

Thanks vamshi for yur reply
It is saying that its already started. Its is production env..I took some extreme step that i have run the dsccsetup demantle and initialize commands which i never run before. Oops. And now i there are no errors coming up but I have lost all the server configured info. So i registered existing each and every server. But for couple of servers its giving error in console while im trying register as
couldnt connect DSCC agent on abc.com server and when i checked cacaodm agent ..its running fine..pls give me where else i can dig more on this
Thanks again vamshi

Server 'location' attribute in DSCC

Is it possible to set the 'location' attribute for servers registered in DSCC via any command line tools (apart from using e.g. ldapmodify) or only via DSCC GUI?

POVAlias function used

DSCC problem on Directory Server enterprise edition Version 11.1.1.7.0

I install ldap version Version 11.1.1.7.0 on redhat 5.6 on /opt/dsee7
I excute:
I have export JAVA_HOME=/opt/dsee7/jre and PATH=$JAVA_HOME/bin:/opt/dsee7/bin:/opt/dsee7/dsrk/bin:$PATH
*[root@sperem ~]# java -version*
java version "1.7.0_10"
Java(TM) SE Runtime Environment (build 1.7.0_10-b18)
Java HotSpot(TM) Server VM (build 23.6-b04, mixed mode)
*[root@sperem ~]# which java*
*/opt/dsee7/jre/bin/java*
*[root@sperem ~]# dsccsetup ads-create*
*[root@sperem ~]# dsccsetup war-file-create*
*[root@sperem ~]# dsccagent create*
*[root@sperem ~]# dsccreg add-agent /opt/dsee7/var/dcc/agent/*
*[root@sperem ~]# dsccagent start*
I deploy the dscc7.war on glassfish.
asadmin deploy /opt/dsee7/var/dscc7.war
All work correctly.
I have create one ldap istanza and i have register to dscc console with commands
*[root@sperem lib]# dsadm create -p 389 -P 636 /opt/dsee7/var/utenti*
Choose the Directory Manager password:
Confirm the Directory Manager password:
Use command 'dsadm start '/opt/dsee7/var/utenti'' to start the instance
*[root@sperem lib]# dsadm start /opt/dsee7/var/utenti*
Directory Server instance '/opt/dsee7/var/utenti' started: pid=9762
*[root@sperem lib]# dsccreg add-server /opt/dsee7/var/utenti/*
Enter DSCC administrator's password:
*/opt/dsee7/var/utenti/ is an instance of DS*
Agent No Hostname Port Owner iPath
*0 sperem.gromanenghi.net 3997 root /opt/dsee7/var/dcc/agent/*
The registration will use DSCC agent on port: 3997
Enter password of "cn=Directory Manager" for /opt/dsee7/var/utenti/:
This operation will restart /opt/dsee7/var/utenti/.
Do you want to continue ? (y/n) y
Connecting to /opt/dsee7/var/utenti (using ldap://127.0.0.1:389)
Enabling DSCC access to /opt/dsee7/var/utenti
Restarting /opt/dsee7/var/utenti
Registering /opt/dsee7/var/utenti in DSCC on localhost.
The problem is:
When i use the dscc web console i can't administer my ldap because i receive the message:
Inaccessible (to enable access click on the server and then on ‘Enable Access’)
*[root@sperem lib]# ps -ef | grep dscc*
root 5452 1 0 09:39 ? 00:00:03 /opt/dsee7/jre/bin/java -Dsun.directory.clip.arg0=/opt/dsee7/lib/dsccagentdaemon -classpath /opt/dsee7/lib/jar/utils.jar:/opt/dsee7/lib/jar/dsccagentdaemon.jar:/opt/dsee7/lib/jar/dcc.jar:/opt/dsee7/lib/jar/ground.jar:/opt/dsee7/lib/jar/clip.jar:/opt/dsee7/lib/jar/common.jar:/opt/dsee7/lib/private/jdmkrt.jar:/opt/dsee7/lib/private/jmxremote_optional.jar -Ddirectory.utils.lib.path=/opt/dsee7/lib/libjutils.so oracle.ldap.dsee.dscc.agent.DsccAgentMain start /opt/dsee7/var/dcc/agent
I try to create one new ldap istance from web dscc but i have the same problem. I try to register the ldap instance directly from dscc but i have the same problem
With other ldap version I don't have problem.
TIA
Giovanni
P.S. Excuse me for my english.

We have found DSCC in 11.1.1.7.0 is much more sensitive to SSL cert issues. Make sure your Directory Server SSL certificates are set up correctly and then remove from DSCC and add again. Then click the "refresh" button in DSCC. You may also want to double-check your dsccagent installation and make sure it is properly registered.

Registering ds 5.2 on dscc

Similar Messages

Maybe you are looking for