Node manager or the Admin server - which one to start first?

Hi Experts,
Somewhere i see its this way.
OBIEE 11.1.1.6 | OBIEE
To start the Oracle Business Intelligence system, you start:
the Node Manager(It is by default windows service in Enterprise Installation of OBIEE 11G)
the Administration Server (It is weblogic Admin Server)
the Managed Servers(Comes with Enterprise Installation of OBIEE 11G)
and then you start the system components.(All OBIEE Components : BI Server,Presentation Server,Schedular,Java Host,Cluster Services.
and at other places i see this...
OBIEE 11G - Starting Oracle Business Intelligence | GerardNico.com (BI, OBIEE, OWB, DataWarehouse)
To start the Oracle Business Intelligence system, you start:
the Administration Server
the Node Manager
the Managed Servers,
and then you start the system components.
I have Linux environment and it has just single BI Server and i go like this.
1) startWeblogic.sh script
2) startNodeManager.sh
3) startManagedWeblogic.sh
4) then system components.
Thanks
Ashish

so the way i am starting OBIEE Services currently is basically wrong ie..
1) startWeblogic.sh script
2) startNodeManager.sh
3) startManagedWeblogic.sh
4) then system components.
( by the way everything comes up perfect even if i start the nodemanager after the startWeblogic.sh script)
and i should do it this way..
1)startNodeManager.sh
2)startWeblogic.sh script
3)startManagedWeblogic.sh
4) then system components.
Kindly confirm...

Similar Messages

How to run OPatch against Node Manager from the admin server

How to run OPatch against Node Manager from the admin server

Hello,
I'm not sure what you meant by Opatch against nodemanager.You can check the below document about how to apply patches using Opatch
Oracle Fusion Middleware Patching with OPatch - 12c (12.1.2)
Refer the section " Common OPatch Commands When Patching an Oracle Fusion Middleware Oracle home"
/MR

How the process starts in XI and which one should start first ?

How the process starts in XI and which one should start first ?

XI flow :
1.File picked by the adapter,at the A.E it converts to XML format.
2.Generate a msg ID for the file and creates XI header to that file using CPA cache. CPA cache will be having the information about all the Control(address) data.
3.Module processor
4.The file goes to send queue by the adapter engine, that file will be picked by the internal XI adapter and the file will be forwarded to the Integration engine.
5.Pipeline steps follow the Integration Engine.
Receiver determination, Interface determination, Msg split, Msg mapping, Logical routing, Receiver aggrement, call adapter
6.The file will go to receive queue, which was taken and forwarded to the adapter engine.

How to find what port the admin server is running

how can I find out what port the admin server is running on a server?
thanks,

Hi
Go to your domain root folder/config and open config.xml file in any editor. Search for the name of the admin server which is typically like AdminServer and under this tag see if you have a tag by name <listen-port>. If yes, then you should see the port number. If not, it means it is running at default port of 7001.
If you have admin access, i hope when you login you will be giving url like http://adminhost:adminport/console. Now this adminport is the port on which admin server is running. If not, then check config.xml file.
Thanks
Ravi Jegga

Which thread will start first?

Hi,
I have a very basic question for you folks, considering the following example code,
new thread(new Runnable(){
public void run(){
TestThread t1 = new Thread();
t1.start();
}).start();
Now the question is which thread will start first. The outer one or t1?
Any explanation would be greatly appreciated.
/khurram

Sorry - I should have been more clear
Runnable r = new Runnable() {
public void run() {
}; //the run() method has not been called yet!
r.run(); //now it has!is defining a class which is to be instantiated. By "defining" a class, I mean providing an implementation of one of the class's methods. This method will not be invoked until explicitly called on the Object "r". The is exactly what is done when the start() is called on the outer thread. Is this a bit clearer?

Clustered enviroments -Starting/Stopping Managed servers, NodeManager & Admin server from single node

Hi,
We have 5 node Weblogic cluster. At the time of some mass activities like patching we have to stop all our managed, Admin Servers and node manager and it takes a lot of time to do this by logging in to all 5 managed servers and stopping all components. Though we have node manager configured so we can stop managed servers from console itself, but still have to login to each server to stop NodeManager and Oracle Http Servers.
Things become worse when wee have to shutdown almost 15-20 instances.
Is there a way (using wlst or shell script) that we can do all these tasks from by logging in to just one server?
Thanks,
Suraj

The simple code below would shutdown all the running Servers. Some of the APIs for ex MBeanHome are deprecated..still work though..if your concerned about that..I am working on the same using JMX API..if you want I could share that too. And also as described in the below link..you can Cluster stop and start using WLST commands. Managing the Server Life Cycle - 12c Release 1 (12.1.1)
<This code is from Oracle Weblogic documentation>
import java.util.Set;
import java.util.Iterator;
import java.rmi.RemoteException;
import javax.naming.Context;
import javax.management.ObjectName;
import java.io.*;
import java.net.*;
import weblogic.jndi.Environment;
import weblogic.management.MBeanHome;
import weblogic.management.WebLogicMBean;
import weblogic.management.configuration.ServerMBean;
import weblogic.management.runtime.ServerRuntimeMBean;
import weblogic.management.runtime.ServerStates;
import weblogic.management.WebLogicObjectName;
public class ServerStopper {
public static void stop() throws Exception {
 MBeanHome home = null;
 //url of the Admin server
 String url = "t3://localhost:7001";
 String username = "weblogic";
 String password = "welcome1";
 ServerRuntimeMBean serverRuntime = null;
 Set mbeanSet = null;
 Iterator mbeanIterator = null;
 try {
 // Set ContextClassloader to prevent assertions
 URL[] urls = { new File("/").toURL() };
 Thread.currentThread().setContextClassLoader(new
 URLClassLoader(urls));
 Environment env = new Environment();
 env.setProviderUrl(url);
 env.setSecurityPrincipal(username);
 env.setSecurityCredentials(password);
 Context ctx = env.getInitialContext();
 home = (MBeanHome)
 ctx.lookup("weblogic.management.adminhome");
 mbeanSet = home.getMBeansByType("ServerRuntime");
 mbeanIterator = mbeanSet.iterator();
 while(mbeanIterator.hasNext()) {
 serverRuntime = (ServerRuntimeMBean)mbeanIterator.next();
 if(serverRuntime.getState().equals(ServerStates.RUNNING)){
 serverRuntime.shutdown();
 } catch (Exception e) {
 e.printStackTrace();

Does SNMP agent on the admin server polls managed objects automatically?

Hi All,
If I enable SNMP agent on the admin server, does it mean that it polls and caches MIB of all the managed servers in the domain and return it if a client requests for information or it polls and caches that MIB value only when requested?
2)Suppose a client requests for SNMP data of a managed instance and the instance is down, does admin server keep polling or does it timeout after a number of secs or retries. I don't see any config params in weblogic 8.1.3 or weblogic 9.0 console.
Thanks. I appreciate your answers.
Thanks,

Are you saying the notes are incorrect?
No, I wasn't commenting on that at all. I was just saying that DBUA is the recommended way of upgrading databases... and that's in spades if you're talking about 100GB databases.
I'll lay odds that DBUA to 10.2.0.1 and then patching to 10.2.0.3 is quicker than exporting and importing 100GB of data.
(Applying a 10.2.0.3 patch is done with opatch and doesn't require a fresh installation of Oracle. A patch mostly just modifies the data dictionary: it's finished in minutes, not hours).
My real point: these sorts of questions are incredibly easy to ask, answer, discard, re-ask, modify, mull over and basically experiment with in a virtual environment.
And again: it's utterly bizarre why you wouldn't have physical access to this database (and keep in mind that I can't keep in mind little nuggets of information such as this one which you didn't see fit to share earlier!)
It's in a virtual server. Virtual servers can be zipped up and emailed! (OK, maybe not 100GB... but I've shipped a small hard disk in a zip-lok pack envelope half way round the world before now -though obviously it wasn't critical to have the contents of that envelope available for use all the time... Still, it sounds to me like here's a technology (virtualisation) that's not being properly exploited).

How to upgrade the Admin Server to WLS 9.2.3 while Managed on 9.2.2

HI,
I have a WLS 9.2.2 domain with Admin and 2 Managed instances clustered. Admin and Managed Servers are on different machines.
I want to upgrade only the Admin Server to WLS 9.2 MP3 while all my Managed Servers are in WLS 9.2 MP2.
Can any one provide me the detailed steps on how to upgrade only the Admin server to WLS 9.2 MP3?
And I read in the Weblogic documentation that this supported. But could not find any detailed steps on how to upgrade only the Admin server to the Major version.
Thanks in Advance.

Hi
1. "And I read in the Weblogic documentation that this supported". Can you please provide the link or documenation that exactly says that this is Supported ???
2. As far as I know, one of the basic requirements for Weblogic Cluster with managed servers across different remote machines is, all the machines, Admin and Managed Servers machines should have Exact Same Version (including Service Pack) of WLS deployed. Right now I do not have this link on top of my head. But this is the only Supported and one basic requirement for Weblogic Cluster.
Since WLS uses all Shared Modules and each Shared module do have like Implementation and Specification Version. If you upgrade admin server domain, most probably config.xml file will be upgraded with all modules version as 10.0.2.3 (something like that). This means when you restart Managed Servers, they will get a new copy of config.xml file from admin server machine. So now on Managed Servers all these modules (10.0.2.3 etc) should exist on their local machines. This is just my thought.
Thanks
Ravi Jegga

Passing memory settings from the Node Manager to the Managed Server

All,
I am trying to start a Managed server from the Node Manager. The configuration is as follows:
I have a domain with two managed servers(M1, M2). I could start both of them using the shell scripts without any problems. Both of the servers has custom memory settings -Xms3072m -Xmx3072m -XX:PermSize=256m
to facilitate deployment and effective operation of managed servers (the applications being deployed are kind of large).
Now, I am trying to start the same two servers using Admin Console:
In the admin console: I created a Unix Machine(U1) assigned the managed servers (M1, M2) to U1. I started the Node Manager on U1.
When I try to start a Managed Server from console, the server is starting but the memory settings (-Xms3072m -Xmx3072m -XX:PermSize=256m ) are not passed to the managed server startup, so the application deployment is failing with out of Memory errors. I tried to assign same memory settings to Node manager assuming it will pass on that configuration to the node manager without any luck.
Any help is appreciated.
Thanks
Raj

Starting Managed Server from Node Manager

Trying to run the SOA/BPM managed server withOUT running the Admin server

(This is for demo/development purposes... Using 11.1.1.4 in Windows 7 with 4gb)
Because of memory constrains I am trying to run the BPM/workspaces application without needing the Admin to be running.
When they both run, I can use the credentials I create with the Admin server but the response time is prohibitive and all my memory is used...
It seems to run much faster when only the bpm managed server is running but then I cannot login ...
So my question is simply: Whats the easiest way to set it up so I can use credentials elsewhere without requiring the admin server to be running?
( I could connect to an OID instance I have outside this server or the seeded demo they refer to in other posts ... but do these also require the admin server to be running???)
aTdHvAaNnKcSe ! (thanks IN advance)
Claudio
Edited by: clichten on Aug 20, 2011 9:35 AM

I don't know if what you want is possible. Only did a suggestion that works fine for me. I'm running SOA Suite and BPM Suite 11.1.1.5 on WLS 10.3.5
Configure a new WLS domain and see if the BPM Dev template is available in your version.
I've tuned my startup script (setSOADomainEnv.cmd) as follows:
set JAVA_OPTIONS=%JAVA_OPTIONS%
set DEFAULT_MEM_ARGS=-Xms512m -Xmx1024m
set PORT_MEM_ARGS=-Xms1536m -Xmx1536m
if "%JAVA_VENDOR%" == "Oracle" goto OracleJVM
set DEFAULT_MEM_ARGS=%DEFAULT_MEM_ARGS% -XX:PermSize=128m -XX:MaxPermSize=512m
set PORT_MEM_ARGS=%PORT_MEM_ARGS% -XX:PermSize=256m -XX:MaxPermSize=512m
Use visualvm that's available from your jdk/bin directory to monitor your jvm and optimize it accordingly
Regards,
Melvin

Can I run a different user as the managed server than the admin server?

Under unix, can I run a Weblogic 7 managed instance as a different user than the
admin server in the same domain? If not, any reference docs on BEAs site?

You mean a different UNIX user? Yes, that should be fine.
-- Rob
Frank wrote:
Under unix, can I run a Weblogic 7 managed instance as a different user than the
admin server in the same domain? If not, any reference docs on BEAs site?

Can you run a different user on the managed server than the admin server?

Under unix, can I run a Weblogic 7 managed instance as a different user than the
admin server in the same domain? If not, any reference docs on BEAs site?

That shouldnt pose a problem.
anand
In article <3f679e4d$[email protected]>, Frank wrote:
>
Under unix, can I run a Weblogic 7 managed instance as a different user than the
admin server in the same domain? If not, any reference docs on BEAs site?

"Unauthorized Host" error when you try to connect to the admin server

"Unauthorized Host" error when you try to connect to the admin server

If you see this error message when you try to connect to a Netscape
administration server:
Internal Error
The administration server was unable to fulfill your request.
Reason: Unauthorized host
--------------------------
Here is how to solve the problem and gain access. First you should
temporarily open access to all sites, and then once you make sure that
this lets you get into your administration server, try again to set up
the domain name or IP address access restrictions you want.
For all 2.x/3.x Netscape servers on Windows NT and Unix, or for Commerce and
Communications servers (1.x) on Unix:
<OL>
<LI>Open the "ns-admin.conf" file with a text editor. You can
find this file in the "admserv" directory under your Netscape
server root. The directory is named "admin-serv" in 3.x servers.
<LI>Delete the "Hosts" and "Addresses" lines you see there (either one
of them might not be present). Don't confuse the "Addresses" line,
which you should delete, with the "Address" line, which you should NOT
delete.
<LI>Save the file, then restart your administration server (on Unix run
"stop-admin" then "start-admin"; on Windows NT go into the Services
control panel and stop/start the "Netscape Admin Server" service).
</OL>
For Commerce Server or Communications Server (1.x) on Windows NT:
<OL>
<LI>Go into the registry editor. On Windows NT 4.0, run the command
"regedit". On Windows 3.51, run the command
"regedt32".
<LI>Navigate down to the section
"HKEY_LOCAL_MACHINE\SOFTWARE\Netscape\Administration".
<LI>Delete the "Hosts" and "Addresses" entries you see there (either one
of them might not be present). Don't confuse the "Addresses" entry,
which you should delete, with the "Address" entry, which you should NOT
delete.
<LI>Close the registry editor, then restart your administration server
by going into the Services control panel and stopping then starting the
"Netscape Administration" service.
</OL>
Now try again to access your administration server. Remember, the URL
will be something like "http://servername:12345/", where
"12345" is where the administration server's port number goes.
If you still get the same "Unauthorized host" error, then make sure that
your "ns-admin.conf" file really doesn't contain any "Hosts" or
"Addresses" lines any more, and try stopping your administration server
again then starting it back up.
Once you have access to your administration server, you can try again to
set up the access controls you want.
<UL>
<LI>For the administration server on a 3.x server installation, select
"Admin Preferences" from the General Administration page (the first page
you see when you connect to the admin server), then click on "Superuser Access
Control" and enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the subsrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that
your DNS can resolve those hostnames -- it's generally safer to stick
with IP address restrictions. When you're finished configuring this,
click "OK" then restart your admin server.
<LI>For the administration server on a 2.x server installation, select
"Configure Administration" from the Server Selector page (the first page
you see when you connect to the admin server), then click on "Access
Control" and enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the subsrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that
your DNS can resolve those hostnames -- it's generally safer to stick
with IP address restrictions. When you're finished configuring this,
click "OK" then restart your admin server.
<LI>For the administration server on a 1.x server installation, select
"Configure Administration Server" from the bottom of the Server Manager
page, then enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the substrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that your
DNS can resolve those hostnames -- it's generally safer to stick with IP address
restrictions.
When you're finished configuring this, click "Make These Changes" then
restart your admin server.
</UL>
If you still find yourself getting an "Unauthorized host" error message,
you can use the above steps to open up access and try different
settings.

"Unauthorized Host" error when you try to connect to the admin server

If you see this error message when you try to connect to a Netscape
administration server:
Internal Error
The administration server was unable to fulfill your request.
Reason: Unauthorized host
--------------------------
Here is how to solve the problem and gain access. First you should
temporarily open access to all sites, and then once you make sure that
this lets you get into your administration server, try again to set up
the domain name or IP address access restrictions you want.
For all 2.x/3.x Netscape servers on Windows NT and Unix, or for Commerce and
Communications servers (1.x) on Unix:
<OL>
<LI>Open the "ns-admin.conf" file with a text editor. You can
find this file in the "admserv" directory under your Netscape
server root. The directory is named "admin-serv" in 3.x servers.
<LI>Delete the "Hosts" and "Addresses" lines you see there (either one
of them might not be present). Don't confuse the "Addresses" line,
which you should delete, with the "Address" line, which you should NOT
delete.
<LI>Save the file, then restart your administration server (on Unix run
"stop-admin" then "start-admin"; on Windows NT go into the Services
control panel and stop/start the "Netscape Admin Server" service).
</OL>
For Commerce Server or Communications Server (1.x) on Windows NT:
<OL>
<LI>Go into the registry editor. On Windows NT 4.0, run the command
"regedit". On Windows 3.51, run the command
"regedt32".
<LI>Navigate down to the section
"HKEY_LOCAL_MACHINE\SOFTWARE\Netscape\Administration".
<LI>Delete the "Hosts" and "Addresses" entries you see there (either one
of them might not be present). Don't confuse the "Addresses" entry,
which you should delete, with the "Address" entry, which you should NOT
delete.
<LI>Close the registry editor, then restart your administration server
by going into the Services control panel and stopping then starting the
"Netscape Administration" service.
</OL>
Now try again to access your administration server. Remember, the URL
will be something like "http://servername:12345/", where
"12345" is where the administration server's port number goes.
If you still get the same "Unauthorized host" error, then make sure that
your "ns-admin.conf" file really doesn't contain any "Hosts" or
"Addresses" lines any more, and try stopping your administration server
again then starting it back up.
Once you have access to your administration server, you can try again to
set up the access controls you want.
<UL>
<LI>For the administration server on a 3.x server installation, select
"Admin Preferences" from the General Administration page (the first page
you see when you connect to the admin server), then click on "Superuser Access
Control" and enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the subsrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that
your DNS can resolve those hostnames -- it's generally safer to stick
with IP address restrictions. When you're finished configuring this,
click "OK" then restart your admin server.
<LI>For the administration server on a 2.x server installation, select
"Configure Administration" from the Server Selector page (the first page
you see when you connect to the admin server), then click on "Access
Control" and enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the subsrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that
your DNS can resolve those hostnames -- it's generally safer to stick
with IP address restrictions. When you're finished configuring this,
click "OK" then restart your admin server.
<LI>For the administration server on a 1.x server installation, select
"Configure Administration Server" from the bottom of the Server Manager
page, then enter hostname and IP address restrictions. If you want
allow access to multiple clients, you'll have to use wildcard patterns
(separate the substrings with a pipe character, like
"(host1|host2|host3)"); the substrings must be enclosed in parentheses, as shown.
If you're setting up hostname restrictions, you'll need to make sure that your
DNS can resolve those hostnames -- it's generally safer to stick with IP address
restrictions.
When you're finished configuring this, click "Make These Changes" then
restart your admin server.
</UL>
If you still find yourself getting an "Unauthorized host" error message,
you can use the above steps to open up access and try different
settings.

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 )

Monitoring Managed servers if Admin server is unavailable in Weblogic

Is it possible to find managed servers state ( example: RUNNING, FAILED, UNKNOWN etc..) if Admin server is unavailable( may be down) in Weblogic.
We can search the state of managed server using keywords in managed server logs. But we don't want to do that.
Is there any other way to find the managed servers state.
Thanks,
Venkat

WLST and connecting to managed servers is one option.
Another one is using a RESTful approach: the one that comes with WLS12c in centrally located on the admin server and therefore not really helpful in your case
You might try OpenSource Jolokia ( Overview ) which is a nifty little tool.
Some more infos about Jolokia and WebLogic:
RESTful WebLogic Monitoring of Servers, Applications, JDBC and JMS with Jolokia — munz & more
best regards!

Node manager or the Admin server - which one to start first?

Similar Messages

Maybe you are looking for