Putting Admin Server to use

Hi all,
          We are planning to use a WL Proxy for teh cluster and I was wondering if I
          could use the Admin server for that ...
          Also how intensive in terms of memory and CPU usage is the Admin server's
          job (in a cluster of 2 managed servers).
          Also does BEA have any take on that ?
          Any help would be appreciated,
          _NR

It's not a recommended practise to use Admin server other than
          configuration & deployment purposes. Regarding the memory and cpu usage,
          it depends on the deployments and tools used to gather runtime statistics
          Otherwise the footprint should be pretty much in the range of 64mb.
          For testing purposes it's ok to use admin server as proxy server but i
          wouldn't
          recommend the same for production.
          Kumar
          [email protected] wrote:
          > Hi all,
          > We are planning to use a WL Proxy for teh cluster and I was wondering if I
          > could use the Admin server for that ...
          > Also how intensive in terms of memory and CPU usage is the Admin server's
          > job (in a cluster of 2 managed servers).
          > Also does BEA have any take on that ?
          >
          > Any help would be appreciated,
          > _NR

Similar Messages

Unable to start Admin server by using weblogic.admin utility

Hi,
I stoped the admin server by using weblogic.admin utility command as bellow.
java weblogic.Admin -url http://server1:8008 -username adminuser -password weblogic SHUTDOWN myserver
It stopped successfully. But while starting as below i am getting error. Kindly help me out.
java weblogic.Admin -url http://172.27.72.70:8008 -username adminuser -password weblogic START myserver
<Warning> <Net> <BEA-000905> <Could not open connection with host: server1 and port: 8008.>
Failed to connect to http://172.27.72.70:8008: Destination unreachable; nested exception is:
java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: 'star', port: '8008'; No available router to destination
Any suggestion is appreciated.
Thanks,

Hi,
Thanks for your reply.
Yes, Node Manager has configured on Managed Server's host machine.
So can't we start admin server by using weblogic.admin utility if admin server is stopped?
Thanks,

Admin Server Location

Hi
          I have a cluster of n managed servers across m physical boxes. I am thinking about having the admin server on another separate physical server to increase robustness in a failure situation. This is particularly needed as I have cluster wide distrubuted JMS destinations. Does anyone know of any reasons why I should/should not do this.
          Thanks
          Matt

While it is reasonable to have your admin server on a seperate box you may end up wasting resources if you don't deploy managed servers on the admin server box, if there is enough spare resource on the admin server box then I suggest using that space to deploy more managed servers.
          Managed servers can run even when the admin server is down so putting your admin server on it's own seperate box for that reason alone, is not justifiable IMHO :)
          However one thing I do suggest is seperating network resources used for administration of your cluster from the workload of your cluster. We are currently performance tuning a cluster and becuase the Admin server is using the same network resources as the cluster the admin console becomes alomst unusable under heavy load.
          Hoos

CA-signed certificate for admin server

hi,
how can i make the admin-server use a CA signed certificate instead of self-signed? i only see an option to renew the self-signed certificates.

okay, this is the method i used:
webserver$ cd /var/opt/SUNWwbsvr7/admin-server/config
# Save the CA certificate in cacert.crt, and import it into the database:
webserver$ certutil -d . -A -n Example-Inc-CA -t CTu -a -i cacert.crt
# Generate a new CSR on stdout:
webserver$ certutil -R -d . -s 'CN=ws.example.org,O=Example, Inc.' -a -g 2048 -k rsa
# Sign the CSR and save the certificate to 'newcert.crt', then import it:
webserver$ certutil -d . -A -n cert-ws.example.org -t u -a -i newcert.cert
webserver$ vi server.xml
# Look for <server-cert-nickname>, and change it from 'Admin-Server-Cert' (the default)
# to 'cert-ws.example.org'.
webserver$ ../bin/stopserv
webserver$ ../bin/startservreplace 'ws.example.org' with the hostname the admin server runs on.
this seemed to work for me; after the restart, the admin server was using the new certificate, and the browser accepted it.

Setting up an admin server (win) + a managed server (linux)

I am trying to set up the following domain on weblogic 8.1 SP2:
1. An administration server (+workshop) on my local Windows box
2. A managed server running on a red hat enterprise box, that connects to the
administration server on my windows box.
I've not been able to find any documentation on this, and the installation process
is far from intuitive.
Can someone help me with a step-by-step guide? I'm not trying to do anything fancy
here ;-) Thanks!

Resolution found:
Went through the config.xml file. Found that in the server tag the listen address
for the server and managed server is not there. Entered the Corresponding listen
address for both Admin and Managed server
"Henrik Pettersen" <[email protected]> wrote:
>
>
>
Thank you for the information. Just what I needed. But I am now encountering
another
problem when I try to startManagedWebLogic:
<03-Jun-2004 16:48:03 o'clock BST> <Info> <Configuration Management>
<BEA-150015>
<Connecting to the administration server http://banana:7001 to retrieve
the initial
configuration.>
<03-Jun-2004 16:48:06 o'clock BST> <Notice> <Log Management> <BEA-170019>
<The
server log file /usr/local/bea/user_projects/domains/domain/managed/managed.log
is opened. All server side log events will be written to this file.>
<03-Jun-2004 16:48:06 o'clock BST> <Emergency> <Configuration Management>
<BEA-150011>
<There was an attempt to start a managed server ( null:7001 ) using the
same address
as the admin server ( banana:7001 ).>
<03-Jun-2004 16:48:06 o'clock BST> <Emergency> <WebLogicServer> <BEA-000342>
<Unable
to initialize the server: weblogic.management.configuration.ConfigurationException:
[Configuration Management:150011]There was an attempt to start a managed
server
( null:7001 ) using the same address as the admin server ( banana:7001
).>
The WebLogic Server did not start up properly.
Exception raised: 'weblogic.management.configuration.ConfigurationException:
[Configuration
Management:150011]There was an attempt to start a managed server ( null:7001
using the same address as the admin server ( banana:7001 ).'
Reason: weblogic.management.configuration.ConfigurationException: [Configuration
Management:150011]There was an attempt to start a managed server ( null:7001
using the same address as the admin server ( banana:7001 ).
I am trying to run Weblogic 8.1 Portal Domain on Red Hat Enterprise 3.
The Linux config file is attached. Any clues would be most appreciated.
Thank you for your help.
Henrik
"Michael Zanchelli" <[email protected]> wrote:
Involving multiple machines obviously adds some complexity but for a
development
environment that you describe, you'll want to use the ConfigurationWizard
to
create domains (with the same name) on both machines. On the admin server
machine,
use the Custom path in Config Wiz to add the managed server, and onthe
managed
server machine, you can use Express mode. Start the admin server, then
use startManagedWeblogic
on the managed server machine, specifying the managed server name and
admin url
as command line args.
In a production environment, you'll likely use node manager to start
managed servers
and a domain does not need to be created on the managed server machine
in that
case.
edocs has lots of good overview information and details on using Config
Wiz.
"Henrik" <[email protected]> wrote:
I am trying to set up the following domain on weblogic 8.1 SP2:
1. An administration server (+workshop) on my local Windows box
2. A managed server running on a red hat enterprise box, that connects
to the
administration server on my windows box.
I've not been able to find any documentation on this, and the installation
process
is far from intuitive.
Can someone help me with a step-by-step guide? I'm not trying to doanything
fancy
here ;-) Thanks!

10.3 Deploying same EAR on both admin server &managed :server jndi in use

Hypotehetical question but is it possible to deploy the same EAR file (some minor differneces) on both Admin server and not have an issue with jndi naming.
I get the follwoing error when deploying on the managed server and suspect it could be cached compiled ejb's as I have already had a failed deployment on this server so might need to clear the cache
Error I am getting is:
An error occurred during activation of changes, please see the log for details.
Exception preparing module: EJBModule(xxx_base_ejb.jar) Unable to deploy EJB: SessionAdministrationLogicEjb from xxx_base_ejb.jar: [EJB:011055]Error deploying the EJB 'SessionAdministrationLogicEjb(Application: RT_Samba, EJBComponent: norkom_base_ejb.jar)', the JNDI name 'ejb/xxx/remote/SessionAdministrationLogicEjb' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
Substituted for missing class [EJB - 11055]Error deploying the EJB 'SessionAdministrationLogicEjb(Application: RT_Samba, EJBComponent: xxx_base_ejb.jar)', the JNDI name 'ejb/xxx/remote/SessionAdministrationLogicEjb' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
Any input very much appreciated.

Hypotehetical question but is it possible to deploy the same EAR file (some minor differneces) on both Admin server and not have an issue with jndi naming.
I get the follwoing error when deploying on the managed server and suspect it could be cached compiled ejb's as I have already had a failed deployment on this server so might need to clear the cache
Error I am getting is:
An error occurred during activation of changes, please see the log for details.
Exception preparing module: EJBModule(xxx_base_ejb.jar) Unable to deploy EJB: SessionAdministrationLogicEjb from xxx_base_ejb.jar: [EJB:011055]Error deploying the EJB 'SessionAdministrationLogicEjb(Application: RT_Samba, EJBComponent: norkom_base_ejb.jar)', the JNDI name 'ejb/xxx/remote/SessionAdministrationLogicEjb' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
Substituted for missing class [EJB - 11055]Error deploying the EJB 'SessionAdministrationLogicEjb(Application: RT_Samba, EJBComponent: xxx_base_ejb.jar)', the JNDI name 'ejb/xxx/remote/SessionAdministrationLogicEjb' is already in use. You must set a different JNDI name in the weblogic-ejb-jar.xml deployment descriptor or corresponding annotation for this EJB before it can be deployed.
Any input very much appreciated.

Errors & warnings when using the Admin Server Console - Help Needed

hi,
i just installed weblogic 12c and created a new domain which contains an adminServer and managedServer under
one cluster.
after finishing the installation, i started the Admin Server and afterwards started the admin server console.
and i got the next warning and errors.
the warning look like this:
<20:00:35 IST 23/03/2012> <Warning> <Munger> <BEA-2156203> <A version attribute
was not found in element "web-app" in the deployment descriptor C:\Oracle\Middle
ware\user_projects\domains\base_domain\servers\AdminServer\tmp\_WL_internal\cons
oleapp\jxhze9\console-ext\sipserver-console-ext\WEB-INF\web.xml. A version attri
bute is required, but this version of the WebLogic Server will assume that the l
atest version is used. Future versions of WebLogic Server will reject descriptor
s that do not specify the Java EE version. To eliminate this warning, add an app
ropriate "version=" to element "web-app" in the deployment descriptor.>
the errors look like this:
<20:01:51 IST 23/03/2012> <Error> <netuix> <BEA-423158> <No content found at con
tentUri = /PortalConfig/security/providers/AuthenticatorConfigCommon.portlet.>
what is the problem? anyone knows?

If you want to have an weblogic environment with one domain having server spread across different physical machines , then you will have to perform the installations of the weblogic server separately on all the machines . Also make sure that the version of the Weblogic server you are installing is same across the machines and the directory structure is also exactly same.
In short you will have to perform the below steps :
1 : install the weblogic server on all the machines with exactly same version and same dir structure .
2 : Create domain on MachineA providing all the details of the Managed Server and different machine hostnames.
3 : Start the Admin Server on machineA and then shut down it.
4 : execute the WLST pack command on MachineA creating a domain template JAR file.
5 : copy the create jar file on all the Machines ( B , C , D ) you have to distribute your domain.
6 : Execute the WLST unpack command on all the machines ( B , C , D ) .
7 : Execute the WLST nmEnroll () command on all the machines ( B, C , D ).
8 : Start the Managed Servers on all the machines ( B , C , D )

Use Admin Server to Manage multiple managed servers through Nodemanager

hi guys,
Iam trying to simulate the production environment for a Weblogic based application.
I want to use one Admin Server(adminServer) to control 2 managed servers(weblogic,Bizarro).
adminServer & weblogic sit on windows machine (prod1) and Bizarro sits on OakStage(unix
machine).
I have nodeManagers running on both machines. They were started using the default
start scripts that were provided.
I can sucessfully start&stop instance weblogic (the instance that resides on the
same machine as adminServer). When I try to start Bizarro i get the following
error in the console
<Oct 18, 2002 7:59:22 AM PDT> <Error> <NodeManager> <Could not start server 'Bizarro'
via Node Manager - reason: '[SecureCommandInvoker: Could not create a socket to
the NodeManager running on host '192.168.0.97:5555' to execute command 'online
Bizarro', reason: Operation timed out: connect. Ensure that the NodeManager on
host '192.168.0.97' is configured to listen on port '5555' and that it is actively
listening]'>
but iam sure node manager is running on port 5555 on that box.
Here is my config.xml file. Is there something Iam missing?
I have also modified the hosts file to only have the ip address of the admin server.
<?xml version="1.0" encoding="UTF-8"?>

<Domain Name="adminDomain">
<Security Name="adminDomain" PasswordPolicy="wl_default_password_policy" Realm="wl_default_realm"/>
<PasswordPolicy Name="wl_default_password_policy"/>
<FileRealm Name="wl_default_file_realm"/>
<StartupClass ClassName="com.ias.hub.weblogic.WeblogicStartup" Name="hubStartup"
Targets="weblogic"/>
<CustomRealm ConfigurationData="user.filter=(&(uid=%u)(objectclass=person));user.dn=ou=people,
o=beasys.com;server.principal=uid=admin, ou=Administrators, ou=TopologyManagement,
o=NetscapeRoot;membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames));group.filter=(&(cn=%g)(objectclass=groupofuniquenames));server.host=ldapserver.example.com;group.dn=ou=groups,
o=beasys.com" Name="defaultLDAPRealmForNetscapeDirectoryServer" Notes="This is
provided as an example. Before enabling this Realm, you must edit the configuration
parameters as appropriate for your environment." Password="{3DES}CqUY0ZB2q6DOFOH3DpKGnQ=="
RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
<Server ListenPort="9000" Machine="Prod1" Name="weblogic" StdoutDebugEnabled="true"
StdoutSeverityLevel="64">
<ServerStart ClassPath="my correct claspath" Name="weblogic" OutputFile="weblogic.log"/>
<SSL ListenPort="9001" Name="weblogic"/>
<ServerDebug Name="weblogic"/>
<KernelDebug Name="weblogic"/>
<Log FileName="weblogic.log" Name="weblogic"/>
<ExecuteQueue Name="default" ThreadCount="15"/>
<WebServer LogFileName="./config/adminDomain/logs/access.log" LoggingEnabled="true"
Name="weblogic"/>
</Server>
<JDBCConnectionPool CapacityIncrement="2" DriverName="weblogic.jdbc.oci.Driver"
InitialCapacity="15" LoginDelaySeconds="1" MaxCapacity="15" Name="IasPool" Properties="user=stage2;password=******;server=ORCL_STAGE.INTERASSET.COM"
RefreshMinutes="25" Targets="weblogic" TestTableName="DUAL" URL="jdbc:weblogic
racle"/>
<SNMPAgent Name="adminDomain"/>
<Application Deployed="true" Name="certificate" Path=".\config\adminDomain\applications">
<WebAppComponent Name="certificate" Targets="adminServer" URI="certificate.war"/>
</Application>
<JDBCDataSource JNDIName="IAS_DATA_SOURCE" Name="IasDataSource" PoolName="IasPool"
Targets="weblogic"/>
<Application Deployed="true" Name="DefaultWebApp" Path=".\config\adminDomain\applications">
<WebAppComponent Name="DefaultWebApp" Targets="adminServer" URI="DefaultWebApp"/>
</Application>
<CustomRealm ConfigurationData="user.filter=(&(uid=%u)(objectclass=person));user.dn=ou=people,
dc=example, dc=com;server.principal=cn=Manager, dc=example, dc=com;membership.filter=(&(uniquemember=%M)(objectclass=groupofuniquenames));group.filter=(&(cn=%g)(objectclass=groupofuniquenames));server.host=ldapserver.example.com;group.dn=ou=groups,
dc=example, c=com" Name="defaultLDAPRealmForOpenLDAPDirectoryServices" Notes="This
is provided as an example. Before enabling this Realm, you must edit the configuration
parameters as appropriate for your environment." Password="{3DES}CqUY0ZB2q6DOFOH3DpKGnQ=="
RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
<Machine Name="Prod1">
<NodeManager Name="Prod1"/>
</Machine>
<Application Deployed="true" Name="entity" Path=".\config\adminDomain\applications">
<EJBComponent Name="entity" Targets="weblogic" URI="entity.jar"/>
</Application>
<Application Deployed="true" Name="hub" Path=".\config\adminDomain\applications">
<WebAppComponent Name="hub" Targets="weblogic" URI="hub"/>
</Application>
<Server ListenAddress="192.168.0.97" ListenPort="7000" Machine="OakStage" Name="Bizarro">
<ServerStart ClassPath="my correct classpath" Name="Bizarro" OutputFile="bizarro.log"/>
<SSL Name="Bizarro"/>
<ServerDebug Name="Bizarro"/>
<KernelDebug Name="Bizarro"/>
<Log Name="Bizarro"/>
<WebServer Name="Bizarro"/>
</Server>
<Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
<ApplicationManager Name="adminDomain"/>
<CustomRealm ConfigurationData="server.host=ldapserver.example.com;membership.scope.depth=1;microsoft.membership.scope=sub;membership.filter=(|(&(memberobject=%M)(objectclass=memberof))(&(groupobject=%M)(objectclass=groupmemberof)));group.dn=ou=Groups,
o=ExampleMembershipDir;group.filter=(&(cn=%g)(objectclass=mgroup));server.principal=cn=Administrator,
ou=Members, o=ExampleMembershipDir;user.dn=ou=Members, o=ExampleMembershipDir;user.filter=(&(cn=%u)(objectclass=member))"
Name="defaultLDAPRealmForMicrosoftSiteServer" Notes="This is provided as an example.
Before enabling this Realm, you must edit the configuration parameters as appropriate
for your environment." Password="{3DES}CqUY0ZB2q6DOFOH3DpKGnQ==" RealmClassName="weblogic.security.ldaprealmv2.LDAPRealm"/>
<JTA Name="adminDomain"/>
<Server ListenPort="7000" Name="adminServer" NativeIOEnabled="true" TransactionLogFilePrefix="config/adminDomain/logs/">
<ServerStart Name="adminServer"/>
<Log FileName="config/adminDomain/logs/weblogic.log" Name="adminServer"/>
<ServerDebug Name="adminServer"/>
<ExecuteQueue Name="default" ThreadCount="15"/>
<KernelDebug Name="adminServer"/>
<WebServer DefaultWebApp="DefaultWebApp" LogFileName="./config/adminDomain/logs/access.log"
LoggingEnabled="true" Name="adminServer"/>
<SSL Enabled="true" ListenPort="7005" Name="adminServer" ServerCertificateChainFileName="config/adminDomain/ca.pem"
ServerCertificateFileName="config/adminDomain/democert.pem" ServerKeyFileName="config/adminDomain/demokey.pem"/>
</Server>
<UnixMachine Name="OakStage">
<NodeManager ListenAddress="192.168.0.97" Name="OakStage"/>
</UnixMachine>
<Log FileName="adminDomain.log" Name="adminDomain"/>
</Domain>
Thanks guys
regards
syd

Can this be done when you set up your domain along with admin and managed servers the very first time ? Even if you set up a domain with bunch of managed servers why does the library still get installed on admin server??? Also, for the method you described dont we have to update targets for statup and shutdown classes and work managers?
Also, what is the other method to do it from the console?
METHOD 2 (Other than the one you described- Please tell me if this is correct method and if we need to go to till level)
Step1:
I went to deployments base_domain (in admin console) > deployments chose each library and changed targets manually and activate the changes
Step2
Go to Startup and shutdown classes and change targets there
Step 3
Go to work managers and change targets there.
Please let me know
Edited by: user9021545 on May 12, 2011 10:18 AM

Errors while starting admin server using WLST and NodeManager

Hi I am trying to start admin server using WLST and NodeManager. I started nodemanager and WLST successfully. but when I am trying to nmConnect() command I am getting below errors. Please any one tell me where am I going wrong? I copied dumpStack() optput as well..
thanks
manohar
C:\oracle\Middleware\wlserver_10.3\server\bin>
C:\oracle\Middleware\wlserver_10.3\server\bin>java weblogic.WLST
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/offline> nmConnect('weblogic','weblogic','localhost','5556')
Connecting to Node Manager ...
<May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
sted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O
=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificat
e list raised a certificate parsing exception PKIX: Unsupported OID in the Algor
ithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
sted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O
=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificat
e list raised a certificate parsing exception PKIX: Unsupported OID in the Algor
ithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
sted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The
loading of the trusted certificate list raised a certificate parsing exception
PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
sted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.
\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate p
arsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.84
0.113549.1.1.11.>
<May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
sted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading
of the trusted certificate list raised a certificate parsing exception PKIX: Un
supported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 646, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node
Manager. : I/O error while reading domain directory
Use dumpStack() to view the full stacktrace
wls:/offline>
wls:/offline>
wls:/offline>
wls:/offline>
wls:/offline>
wls:/offline>
wls:/offline> dumpStack()
This Exception occurred at Tue May 03 10:45:03 EDT 2011.
weblogic.nodemanager.NMException: I/O error while reading domain directory
at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClie
nt.java:299)
at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClie
nt.java:312)
at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.jav
a:248)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerCli
ent.java:199)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerCli
ent.java:205)
at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.
java:52)
at weblogic.management.scripting.NodeManagerService.verifyConnection(Nod
eManagerService.java:179)
at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManage
rService.java:173)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyMethod.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyObject.invoke(Unknown Source)
at org.python.pycode._pyx2.nmConnect$3(<iostream>:118)
at org.python.pycode._pyx2.call_function(<iostream>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyFunction.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.pycode._pyx16.f$0(<console>:1)
at org.python.pycode._pyx16.call_function(<console>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyCode.call(Unknown Source)
at org.python.core.Py.runCode(Unknown Source)
at org.python.core.Py.exec(Unknown Source)
at org.python.util.PythonInterpreter.exec(Unknown Source)
at org.python.util.InteractiveInterpreter.runcode(Unknown Source)
at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
at weblogic.management.scripting.WLST.main(WLST.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.WLST.main(WLST.java:29)
weblogic.nodemanager.NMException: I/O error while reading domain directory
wls:/offline>
wls:/offline>

Hi manohar,
Please try the following article... (With Node Manager Communication type as "Plain" because it looks like you are getting PKIX security certificate chain message ) Just to isolate the issue
Topic: Start AdminServer And NodeManager Using WLST
http://middlewaremagic.com/weblogic/?p=6580
Thanks
Ravish Mody

Starting admin server using WLST and NodeManager

Hi I am trying to start admin server using WLST and NodeManager. I started nodemanager and WLST successfully. but when I am trying to nmConnect() command I am getting below errors. Please any one tell me where am I going wrong? I copied dumpStack() optput as well..
thanks
manohar
C:\oracle\Middleware\wlserver_10.3\server\bin>
C:\oracle\Middleware\wlserver_10.3\server\bin>java weblogic.WLST
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/offline> nmConnect('weblogic','weblogic','localhost','5556')
Connecting to Node Manager ...
<May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
sted CA certificate "CN=T-TeleSec GlobalRoot Class 3,OU=T-Systems Trust Center,O
=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificat
e list raised a certificate parsing exception PKIX: Unsupported OID in the Algor
ithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
sted CA certificate "CN=T-TeleSec GlobalRoot Class 2,OU=T-Systems Trust Center,O
=T-Systems Enterprise Services GmbH,C=DE". The loading of the trusted certificat
e list raised a certificate parsing exception PKIX: Unsupported OID in the Algor
ithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
sted CA certificate "CN=GlobalSign,O=GlobalSign,OU=GlobalSign Root CA - R3". The
loading of the trusted certificate list raised a certificate parsing exception
PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
<May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
sted CA certificate "OU=Security Communication RootCA2,O=SECOM Trust Systems CO.
\,LTD.,C=JP". The loading of the trusted certificate list raised a certificate p
arsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object: 1.2.84
0.113549.1.1.11.>
<May 3, 2011 10:45:02 AM EDT> <Notice> <Security> <BEA-090898> <Ignoring the tru
sted CA certificate "CN=KEYNECTIS ROOT CA,OU=ROOT,O=KEYNECTIS,C=FR". The loading
of the trusted certificate list raised a certificate parsing exception PKIX: Un
supported OID in the AlgorithmIdentifier object: 1.2.840.113549.1.1.11.>
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 123, in nmConnect
File "<iostream>", line 646, in raiseWLSTException
WLSTException: Error occured while performing nmConnect : Cannot connect to Node
Manager. : I/O error while reading domain directory
Use dumpStack() to view the full stacktrace
wls:/offline>
wls:/offline>
wls:/offline>
wls:/offline>
wls:/offline>
wls:/offline>
wls:/offline> dumpStack()
This Exception occurred at Tue May 03 10:45:03 EDT 2011.
weblogic.nodemanager.NMException: I/O error while reading domain directory
at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClie
nt.java:299)
at weblogic.nodemanager.client.NMServerClient.checkResponse(NMServerClie
nt.java:312)
at weblogic.nodemanager.client.NMServerClient.connect(NMServerClient.jav
a:248)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerCli
ent.java:199)
at weblogic.nodemanager.client.NMServerClient.checkConnected(NMServerCli
ent.java:205)
at weblogic.nodemanager.client.NMServerClient.getVersion(NMServerClient.
java:52)
at weblogic.management.scripting.NodeManagerService.verifyConnection(Nod
eManagerService.java:179)
at weblogic.management.scripting.NodeManagerService.nmConnect(NodeManage
rService.java:173)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.python.core.PyReflectedFunction.__call__(Unknown Source)
at org.python.core.PyMethod.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.core.PyObject.invoke(Unknown Source)
at org.python.pycode._pyx2.nmConnect$3(<iostream>:118)
at org.python.pycode._pyx2.call_function(<iostream>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyFunction.__call__(Unknown Source)
at org.python.core.PyObject.__call__(Unknown Source)
at org.python.pycode._pyx16.f$0(<console>:1)
at org.python.pycode._pyx16.call_function(<console>)
at org.python.core.PyTableCode.call(Unknown Source)
at org.python.core.PyCode.call(Unknown Source)
at org.python.core.Py.runCode(Unknown Source)
at org.python.core.Py.exec(Unknown Source)
at org.python.util.PythonInterpreter.exec(Unknown Source)
at org.python.util.InteractiveInterpreter.runcode(Unknown Source)
at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
at weblogic.management.scripting.WLST.main(WLST.java:180)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.WLST.main(WLST.java:29)
weblogic.nodemanager.NMException: I/O error while reading domain directory
wls:/offline>
wls:/offline>

Hi manohar,
Thank you, Pierluigi for encouraging Middleware Magic Team :)
manohar, apart from what *"Pierluigi"* has suggested, additionally please notice the following messsage in your StackTrace (whih is basically a NOTICE message but does not look good)
The loading of the trusted certificate list raised a certificate parsing exception PKIX: Unsupported OID in the AlgorithmIdentifier object:In your case it looks like the actual issue is your Certificate which comes by default with JDK. As mentioned in this BUG.
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6803022
Additionally please refer to the following Thread:
http://forums.oracle.com/forums/message.jspa?messageID=3958098#3958098
I am suspecting that you need to do the following in order to get rid of Certificate Errors which is the ROOT cause of your issue
Do the following: After taking a backup of *"$JAVA_HOME/jre/lib/security/cacerts"* file
cd $JAVA_HOME/jre/lib/security
cp -p cacerts cacerts.original
chmod 644 cacerts
keytool -delete -alias ttelesecglobalrootclass2ca -keystore cacerts
keytool -delete -alias ttelesecglobalrootclass3ca -keystore cacertsAlso try with Node Manager Communication type as "*Plain*" because it looks like you are getting PKIX security certificate chain message, just to isolate the issue.
Regards,
Ravish Mody

Problem starting Admin Server using Node Manager

I have configured the Node Manager to run as a windows service. I want it to start the Admin Server when it is started. This is not working. The Node Manager starts without problem but does not appear to even attempt to start the Admin Server. No error message is written to the nodemanager.log. I have configured the following properties as described in the documentation:
StartScriptEnabled=true
StartScriptName=startWebLogic.cmd
Starting the Admin Server using wlst works. As does starting and stopping a Managed server using the Admin console. This leads me to conclude that the Node Manager configuration is ok.
WLS version is 9.2.
All suggestions as to what could be the issue here would be greatly appreciated.
Cheers!

Ok, I just wasted a whole day before I found the tricks.
First, you don't need to do that StartScriptEnabled stuff, unless you have important things to add there.
Ok, and now what I found:
- You must make sure you have installed the NodeManager as a service
- Next, make sure the admin server is assigned to the right machine. Since you can do the WLST trick, that should be fine. If not, tough luck, because the docs say you cannot re-assign an admin server.
- In nodemanager.properties (...\weblogic92\common\nodemanager) make sure CrashRecoveryEnabled is set to true
- In nodemanager.domains (same dir) make sure your domain is mentioned with its path
- For each of the servers to be auto-started, make sure that a startup.properties (in <your-domain-dir> \servers\<server-name> \data\nodemanager) contains Arguments=-Xnohup (for JRockit, for Sun JDK its -Xrs)
Make sure they are started through the nodemanager, et voila, they'll be restarted after a reboot.
Why this works? At reboot, the OS ask all processes to die, nicely. Those that don't, get killed forcibly. Without the -Xnohup/rs, the WebLogic servers respond to the nice request, and the nodemanager immediately tries to restart them. Unfortunately, the OS refuses to do that, and the server process is marked as failed, and won't be restarted after reboot. With the option given, the servers ignore mr nice guy, and get killed after the nodemanager has disappeared.
What can go wrong? A lot. I was playing with the nodemanager username and password, and that took some time to clean up. I probably have to redo the entire setup just to make sure I have a repeatable experience now...
Cheers,
Bert

Java.io.IOException when to use WLST to connect admin server

Hello experts,
I am following this article to use wlst to connect to admin server from remote, but failed with below error.
Oracle WebLogic Server 12c: Configuring and Using Node Manager
>java weblogic.WLST
wls:/offline> connect('superadmin', 'agile9', 't3://myadminserver.company.com:7001')
Connecting to t3://myadminserver.company.com:7001 with userid superadmin ...
The CompatabilityMBeanServer is not initialized properly.
This might happen if the CompatabilityMBeanServer is
disabled via the JMXMBean.
To view the root cause exception use dumpStack()
WLST detected that the RuntimeMBeanServer is not enabled. This
might happen if the RuntimeMBeanServer is disabled via the JMXMBean.
Please ensure that this MBeanServer is enabled. Online WLST cannot
function without this MBeanServer.
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 22, in connect
File "<iostream>", line 648, in raiseWLSTException
WLSTException: Error occured while performing connect : "Cannot connect to WLST."
Use dumpStack() to view the full stacktrace
wls:/offline> dumpStack()
This Exception occurred at Tue Jul 22 20:45:53 PDT 2014.
java.io.IOException
java.io.IOException
wls:/offline>
I checked CompatabilityMBeanServer is already enabled in Admin Console
Does anybody has any idea how to resolve?
My Environment:
weblogic 12.1.1.0
OS: REL 6.0
Java: 1.7.0_21
Thanks
Jie

Hi,
Thanks for the reply. There was some problem with the input parameters to the automated activity. That error is resolved now.
I try to view the output of the automated activity, i.e, response of the web service call. I do an output mapping from the automated activity to a data object. But once I start the process and the automated activity executes, I could not see the output data in the context data in 'Operation Management --> Manage Processes'. The data object doesn't have any value.
The default trace doesn't have any error. I doubt if the web service is called at all!
Any suggestions?
Thank you.

Unable to connect to Admin Server from second machine using WLST

Hello,
PROBLEM
Can't get WLST to connect to admin server from 2nd host to register the domain.
SETUP
I have 2 Centos VMs running on Oracle Virtual box in a single laptop. Both the VMs use "Bridged Networking".
VM-1 CONFIG
cat /etc/hosts
192.168.1.17
dom1 dom1.my mac1
192.168.1.51
centos2 mac2
VM-1 hosts admin server & one managed server
VM-2 CONFIG
192.168.1.51
mac2
192.168.1.17
centos1 mac1
VM-2 hosts just one managed server
I can start up admin on VM-1 fine. The node manager is reachable too. Both the VMs are can be pinged from each other. I can also telnet to the admin server's port ( telnet 192.168.1.17 7001) from the second server.
My HOST OS is Windows 7. I can ping from windows to both the VM IPs too. The reverse is working fine as well.
I've tried both mechanisms of copying the whole domain from machine 1 over to machine2 & also using the pack.sh/unpack.sh combinations to transfer the domains.
When I invoke WLST, this is what happens
./wlst.sh
CLASSPATH=/apps/prod/appservers/weblogic/wls_10_3_6/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/apps/prod/appservers/weblogic/wls_10_3_6/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.25.x86_64/lib/tools.jar:/apps/prod/appservers/weblogic/wls_10_3_6/wlserver_10.3/server/lib/weblogic_sp.jar:/apps/prod/appservers/weblogic/wls_10_3_6/wlserver_10.3/server/lib/weblogic.jar:/apps/prod/appservers/weblogic/wls_10_3_6/modules/features/weblogic.server.modules_10.3.6.0.jar:/apps/prod/appservers/weblogic/wls_10_3_6/wlserver_10.3/server/lib/webservices.jar:/apps/prod/appservers/weblogic/wls_10_3_6/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/apps/prod/appservers/weblogic/wls_10_3_6/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/apps/prod/appservers/weblogic/wls_10_3_6/utils/config/10.3/config-launch.jar::/apps/prod/appservers/weblogic/wls_10_3_6/wlserver_10.3/common/derby/lib/derbynet.jar:/apps/prod/appservers/weblogic/wls_10_3_6/wlserver_10.3/common/derby/lib/derbyclient.jar:/apps/prod/appservers/weblogic/wls_10_3_6/wlserver_10.3/common/derby/lib/derbytools.jar::
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
wls:/offline> connect('weblogic','weblogic123','t3://192.168.1.17:7001')
Connecting to t3://192.168.1.17:7001 with userid weblogic ...
Traceback (innermost last):
File "<console>", line 1, in ?
File "<iostream>", line 22, in connect
File "<iostream>", line 648, in raiseWLSTException
WLSTException: Error occured while performing connect : Error connecting to the server : Could not obtain the localhost address. The most likely cause is an error in the network configuration of this machine.
Use dumpStack() to view the full stacktrace
wls:/offline> dumpStack()
This Exception occurred at Fri Oct 11 17:11:07 NZDT 2013.
java.lang.AssertionError: Could not obtain the localhost address. The most likely cause is an error in the network configuration of this machine.
java.lang.AssertionError: Could not obtain the localhost address. The most likely cause is an error in the network configuration of this machine.
wls:/offline>
Also, I can't invoke weblogic.Admin from the second VM despite setting the environment using "setWLSEnv.sh". i get the error "Error: Could not find or load main class weblogic.Admin".
Please could you help me fix this? I've spent 3 days now trying numerous things without much luck :-(
Kind Regards

Hi Raj,
Issue is with NM registry with domain home. Please follow the below steps and let us know the status.
1 . Check whether the node manager port ( default 5556 ) is opened for communication on both Admin and Managed server.
2 . After opening the port - We would need to enroll the node manager home with domain home to establish the communication between Admin and Managed server.
   a . Start the Administration Server.
   b . Using the Administration Console update the Node Manager credentials from the Advanced options under domain_nameArrow symbolSecurityArrow symbolGeneral.
   c . Invoke WLST and connect to an Administration Server using the connect command. See Using the WebLogic Scripting Tool in WebLogic Scripting Tool.
   d . Run nmEnroll using the following syntax:
        nmEnroll([domainDir], [nmHome])
Running nmEnroll() ensures that the correct Node Manager user and password token are supplied to each Managed Server. Once these are available for each Managed Server, you can use nmConnect() in a production environment.
Note:     You must run nmEnroll() on each machine that is running a Managed Server. Additionally, you should run nmEnroll() for each domain directory on each machine.
For more info : General Node Manager Configuration
Thanks
Lakshman

SCOM 2012 - Use Powershell to put specific server and contained objects into Maintenance Mode

I am still trying to develop what I thought was going to be an easy script, to put a specific server and all it's contained objects into maintenance mode in SCOM 2012.   Not a group, but just one specific server and all it's stuff.
My script to START maintenance mode has two parameters:
1. The FQDN. So for example: server1.contoso.com
2. The amount of minutes to put into maintenance mode
Then it does the following to START maintenance mode:
Import-Module OperationsManager
$Instance = Get-SCOMClassInstance -Name $FQDN
If ($Instance)
$newEnd = ((Get-Date).AddMinutes($minutes))
Start-SCOMMaintenanceMode -Instance $Instance -end $newEnd -Reason "PlannedOther" -Comment "Comments here"
This seems to work from what I can tell. I know that when you schedule maintenance mode manually in SCOM, there is an option to apply to "Selected objects and all their contained objects". I do not know if that is occurring based on
my code above.   But I think that is what I want to happen.   I just want all monitoring and alerting for the specified server to stop.   So if you think I need to change the above code so that it gets all the "contained
objects" please let me know.
The second part, which I know for a fact isn't fully working, is intended to stop maintenance mode for a server.
My script to STOP maintenance mode has only one parameter:
1. The FQDN. So for example: server1.contoso.com
Then it does the following to STOP maintenance mode:
Import-Module OperationsManager
$Instance = Get-SCOMClassInstance -Name $FQDN
If ($Instance)
$MMEntry = Get-SCOMMaintenanceMode -Instance $Instance
If ($MMentry)
#basically sends an end time of 1 minute from when the script is run
$newEnd = ((Get-Date).AddMinutes(1))
Set-SCOMMaintenanceMode -MaintenanceModeEntry $MMEntry -EndTime $NewEnd -Comment "Removing from Maintenance Mode"
This part does seem to work partially.   It does remove the server from maintenance mode. However, I suspect that it's not removing all the "contained objects" from maintenance mode because when I run the script to stop maintenance
mode on a server, the little maintenance mode icon in SCOM does go away but the overall light for the server stays set to "Not Monitored".   It never turns back to the green checkbox and says "Healthy".   When I start
and stop maintenance mode manually I can see that the green Healthy checkbox comes back. But when I try to run my above code to do it via script, it stays at "Not Monitored" instead.
Can someone help me out here? Looking for answers to two questions:
1. Does my Start maintenance mode code look ok? Will that put a server and all it's contained objects into maintenance mode?
2. What do I need to hadd to my Stop maintenance mode code, so that it correctly stops maintenance mode on the server and all its objects and everything starts to be monitored again?
Thanks in advance! Please let me know if you need any more information in order to be able to help me!

Hello, thanks for your response. Unfortunately, it does not appear that the link you provided works.
As far as not including "selected objects and all their contained objects" I am wondering if there is a way for me to tell for sure. One thing I found was that if I run this script and put the server into maintenance mode, then I go into
SCOM and click on Edit Maintenance Mode for that server, it shows me the details.   It has some comment, and my selected reason, based on the code I posted above.   It also DOES have "selected objects and all their contained objects"
selected at top. So it seems to me like it is working correctly, and does contain all the objects.   If you think that 'Edit' screen would be inaccurate for some reason, please let me know. Or if you know of a way for me to check and
confirm, please let me know that as well.
As for REMOVING it from maintenance mode, I did eventually find a line of code that I think works. Here's what my code looks like now:
Import-Module OperationsManager
$Instance = Get-SCOMClassInstance -Name $FQDN
If ($Instance)
$MMEntry = Get-SCOMMaintenanceMode -Instance $Instance If ($MMentry)
$Instance.StopMaintenanceMode([DateTime]::Now.ToUniversalTime(),[Microsoft.EnterpriseManagement.Common.TraversalDepth]::Recursive);
When I use the above code to STOP maintenance mode, the green checkmark does reappear for the server, and everything seems to be being monitored again.   Unlike before, where the maintenance mode icon would go away, but it would never change back
to saying 'Monitored' again. So I think that changing that one line to stop maintenance mode seems to have done the trick.
So I guess my last concern now is just putting in maintenance mode initially, as I was talking about above. If you still think the 'Edit Maintenance Mode' screen is not a good indicator of what my code does, please let me know.

Start Admin Server using NodeManager without 'boot.properties'

Hi All,
I am trying to stat Admin Server using nodemanager through below code.
public static void main(String args[]) {
          try{
          System.out.println("Starting...");
          InteractiveInterpreter interpreter = new WLSTInterpreter();
          interpreter.exec("nmConnect('weblogic', 'weblogic123', '10.0.0.100', '5556', 'domain1','D:/oracle/MiddleWare/user_projects/domains/domain1','ssl')");
          interpreter.exec("nmServerStatus('AdminServer')");
          interpreter.exec("nmStart('AdminServer')");
          interpreter.exec("nmDisconnect()");
          System.out.println("End.");
          }catch(Exception ex){
               System.out.println("Hello...");
               ex.printStackTrace();
     }Everything is working fine but we need a property file 'boot.properties' under location 'Bea Home/user_projects/domain/domain1/servers/AdminServer/data/nodemanager' having username and password.
Please let me know if there is any way to start Admin Server using nodemanager without using 'boot.properties' file.
Is there any way to provide username and password directly to 'nmStart()' method.
Please let me know...
Edited by: Rajesh Panchal on Jun 14, 2011 1:56 AM

Hi Rajesh,
Maybe you are looking for something like:
wls:/nm/IDMDomain> pr=makePropertiesObject("username=weblogic;password=weblogic0");
wls:/nm/IDMDomain> nmStart('AdminServer',props=pr);
Then, in your source code it should be something like:
interpreter.exec("pr=makePropertiesObject('username=weblogic;password=weblogic0')");
interpreter.exec("nmStart('AdminServer',props=pr)");
Hope it works.
-Cris

Putting Admin Server to use

Similar Messages

Maybe you are looking for