Win a copy of Escape Velocity: Better Metrics for Agile Teams this week in the Agile and Other Processes forum!

Justin joseph

Greenhorn
+ Follow
since Aug 03, 2004
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
0
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Justin joseph

Hi,

we are running a Weblogic 9.1 server on AIX (5.3). When we enable application logs (and there are lots of logs), transactions are taking too much time to complete. Intel-linux based system is giving twice the performace. When the logs are turned off, AIX box performs as expected, I mean much much faster that any other systems we ahve tested. Tested this with enabling and disabling WL natvie I/O. same result.

we are using 32 bit jdk.

i assume, it has something to do with environment variables and configuration
Does anybody have any standard env variables and setting for WL on AIX, for optimum performace?

thanks in advance,
Justin
[ April 17, 2006: Message edited by: Justin joseph ]
16 years ago
Deployement descripotors define the runtime environment for your application. For example an EJB deployement descriptor defines, the JNDI names, the resource refeneces, the environment entries used by application , etc
16 years ago
Is t3 protocol written over TCp or UDP?

thanks in advance
16 years ago
try opening the file using this.getClass().getResourceAsStream(
"/filename.xml");

this will load from the classpath for the current classloader. this is much better approach, i think.
17 years ago
if u r calling from outside the container, give app servers initial context factory as param fro lookup
first one (when running without security manager) the issue is because of invalid class at the client side. u might want to check ur classpath. u can also use the serialver tool to locate the problem.

in the seconf case, u have to edit the policy file in the jre to give required permissions for opening a socket in prot 1099.
17 years ago
do u have the client jar or the jar which contains the interfaces(homa and remote) at the client side classpath??

thanks
17 years ago
try a
jar -cvf <jar-namr> .

in the folder and upload the same.
17 years ago
when our large applications goes live and they require to be updated without bringing down the system, we normally go for clustered environment for smooth application upgrade.

thanks
17 years ago
realm shud be ur network realm or PC name if u are loggin in using local domain.

u have to provide a jaas.conf by using:-Djava.security.auth.login.config=
and conf file shud contain :

MyLogin {
com.sun.security.auth.module.Krb5LoginModule required;
};

where MyLogin is the string that u pass to the constructor of LoginContext.
also KDC name has to be provided for kerberose usage.
17 years ago
when i use a custom registry websphere is using LptaLoginModule to login the user (by invoking my registry class). this class creates its own principal, i suppose, which implements WSPrincipal. so whatever i try to propagate from client is ot taking effect. the one created at the server side is being used. i get the name of the user correctly from the pricipal but other information which i have in my custom principal is not propagated.

is it possible to write my own login module at the server side and change the security.xml file so that it is inovked not the LptaLogin module. is it the recommended approach in websphere?

is there any way to propagate my own principal to the server side.

i'm at wits end now.... please help.

thanks
Justin
17 years ago
i'm at wits end now.... please help.

when i use a registry websphere is using LptaLoginModule to login the user (by invoking my registry class). this class creates its own principal, is suppose. so whatever i try to propagate from client is ot taking effect. the default one created at the server side is being used. i get the name of the user correctly from the pricipal but other information which i have in my custom principal is not propagated.

is there any way to propagate my own principal to the server side.

thanks
Justin
17 years ago
by the way, forgot to mention one thing.

when the server security is enabled, the lookup() call at client side authnticates the subject created at the client using login module using servers authentication mechanism, which is not JAAS but based on OS or ldap or custome registry.

my probelm is that my registry is database based and it is not the group user based registry that websphere supports for its security management. i would like use my own registry and apis and custom principal (ofcourse, derviced from WSPrincipal) needs to be propagated.

thanks
Justin
18 years ago
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.ibm.websphere.naming.WsnInitialContextFactory");
env.put(Context.PROVIDER_URL, "iiop://localhost:2809");
Context initialContext = new InitialContext(env);
java.lang.Object obj = initialContext.lookup("");
LoginContext lc1 = null;
lc1 = new LoginContext("MyLogin1",
new WSCallbackHandlerImpl("user1", "MyLogin1","pass1") );
lc1.login();
Subject as1= lc1.getSubject();


this code only looks for login modules at the client side. what i need is server login modules to be invoke from there. is there anything that i can write in client side login module which invokes server login module (for example: Authenticate.authenticate() in weblogic or security interceptor in jboss)
or is it some different mechanism in websphere?
What is the target realm name that we specify in Callbackhanler? does it have significance? because this is what is there inside the constructors of WSCallbackhandlerImpl
public WSCallbackHandlerImpl(String s, String s1)
{
if(tc.isEntryEnabled())
Tr.entry(tc, "WSCallbackHandlerImpl(userName = \"" + s + "\", password = \"********\")");
userName = s;
password = s1;
if(tc.isEntryEnabled())
Tr.exit(tc, "WSCallbackHandlerImpl(userName, password)");
}

public WSCallbackHandlerImpl(String s, String s1, String s2)
{
this(s, s2);
}
18 years ago