WLS 6.1 console ACL

Anyone want to tell me how to add users/groups to the console ACL. I've got
some users that want access to the console, but I don't want them in the
Administrators group. WLS 6.1 SP4.
Thanks!
Phil Knost
Sr. Architect
McKesson Information Solutions

Hi John,
          is there any reason why you start with WLS6.1, the most actual version is Weblogic 8.1 with service pack 3?
          If you need to stay with 6.1, then please upgrade to the highest service pack level (SP7) at least.
          --Stefan

Similar Messages

Console startup of WLS - Where does console get CLASSPATH?

Hi-
I just installed the eval version of WLS 5.1 + SP5 on my NT4 box. I followed the
SP5 installation instructions for modifying my classpath to include the new sp5
jars. Here's the output of wlconfig:
WebLogic startup settings are presently:
CLASSPATH Prefix d:\weblogic\lib\weblogic510sp5boot.jar
CLASSPATH
d:\weblogic\lib\weblogic510sp5boot.jar;d:\jdk1.3\lib\tools.jar;d:\jdk1.3\jre\lib\rt.jar;d:\jdk1.3\jre\lib\i18n.jar;d:\weblogic\license;d:\weblogic\classes\boot;d:\weblogic\classes;d:\weblogic\lib\weblogicaux.jar;d:\weblogic\eval\cloudscape\lib\cloudscape.jar
JAVA_HOME d:\jdk1.3
WEBLOGIC_LICENSEDIR d:\weblogic\license
WEBLOGIC_HOME d:\weblogic
system properties:
java.security.manager
java.security.policy==d:\weblogic\weblogic.policy
weblogic.system.home=d:\weblogic
java.compiler=NONE
weblogic.class.path=c:\weblogic\lib\weblogic510sp5.jar;d:\weblogic\license;d:\weblogic\classes;d:\weblogic\myserver\serverclasses;d:\weblogic\lib\weblogicaux.jar
INITIAL_HEAP 64 MB
MAX_HEAP 64 MB
SERVERCLASSPATH
d:\weblogic\lib\weblogic510sp5boot.jar;d:\jdk1.3\jre\lib\rt.jar;d:\jdk1.3\jre\lib\i18n.jar;d:\weblogic\classes\boot;d:\weblogic\eval\cloudscape\lib\cloudscape.jar
Now: If I start the server using startWebLogic.cmd and then attach the console
to it, I see that I'm running SP5 and the CLASSPATH is what I expect. However,
if I start WLS from the console I see that
d:\weblogic\lib\weblogic510sp5boot.jar is NOT in the CLASSPATH and I'm actually
running the "original" WLS 5.1
My question: Where is the console getting its settings, if not from the
registry? How can I change the console settings so it uses the right CLASSPATH?
Thanks,
James Scott

I'm not sure I understand your specific problem. Can you provide some details.
WLS does not require its admin console to be running, and it can be run in the background. (ie started via nohup from an init script.)
-- Rob
WLS Blog http://dev2dev.bea.com/blog/rwoollen/

WLS 5.1 Console connect throug firewall

Greetings,
Could someone please tell me if he/she did manage to connect via a firewall with
the WLS5.1 Console (Java-GUI-Console)?
If yes, how did you manage?
Thank you,
Dave

Same here. I am on WLS6.1 sp1, on Solaris 2.6. We restarted our
production admin last week. of our 4 clustered apps, 2 are showing as
running and 2 are not. However, all 4 or actually up and responding. How
can we get the admin server to discover them. I have discover on, or I
wouldn't see the 2 clusters that I do.
Dimitri I. Rakitine wrote:
Did you try using http: instead of t3: when connecting to WLS? (also
note that http tunnelling is disabled by default starting from some
service pack - 8?).
Dave Helger <[email protected]> wrote:
Greetings,
Could someone please tell me if he/she did manage to connect via a firewall with
the WLS5.1 Console (Java-GUI-Console)?
If yes, how did you manage?
Thank you,
Dave

Cannot create JVM message box in WLS 92 admin console

Hi,
I want to open a new windows process from weblogic admin console. I wanted to know if there is a way to launch a jvm from console.
If I use Runtime.getRuntime().exec(cmd), cmd is a javaw command, in my console extension, I get "cannot create JVM" dialog box.
Is this possible?
Pl. suggest

Hi,
I want to open a new windows process from weblogic admin console. I wanted to know if there is a way to launch a jvm from console.
If I use Runtime.getRuntime().exec(cmd), cmd is a javaw command, in my console extension, I get "cannot create JVM" dialog box.
Is this possible?
Pl. suggest

WLS 9.2 Console App Conflicts with Stuts2 App

We are seeing the following error when starting up our Struts2 application on the Admin server.
          ERROR org.apache.beehive.netui.pageflow.internal.AdapterManager :
          ServletContainerAdapter manager not initialized correctly.
          The error seems to be happening as a result of the struts configuration setting which allows you to set a class to handle MulitPart Requests:
          struts.multipart.parser=mypackage.MyMultiPartRequest
          It appears that this error only occurs when the application is installed on the admin server. Our application is not utilizing Beehive. It appears though that the Weblogic Console is. I believe that the two are conflicting. When running our application on a managed server without the console app, we do not get the error.
          This is okay since our production and test environments are set up this way anyhow. However, our developers working locally by installing the app in the admin server rather than running an admin server and a managed server.
          Anyone seen this or know of a work around?

Have you been able to fix this problem?
          Did you try prefer-web-inf-classes" in the
          weblogic.xml file?
          Unfortunately, I don't have any suggestions. I'm in the same quandry and looking for answers.

Starting WLS from the console...

Hello,
when trying to start the WL server from within the WL console on
my NT4, it seems like the console is trying to build a new classpath
rather than using the one it was started with.
This would be fine apart from the fact that it doesn't seem to
be doing this correctly. I have built my environment using wlconfig.exe
and the properties page in the console looks fine (i.e. all the
jars and other bits and bobs are in place). The registry also (obviously)
looks fine. However, the classpath used to start the server SHOULD
be prepended by the value of HKEY_LOCAL_MACHINE/SOFTWARE/BEA/WL5.1/CLASSPATH
but it isn't?? (As an aside, why call it classpath when it really
only the classpath_prefix?)
It also took me a while to find that there are two binaries used
for starting the console: wlconsolew.exe and wlconsole.exe. wlconsolew.exe
is what is run when you use the Start Menu and it blatantly ignores
any settings in the registry. wlconsole.exe does this right but
still manages to stuff up the building of the classpath for starting
the server. Any VM settings in the registry are also ignored.
Any comments? Has anyone managed to find a way around this (apart
from the obvious, i.e. using scripts instead?)
/Lars

A partial solution might be the following. Make shortcuts in your programs folder to target the batch files in %TOMCAT_HOME%\bin.
Then, all you need to do is select the shortcuts whenever you need to access the server.
The command prompt window will still be visible, but this method saves some typing time.
The next step is figuring out how to make Tomcat a Windows service so it runs in the background. I don't know how to do this.

How to create and deploy a war file on wls using the console

          my question is how to deploy the simpleSession.jsp example in the weblogic/samples/examples/jsp/
          dir examples as a war file on wls cluster what are the steps to do so.. thanks
          in advance


[att1.html]

Monitoring JRockit 8.0 from WLS console

Hi,
In JRockit 8.0 docs in section "Monitoring WebLogic JRockit JVM from WebLogic
Server" I read the following:
To monitor WebLogic JRockit JVM, do the following:
Start WebLogic Server with WebLogic JRockit JVM as the VM.
In the left pane of the Administration Console, expand the Servers folder.
Click a server that is using the WebLogic JRockit JVM.
In the right pane, click the Monitoring tab. Then click the JRockit tab.
Unfortunately there is no JRockit tab in WLS 7.0 sp1 console. Is it possible
to monitor JRockit from WLS 7.0 console? Any additional setup needed for that?
Thanks in advance,
Andrew

Unfortunately this piece of documentation refers to the coming release of
WLS, not 7.0. Sorry about that.
Regards,
/Staffan
"Andrew" <[email protected]> skrev i meddelandet
news:[email protected]..
>
Hi,
In JRockit 8.0 docs in section "Monitoring WebLogic JRockit JVM fromWebLogic
Server" I read the following:
To monitor WebLogic JRockit JVM, do the following:
Start WebLogic Server with WebLogic JRockit JVM as the VM.
In the left pane of the Administration Console, expand the Servers folder.
Click a server that is using the WebLogic JRockit JVM.
In the right pane, click the Monitoring tab. Then click the JRockit tab.
Unfortunately there is no JRockit tab in WLS 7.0 sp1 console. Is itpossible
to monitor JRockit from WLS 7.0 console? Any additional setup needed forthat?
>
Thanks in advance,
Andrew

WLS 12.1.2.0.0 : Another user (admin2) already owns the lock.

hi
Please consider a WebLogic Server 12.1.2.0.0 that is NOT in Production Mode (so in Development Mode).
When is a button like "Take Lock & Edit" (ever) to be expected?
Or messages like :
- "admin2 is currently making changes."
- "Another user (admin2) already owns the lock. You will need to either wait for the lock to be released, or take the lock."
If both users "admin1" and "admin2" are in the "Administrators" group,
the following scenario (sc1) seems to be reproducible:
- (sc1-a) start a first browser session and login on the WLS admin-server console using "admin1"
- (sc1-b) start a second browser session and login on the WLS admin-server console using "admin2"
- (sc1-c) in the second browser session, click Deployments
- (sc1-d) in the first browser session, click Deployments and see the "Take Lock & Edit" button and messages
-- "admin2 is currently making changes."
-- "Another user (admin2) already owns the lock. You will need to either wait for the lock to be released, or take the lock."
The scenario (sc1) is included in the screencast
at http://screencast.com/t/Yw3k3EI1
- (q1) Is the lock message in scenario (sc1) intended behavior?
It could be that these "locks" are causing our Jenkins jobs (doing an Ant wldeploy task) to fail when someone is "browsing" using the WebLogic Server console, with
weblogic.management.provider.EditWaitTimedOutException: Waited 0 milliseconds
    at weblogic.management.provider.internal.EditLockManager.getEditLock(EditLockManager.java:259)
    at weblogic.management.provider.internal.EditAccessImpl.acquireLock(EditAccessImpl.java:266)
    at weblogic.management.provider.internal.EditAccessImpl.startEdit(EditAccessImpl.java:297)
    at weblogic.deploy.internal.adminserver.EditAccessHelper.startEditSession(EditAccessHelper.java:72)
    at weblogic.deploy.internal.adminserver.operations.AbstractOperation.execute(AbstractOperation.java:236)
    at weblogic.management.deploy.internal.DeployerRuntimeImpl$2.run(DeployerRuntimeImpl.java:846)
    at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)
    at weblogic.management.deploy.internal.DeployerRuntimeImpl.performDeployerActions(DeployerRuntimeImpl.java:840)
    at weblogic.management.deploy.internal.DeployerRuntimeImpl.deploy(DeployerRuntimeImpl.java:418)
many thanks
Jan Vervecken

The answer to this "(q1) Is the lock message in scenario (sc1) intended behavior?" you already know. Just for good measure see the documentation on managing locks (5 Managing a Domain's Configuration with JMX). Note that in development mode the locking in the admin console is automatic, you can change this in Admin Console - click the preferences link, User Preferences tab, here you can change the 'Automatically Acquire Lock and Activate Changes' option.
WebLogic provides a ConfigurationManagerMBean (http://docs.oracle.com/middleware/1212/wls/WLMBR/mbeans/EditServiceMBean.html?skipReload=true#ConfigurationManager) that provides methods for safely starting an edit session. You can use haveUnactivatedChanges (http://docs.oracle.com/middleware/1212/wls/WLMBR/mbeans/ConfigurationManagerMBean.html?skipReload=true#haveUnactivatedChanges) to check if there are any pending changes (this gives you an indication if someone that has taken a lock is doing some actual changes to the system, such that the ANT job can decide not to start an edit session). If there is an edit session going on and there are no pending changes you can call undoUnactivatedChanges (http://docs.oracle.com/middleware/1212/wls/WLMBR/mbeans/ConfigurationManagerMBean.html?skipReload=true#undoUnactivatedChanges) - now the ANT job can start a new edit session.
The following example shows the use of the ConfigurationManager (in Java with JMX)
                        Object[] unactivatedChanges = (Object[]) editConnection.getAttribute(configManager, "UnactivatedChanges");
                        if (unactivatedChanges.length > 0) {
                            System.out.println("ACTIVATING CHANGES");
                            editConnection.invoke(configManager, "activate",
                                    new Object[] { new Long(120000) }, new String[] { "java.lang.Long" });
                        } else {
                            System.out.println("CANCEL EDIT SESSION");
                            editConnection.invoke(configManager, "cancelEdit", null, null);
More information can be found on using the EditService and ConfigurationManager can be found here: Middleware Snippets: Automatic Scaling an Application Using WebLogic (and the references therein).

ACL for web application

Dear all,
I am using WLS5.1 sp9 and would like to do web application
and custom realm. I also need ability to change ACL for
any user or group on the fly without restarting WLS.
But after reading WLS document, I found that ACL is tied with
deployment descriptor. So does it mean ACL in custom realm is
useless? It also means we need to restart WLS everytime we
modify ACL, doesn't it?
Thanks you very much,
Khemchart

Hi Gokula,
Web Application security is defined in the servlet spec. You should use
web.xml and weblogic.xml to configure security instead of using acl's
I am enclosing the link to the relevant documentation below
http://e-docs.bea.com/wls/docs61/webapp/security.html#100365
Gokula Krishnan wrote:
Hi All,
I am working on Weblogic6.1 and iPlanet Directory Server 5.1. I
am trying to create ACL's in Weblogic and to test a Web Application
which I have configured in weblogic. The problem is I am not able to
create a ACL for the web application resource in weblogic. Could any
one pls help me on how to create ACL through weblogic console.
I try creating ACL as per the document but I dont now how to give
permission and map the ACL for the resource.
Thanks in advance...
With regards,
Gokul.

UndeclaredThrowableException while trying to deploy EJB in WLS 6.1

I get the following excption while trying to deploy a Entity Bean
through the WLS 6.1 console:-
<Error deploying application
.\config\mydomain\applications\EnrollmentTransaction.jar:
java.lang.reflect.UndeclaredThrowableException
Can anyone throw some light on this one.
Anand
PS:- This JAR was compile using the WLS 5.1 EJBC

You'll have to show me the full error message, but you'll need to
re-compile with the weblogic.ejbc in 6.1
-- Rob
Anand B N wrote:
I get the following excption while trying to deploy a Entity Bean
through the WLS 6.1 console:-
<Error deploying application
.\config\mydomain\applications\EnrollmentTransaction.jar:
java.lang.reflect.UndeclaredThrowableException
Can anyone throw some light on this one.
Anand
PS:- This JAR was compile using the WLS 5.1 EJBC

What is the best way to deploy/update custom security realm classes to WLS 6.0?

From the WLS 6.0 console, I see that I can specify the Java class that
implements my custom security realm but I am wondering what is the best way
to deploy/update this code. I don't see a way to do this from the console.
Does this mean that I have to manually copy the class files over that
implement my custom security realm?

Thanks Danut,
A jar file seems to be a good way to package it up but it sounds like it
still needs to be manually copied to each Weblogic server install directory
post-installation and whenever it is updated. I thought it would be nice to
be able to deploy/update the custom security realm by uploading it through
the Console just as you can with web applications and EJBs.
Brian
"Danut Prisacaru" <[email protected]> wrote in message
news:3aba2db0$[email protected]..
You have to have your Custom Realm class in the class path. I usually havea
jar file with all the Custom Realm classes and that jar I copy it in thelib
folder. Then I modify "startWebLogic.cmd" and I add to the classpath
".\lib\CustomRealm.jar"
set
CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar;.\lib\CustomRealm.jar;
>
Be aware that in order to have you custom realm besides creating thecustom
realm using the console you also have to create a custom caching andchoose
that one as your default caching realm.
Here is how the security settings are looking in my "config.xml"
<CustomRealm Name="CustomRealm"
RealmClassName="Custom.appserver.weblogic.security.CustomRealm"/>
<CachingRealm BasicRealm="CustomRealm" CacheCaseSensitive="true"
Name="CustomCachingRealm"/>
<Realm CachingRealm="CustomCachingRealm" FileRealm="wl_default_file_realm"
Name="wl_default_realm"/>
<FileRealm Name="wl_default_file_realm"/>
<Security GuestDisabled="false"
Name="mydomain" PasswordPolicy="wl_default_password_policy"
Realm="wl_default_realm"/>
Danut

Weblogic Server 9.2 - Weblogic Admin Console Error

When I open the admin console from the browser on localhost, I get an error "You must have valid license to use WebLogic Portal Framework.
It was working fine until some point and started giving this error.
Any help in resolving this is very much appreciated.
Thanks

Hello User,
You can find the application under below path
Domain_name - Expand "Environment" and Select " Deployments " - here your application will show which are deployed in this domain.
Please refer -http://docs.oracle.com/cd/E13222_01/wls/docs100/intro/console.html
Regards
Laksh

Can't start WLS7 console after changing configuration

Hi,
Do you have similar situation using WebLogic v7 ?
We can’t start our weblogic server after changing JMS configuration
a bit. Our consultant and I discussed about the solution - one of
them was to re-install weblogic domain. However, this method is not
good for production since all applications will have to be re-installed
again although this WLS is for internal testing.
Using your production mind, what is the better approach while you can't
even start weblogic console after an incomplete configuration.
Consultant's description:
"Our web application needs to configure WebLogic 7.0 JMS service via
wls console. After I did configure a new Connection Factory and a
Destination Keys (actually I should configure a new JMS server and
queue here), the WLS couldn’t reboot so that there is no way to logon
console to modify JMS configuration."
Thanks,
Alex Lin

If WLS through the console is creating an unbootable config.xml this is a
bug.
When you start WLS it makes a copy of its bootable configuration by renaming
config.xml to config.xml.booted. If this corruption occurs as you not with
the console, then you have to back up to config.xml.booted and start over.
You should open a case with support describing:
a) the exact version of wls
b) copy of "bad xml"
c) the exact steps you took to cause the problem
To work around the problem I would try following the exact steps listed
here:
http://edocs.bea.com/wls/docs70/ConsoleHelp/jms.html
Cheers
mbg
"Alex Lin" <[email protected]> wrote in message
news:[email protected]..
Hi,
Do you have similar situation using WebLogic v7 ?
We can't start our weblogic server after changing JMS configuration
a bit. Our consultant and I discussed about the solution - one of
them was to re-install weblogic domain. However, this method is not
good for production since all applications will have to be re-installed
again although this WLS is for internal testing.
Using your production mind, what is the better approach while you can't
even start weblogic console after an incomplete configuration.
Consultant's description:
"Our web application needs to configure WebLogic 7.0 JMS service via
wls console. After I did configure a new Connection Factory and a
Destination Keys (actually I should configure a new JMS server and
queue here), the WLS couldn't reboot so that there is no way to logon
console to modify JMS configuration."
Thanks,
Alex Lin

Changing port for console?

Hi,
is it possible to change WLS port for console application only on a standalone wls server?

If i understand you right then .....i guess what you need is to have console on a differnt port than the http listen port ....for this you can use Administartion port.....in your console go to the domain tab and in that Enable Administaration port and then you can use this port for the administrative traffic.....so the new url for consle will be t3s://ipaddress:adminport/console..please test this in a test enviornment first......
The other thing you were telling about is to change the context root for the console application ...you can do this in the same domain tab under configuration ...in the advanced tab you would see Console Context Path...just modify (sayfor eg: MyConsole) this and then you can use that value to bring up your console...http:ipaddress:port/MyConsole.....
Both the above changes needs a restart of admin server......
try in a test enviornment first.....
Hope this answers your question .....
Let us know if this works.......

WLS 6.1 console ACL

Similar Messages

Maybe you are looking for