Subendu Dasgupta

Greenhorn
+ Follow
since Jul 11, 2001
Merit badge: grant badges
For More
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 Subendu Dasgupta

I am trying to run a perl script, and for that i have added the necessary code as listed in
http://edocs.bea.com/wls/docs81/webapp/components.html#100540
But I am getting Error 500--Internal Server Error. On viewing the log fole, i see the following message
CGIServlet: Failed to exec CGI script:index.pl
I am not sure, where i am doping wrong. pls help.
Also, i see that perl.exe as specified in the
<init-param> <param-name>*.pl</param-name> <param-value>/bin/perl.exe</param-value> </init-param>
is not present under the bin folder. In fact, I gave a search for perl.exe, and I didn't find it. let me know, if I need to install it separately.
Subendu
20 years ago
No, it was my typing mistake. It should have been "/config" everywhere.
21 years ago
We are facing problems in enabling SSL on BEA weblogic6.1 with sp3. We used RSA Keon CA to request the server certificates. The parameter values that were used for enabling SSL are specifed as below:

<SSL Enabled="true" ListenPort="7002" Name="myserver"
ServerCertificateChainFileName="config/mydomain/rsa_ca.pem"
ServerCertificateFileName="config/mydomain/rsa_cert.pem"
ServerKeyFileName="config/mydomain/rsa_net_key.der"
TrustedCAFileName="/config/mydomain/root.pem"/>
When the application was deployed using this setup, and was accesed using https, there were no errors that are reported.
But when the same setup is being used with a client side authentication we are getting errors as " Client Certificate Chain Invalid" in the WebAgents log file. We are using a RSA agent to protect the WebLogic.
The client side certificate is being asked by this agent but not from the weblogic. i.e the parameter "Client Certificate Enforced" is not set.
So if any of you could help out with the problem it would be of great help.
21 years ago
We are facing problems in enabling SSL on BEA weblogic6.1 with sp3. We used RSA Keon CA to request the server certificates. The parameter values that were used for enabling SSL are specifed as below:

<SSL Enabled="true" ListenPort="7002" Name="myserver"
ServerCertificateChainFileName="config/mydomain/rsa_ca.pem"
ServerCertificateFileName="config/mydomain/rsa_cert.pem"
ServerKeyFileName="config/mydomain/rsa_net_key.der"
TrustedCAFileName="/config/mydomain/root.pem"/>
When the application was deployed using this setup, and was accesed using https, there were no errors that are reported.
But when the same setup is being used with a client side authentication we are getting errors as " Client Certificate Chain Invalid" in the WebAgents log file. We are using a RSA agent to protect the WebLogic.
The client side certificate is being asked by this agent but not from the weblogic. i.e the parameter "Client Certificate Enforced" is not set.
So if any of you could help out with the problem it would be of great help.
21 years ago
Hi All,
I have heard that it is possible with Weblogic 6.0 to have transactions across 2 databses. Can anyone throw some light on this. I am thinking of a transaction across Oracle and Sybase, can anyone suggest the way to do this in Weblogic 6.0.
Subendu
22 years ago
Hi,
Just found this info on the net, thought would be useful.
Whats New in Version 6.1:
Support for SOAP and WSDL; includes J2EE Connector Architecture 1.0, an open solution for application integration; supports EJB 2.0, Servlet 2.3, and JSP 1.2; support for the latest XML parsing, transformation, Web Services, and standard support for JAXP 1.1, SAX V2.0, DOM Level 2, and W3C Schema; optional asynchronous I/O allows for maximum messaging throughput; the WebLogic/Tuxedo Connector delivers bi-directional connectivity with security between WebLogic Server and Tuxedo, and transaction propagation from WebLogic Server to Tuxedo support for Oracle 8.1.7, with support for BLOB and CLOB data types; EJB caching improvements; all documentation, messages and tools are available in Japanese.
Subendu
22 years ago
Hi Avinash,
I am not sure about the features in Weblogic6.1 aver 6.0 , but you can go to this link and get some info.
http://www.beasys.com/products/weblogic/server/whatsnew.shtml
Subendu
22 years ago
Hi,
Here are some of the enhancements in Weblogic6.0 :
WebLogic Server 6.0 contains the following new features:
Enterprise Messaging Platform � BEA WebLogic Server extends the
platform to include high-volume messaging based on Java
Messaging Service (JMS).
Integrated XML Support � Leverage Extensible Markup Language
(XML) capabilities for B2B, EAI, and presentation services.
Enterprise JavaBeans (EJB) 2.0 with Message Driven Beans and
Advanced Container Managed Persistence -- Take a look into the
future of Enterprise Java (J2EE) with BEA's EJB 2.0
implementation.
Distributed Transaction Management � The new transaction
manager, leveraging BEA's expertise with BEA Tuxedo�, gives
developers the ability to do complex, distributed transactions
from Java-based applications.
New Web-based System Management � New management and usability
features greatly enhance administrator and developer
productivity. These features dramatically improve every aspect
of the application lifecycle - from installation, to
configuration, development, deployment and management.
J2EE Certification - Certification assures enterprises and
developers alike that APIs and development features will work in
a uniform way.
Web and Object Clustering Enhancements � BEA WebLogic Server 6.0
extends the clustering architecture to improve scalability and
high availability.
Web Server Enhancements � BEA WebLogic Server 6.0 eliminates the
requirement for a separate Web server with a powerful and
tightly integrated Web/application server architecture.
Security Enhancements � BEA WebLogic Server 6.0 offers new
security features including denial of service protection and
improved administration.
Internationalization � BEA WebLogic Server 6.0 can support
virtually any language , including double-byte character-set languages like Japanese kanji
Database Multipools � You have always been able to setup jdbc connection pools in WLS, but in 6.0 they allow you to setup a meta pool. You would normally setup your architecture so that you have replicated database servers, and then the pool points to both servers (e.g. Oracle replication). Then if the main oracle instance dies, the multipool will failover to the backup instance.
Solid transaction support (Two Phase Commit) -- BEA got the transaction gurus from Tuxedo, and built full XA compliant 2PC transactional support into WLS 6.0.
No more weblogic.class.path � Again, if you are used to WLS 5.1 and below you will have run into problems when you didn't setup your weblogic.class.path, CLASSPATH, and/or servlet.class.path correctly. The nasty "ClassCastException" can glare at you if you are not careful. Now JDK1.3 is out, it allows WLS to disgard it's
hack with multiple classloaders, and we are left with one CLASSPATH.
WLS forces you to use 1.3 and above for the server.
Central Admin Server -> Managed Server -- WLS 6.0 has changed it's configuration architecture to come closer to BEA Tuxedo. You have an admin server that holds the configuration for all servers in a given "domain". When you start up the managed servers, they point to the admin and get their config, and code sent over to them. This allows you to centralize your configuration, instead of having properties files all over the network.
Stateful Session In-memory replication -- WebLogic clustering has been improved in 6.0. You can now cluster stateful session beans using in-memory replication. The server that holds the state will replicate it to a backup server. If the primary goes down you will be routed across to the backup. Then the backup will become the primary and choose another server as its backup.
22 years ago