NSAPI [iPlanet 6.0SP1] for WLS6.1 SP1

Hi,
I am trying to integrate iPlanet WebServer 6.0 SP1 with Weblogic6.1 SP1 but am
not able to get it up and running. I followed the documentation and able to get
the ststic HTML pages but am not able to get the JSP's and Servlets to work. Here
are the steps I followed, can anyone help me out.
Thanks in advance
Ravi
1. Copy “proxy36.dll” located in the “<weblogic_home>/bin”
directory to “<Netscape_Home>/Servers/Plugins/” directory.
2. Modify “Magnus.conf” file.
Add following two lines at the top of the file after the comments.
>Init fn="load-modules" funcs="wl-proxy,wl-init"\ shlib="C:/Netscape/Server4/plugins/proxy36.dll"
Init fn="wl-init"
3.Modify “obj.conf” file. Add the following lines
<Object name="weblogic" ppath="*/weblogic/*">
Service fn="wl-proxy" WebLogicHost=<IPAddress of WLS Server>WebLogicPort="Port#"
PathTrim="/weblogic"
</Object>
4.Apply changes and Stop/Start the iPlanet Server.
6.Create subfolder called “my_apps” under “<NETSCAPE_HOME>/docs/”.
Move the contents of the “<WEBLOGIC_HOME>/public-html/my_apps” folder
to this folder.
7.Modify “myapps.properties” located in “<WEBLOGIC_HOME>/MyDomain/myappsproperties”
and modify the “web_server_url” and “web_server_ip” to
indicate the URL of the webserver
web_server_url=http://<iPlanetHostname>:port/weblogic/
web_server_ip= http://<iPlanetHostname>:port
8. Restart WebLogic Server
9. Restart iPlanet Enterprise Server

Hi,
My previous request might have been misleading, i found that it is not just images that don't work but all the resources deployed in apache with the webconnector to iplanet do not work if there is a query string attached to it.
for eg., http://<host>/home/index.html?user=username does not work either.
Thanks
Prashanth Sukumaran.

Similar Messages

Is there a Bug or Bug Fix in iPlanet 4.1 for URL Forwarding???

Here's the issue...
We are forwarding a number of URL's from one website to another.
When we create these under the iPlanet Web Server Admin UI, the URL's appear, and get written to obj.conf, and the Web Server appears to "Save and Apply" the changes, effectively restarting the Solaris Process ID.
The problem is that the httpd process does not actually restart, and the URL forwards return a 404.
If we manually restart the Web Server daemon, everything appears to funtion properly.
I have been searching through the iPlanet Knowledge Base, and not haveing any luck, so I am hoping someone here may have an idea.
Thanks!

Hi,
Please let me know your iWS version including service pack(example:4.1sp7)and OS version. So that i can test it and let you know the feedback.
Is there a Bug or Bug Fix in iPlanet 4.1 for URL Forwarding???
yes is there, but related to NSAPI please check the below link.
http://docs.iplanet.com/docs/manuals/enterprise/41/rn41sp9.html#26930
Thanks,
Daks.

OptimizeIt 4.11 and iPlanet 6.0sp1

Hi,
has anyone successfully configured OptIt 4.11 to work with iPlanet 6.0sp1?
The instructions presented in iPlanet's documentation..
http://docs.iplanet.com/docs/manuals/enterprise/50/servlets/xprof.htm#22740
... are a bit vague, and the server simply refuses to start with absolutely
nothing in the error log. If I remove the -Xrunoii option, and replace it
with -Xbootclasspath/a:/usr/local/OptimizeItSuite/lib/oibcp.jar, the server
starts ok, but with the following error..
warning ( 1186): Attempt to start OptimizeIT failed (exception: unknown
exception,no description)
While starting the server, it does print out stuff from OptIt, so there must
be some kind of connection between them:
OptimizeIt Profiler 4.11 build 442 Audit System.
(c) 1997, 1998, 1999, 2000, 2001 VMGEAR.
Port is 1470
Although that port 1470 cannot be accessed as the OptIt didn't start
successfully.
Does this seem familiar to anyone?
cheers,
Juha

wryteralways wrote:
My software update wants to download and install 10.4.11, but I want to make sure my Appleworks 6.2.9 will still work before I install the update because I have no desire want so ever to move to iWorks etc. which are just far inferior to Appleworks for my uses.
The AppleWorks 6.2.9 Update will do absolutely nothing on your already installed AppleWorks 6.2.9.
Its task is to update old AppleWorks 6 versions (6.0 thru 6.2.8).
Yvan KOENIG (from FRANCE dimanche 3 août 2008 12:32:28)

Include directive in iplanet 6.0SP1

If I have a include directive
<%@ page contentType="text/xml; charset=UTF-8" %>
in jsp then it loads up fine in iplanet 6.0SP1 and shows Japanese characters.
However when I have the same directive in some declare.jsp and include declare.jsp in another jsp file like:
<%@ include file='/declare.jsp' %>
then the webserver doesn't take the utf-8 encoding and doesn't process japanese characters correctly.
Is this bug fixed in later versions of iplanet? Any help is appreciated.
Thanks
Ravi

This doesn't seem to be an error. This is may be because the maximum characters they allow is 4096 and anything above it might be truncated. Check with Sun Support may be they have a better answer.

IPlanet Web Server 6.0 SP1 bug new details

I have found more details regarding the iPlanet Web Server 6.0 SP1 web.xml
parsing errors:
It appears that in web.xml now the sequence of declaration of the elements
plays role!!!!
If I put <servlet-mapping> tag in the beginning, after that I cannot declare
any other <servlet> tag in
web.xml, but if I change the sequence, that is put the <servlet> tags and
than only one <servlet-mapping> tag
at the end than the parser works fine and the server runs.
This is more than strange behavior, because the declaration of the elements
should not be dependent on their sequence of declaration!!!.
Sincerely,
Petros Bezirganyan
3601 Magic Dr. Shallow Creek, apt. 406
SAN ANTONIO, TX 78229
Phone: (210) 340-4401
E-Mail: [email protected]
----------------------------------------------------------------

Dear All,
I want to finalize this problem.
This behavior is actually quite normal and follows from DTD declared at
http://java.sun.com/j2ee/dtds/web-app_2_2.dtd
That is the element <servlet> is listed prior to the element
<servlet-mapping>, so as we
know from DTD syntax, when elements are separated by commas in declaration,
their order is
essential.
So basically what happened, in iPlanet Web Server 6.0 SP1 the DTD
(http://java.sun.com/j2ee/dtds/web-app_2_2.dtd) has changed, so that is why
the old web.xml files, where the order of elements was different, became
invalid according to the new DTD, this is all the problem.
Thank you.
Petros
"Petros Bezirganyan" <[email protected]> wrote in message
news:9nt7vn$[email protected]..
I could find out that web.xml parsing (SAX) error occurs only if
<servlet-mapping> tag precedes any <servlet>
tag in Web deployment descriptor of iPlanet Web Server 6.0 SP1.
That is if I group all <servlet> tags in the beginning and then at the
bottom I group all the <servlet-mapping> tags,
the SAX parser works fine and the server starts.
In my previous messages I stated that we can have only one<servlet-mapping>
tag, this is not true, the problem was in a position of the tag's
declaration.
Sincerely,
Petros Bezirganyan
3601 Magic Dr. Shallow Creek, apt. 406
SAN ANTONIO, TX 78229
Phone: (210) 340-4401
E-Mail: [email protected]

Does iPlanet LDAP SDK for C, version 5.8 support TLS?

thanx!

"The Netscape LDAP SDK for C only supports SSL 3.0 and does not support the
Start Transport Layer Security (TLS) Operation."
-- from Netscape LDAP SDK for C 4.1
so, i want to know whether iPlanet LDAP SDK for C 5.08 support TLS?

Generating Self Signed Certificate for iPlanet Directory Server for testing

Hi Experts,
I am unable to find how to generate self signed certificate for iPlanet Directory Server for testing purpose. Actually what i mean is i want to connect to the iPlanet LDAP Server with LDAPS:// rather than LDAP:// for Secured LDAP Authentication. For this purpose How to create a Dummy Certificate to enable iPlanet Directory Server SSL. I searched in google but no help. Please provide me the solution how to test it.
Thanks in Advance,
Kalyan

Here's one I did earlier.
Refers to Solaris 10
SSL Security
add a new certificate that lasts for ten years (120 months).
stop the instance:
dsadm stop <instance>
Remove DS from smf control:
dsadm disable-service <instance>
Change Certificate Database Password:
dsadm set-flags <instance> cert-pwd-prompt=on
     Choose the new certificate database password:
     Confirm the new certificate database password:
Certificate database password successfully updated.
Restart the instance from the dscc:
DSCC -> start <instance>
Now add a new Certificate which lasts for ten years (120 months; -v 120):
`cd <instance_path>`
`certutil -S -d . -P slapd- -s "CN=<FQDN_server_name>" �n testcert �v 120 -t T,, -x`
     Enter Password or Pin for "NSS Certificate DB":
Stop the Instance.
On the DSCC Security -> Certificates tab:
     select option to "Do not Prompt for Password"
Restart the instance.
On the Security -> General tab, select the new certificate to use for ssl encryption
Restart the instance
Stop the instance
Put DS back into smf control:
dsadm enable-service <instance>
Check the smf:
svcs -a | grep ds
# svcs -a|grep ds
disabled Aug_16 svc:/application/sun/ds:default
online Aug_16 svc:/application/sun/ds:ds--var-opt-SUNWdsee-dscc6-dcc-ads
online 17:04:28 svc:/application/sun/ds:ds--var-opt-SUNWdsee-dsins1

Apache Plugin in linux for WLS6.0 sp1 and (?sp2?)

This message is a little long,
The following message is arranged in 4 parts where:
1. Conclusion and Sugestions.
2. Tests Environment
3. Simple plugin environment
4. Virtual Hosting with apache
Any comment and help will be welcome
Conclusion
The plug-in has not been tested and documented and therefore does not
work in the described environment. The plugin parameter needs to be :
1. Syntaxly rewieved. The parameters not starting with
WebLogic.... (like PathTrim, PathPrepend, ConnectTimeoutSecs,
ConnectRetrySecs, Debug, DebugConfigInfo, StatPath, ErrorPage,
HungServerRecoverSecs, Idempotent, CookieName,
DefaultFileName, MaxPostSize, MatchExpression, FileCaching,
SecureProxy, TrustedCAFile, RequireSSLHostMatch,
SSLHostMatchOID) are confusing and couyld be bug/problem
generators when adding other non BEA modules in apache. I
would suggest to have all the parameter starting with a common
root like WebLogic or Wls or something else deterministic
2. Better documented. The module parameters in Apache need to
get an action perimeter. For example the "LoadModule
weblogic_module" and "AddModule mod_weblogic.c" need to be
declared one time at the server level. But there no
indication for the others plugin parameters if they are
limited inside the sublocation where declared, i.e
<VirtualHost>, <location> <file>.....
3. Documented with configuration examples: The apache plugin is
interlinked with what is declared in the WLS server. I would
sugest to provide some examples on this matter. I.e how to
relate the Apache virtual hosting with or without the virtual
hosting in wls.
Test Environment
The tests described below has been done with the following system
environment.
Operating System:
RedHat 7.0 + glibc updates + network uodates, kernel level 2.2.17-14
RedHat 7.1 + updates, kernel 2.4.2-2
Java Level:
On the RedHat 7.0 system the default Java JVM provided in the BEA
distribution
On the RedHat 7.1 system the Sun JDK 1.3.1 for Linux
Apache: 1.3.19
DNS: one system called cordoba.paris.inetpc.com with 3 cnames added
(w1cordoba, w2cordoba, w3cordoba)
The Weblogic installtion is coming from a single reference system.
This system runs under RedHat 6.2 + latest update levels. The WebLogic
tree directory has been deployed in both systems and the JVM set in the
proper manner. Despite the well known problem with the default webapp
Wls 6.0 works fine and as expected. Default ports are used (7001).
The apache environment works fine too. In a single apache environment
and with the virtual hosting supporting the 3 cnames (w1cordoba,
w2cordoba, w3cordoba)
In both systems the behavior and and problems are equal.
Simple plugin environment
A single default web app runs under wls6.0. calling the wls60 thru the
URI: "http://cordoba:7001" works fines and the Welcome.html default page
is properly displayed. Similar tests have been done with a jsp page and
works fine too.
The httpd.conf file has been set has described in the documentation and
as follow:
LoadModule weblogic_module modules/mod_wl.so
WebLogicHost cordoba
WebLogicPort 7001
Debug ON
DebugConfigInfo ON
<location /wls>
SetHandler weblogic-handler
PathTrin /wls
</location>
Problem 1: When requesting the page using the URI: "http://cordoba/wls"
the answer from the couple apache/plugin is:
-1- In the netscape location entry fileld we get in return:
"http://cordoba/Welcome.html"
-2- The response from apache is "NOT FOUND The requested URL
/Welcome.html was not found on this server."
-3- When requesting the page using the URI: "http://cordoba:7001" the
return is properly rendered, and the Netscape Location entry field
gets: "http://cordoba:7001/Welcome.html"
-4- wlproxy.log contains:
Sun Jun 3 16:34:19 2001
================New Request: [GET /wls HTTP/1.0] =================
Sun Jun 3 16:34:19 2001 The request string is '/wls'
Sun Jun 3 16:34:19 2001 INFO: SSL is not configured
Sun Jun 3 16:34:19 2001 Now trying whatever is on the list;
ci->canUseSrvrList = 1
Sun Jun 3 16:34:19 2001 INFO: New NON-SSL URL
Sun Jun 3 16:34:19 2001 general list: trying connect to 'cordoba'/7001
Sun Jun 3 16:34:19 2001 Connected to cordoba:7001
Sun Jun 3 16:34:19 2001 INFO: sysSend 343
Sun Jun 3 16:34:19 2001 INFO: Reader::fill(): first=0 last=0
toRead=4096
Sun Jun 3 16:34:19 2001 parsed all headers OK
Sun Jun 3 16:34:19 2001 INFO: Reader::fill(): first=0 last=0
toRead=4096
Sun Jun 3 16:34:19 2001 INFO: Reader::fill(): first=0 last=0
toRead=4096
Sun Jun 3 16:34:19 2001 r->status=302 returning 0
Sun Jun 3 16:36:08 2001
================New Request: [GET /wls HTTP/1.0] =================
Sun Jun 3 16:36:08 2001 The request string is '/wls'
Sun Jun 3 16:36:08 2001 INFO: SSL is not configured
Sun Jun 3 16:36:08 2001 Now trying whatever is on the list;
ci->canUseSrvrList = 1
Sun Jun 3 16:36:08 2001 INFO: New NON-SSL URL
Sun Jun 3 16:36:08 2001 general list: trying connect to 'cordoba'/7001
Sun Jun 3 16:36:08 2001 Connected to cordoba:7001
Sun Jun 3 16:36:08 2001 INFO: sysSend 343
Sun Jun 3 16:36:08 2001 INFO: Reader::fill(): first=0 last=0
toRead=4096
Sun Jun 3 16:36:08 2001 parsed all headers OK
Sun Jun 3 16:36:08 2001 r->status=302 returning 0
Virtual Hosting with Apache
These tests aim to validate a production environment where an entry cell
of apache servers will serve static pages and route dynamic requests to
a set of WebLogic servers. From the Apache/Httpd point of view the
dispatch is done first at a virtual host level and then for each virtual
server, each different location will be served by one or multiple
weblogic servers. A try with Apache virtual hosts in where a reroute by
location or a full reroute has done the same results than stated in
"Simple plugin environment".
[att1.html]

Hi
I am trying to configure the following pattern:
->https->apache->SSL->weblogic
using the apache plugin that you provided from the distribution.
There is no way to let it work.
the apache site trying to connect to weblogic is a virtual host, follows the config
file.
Checking the DEbugDebug config monitor it I discover that SecureProxy it is OFF
istead of ON and checking the debug file I've got this message:
INFO: ssl is not activated..
It means that despite of SecureProxy set to ON, it is still working in clear.
I have the same behaviour using 6.0, SP1, SP2 and 6.1
(If there more documentation about it in 6.1, please let me know where!)
Please, anyone can send me documentation about it or help me???
# <-- Start XXXXX Virtual Host
<VirtualHost XXXXXX>
SSLEngine on
SSLCipherSuite ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL
SSLCertificateKeyFile XXXX
SSLCertificateFile XXXXX
<Location />
AddHandler weblogic-handler .jsp
</Location>
<IfModule mod_weblogic.c>
SecureProxy ON
RequireSSLHostMatch false
TrustedCAFile /ssl/certs/ca.pem
Debug ALL
DebugConfigInfo ON
WebLogicHost XXXXX
WebLogicPort XXXXX
ErrorPage /pm/private/frame_044_error_500.htm
MatchExpression *.jsp
</IfModule>
</VirtualHost>
# <-- End XXXXX Virtual Host
"Jong Lee" <[email protected]> wrote:
>
1. Syntaxly rewieved.
Worth considering for the next major release.
2. Better documented.
Yes, 6.1 release is doing a much better job of documentation!
The module parameters in Apache need to
get an action perimeter. For example the "LoadModule
weblogic_module" and "AddModule mod_weblogic.c" need to be
declared one time at the server level. If apxs is used to update the module, end user should not need
to worry about adding/changing these two lines.
But there no
indication for the others plugin parameters if they are
limited inside the sublocation where declared, i.e
<VirtualHost>, <location> <file>.....
3. Documented with configuration examples: The apache plugin
is
interlinked with what is declared in the WLS server. I would
sugest to provide some examples on this matter. I.e how to
relate the Apache virtual hosting with or without the virtual
hosting in wls.
Again, better on 6.1 docs.
Problem 1: When requesting the page using the URI: "http://cordoba/wls"
the answer from the couple apache/plugin is:
-1- In the netscape location entry fileld we get in return:
"http://cordoba/Welcome.html"
"DefaultFileName Welcome.html" should be used in your httpd.conf
-2- The response from apache is "NOT FOUND The requested URL
/Welcome.html was not found on this server."
-3- When requesting the page using the URI: "http://cordoba:7001" the
return is properly rendered, and the Netscape Location entry field
gets: "http://cordoba:7001/Welcome.html"
-4- wlproxy.log contains:on 6.1, if relative URI is used in sendRedirect(), PathTrim and
PathPrepend should be taken care automatically. i.e:
in httpd.conf:
PathTrim /weblogic
PathPrepend /abc
in a jsp page:
response.sendRedirect("HelloWorld.jsp");
The plugin and wls will be smart enough to set Location header
to the following:
Location: http://apache_host:apache_port/weblogic/HelloWorld.jsp
Then the plugin will trim the /weblogic and prepend /abc to it
i.e:
http://wls_host:wls_port/abc/HelloWorld.jsp
Virtual Hosting with Apache
These tests aim to validate a production environment where an entrycell
of apache servers will serve static pages and route dynamic requests
to
a set of WebLogic servers. From the Apache/Httpd point of view the
dispatch is done first at a virtual host level and then for each virtual
server, each different location will be served by one or multiple
weblogic servers. A try with Apache virtual hosts in where a reroute
by
location or a full reroute has done the same results than stated in
"Simple plugin environment".Absolutely. in 6.1 you can specify different weblogic hosts per
vhost. Even you can use MatchExresspion or <Location> to define
different parameters per mime type and path:
i.e:
MatchExpression *.jsp WebLogicHost=www.bea.com|WebLogicPort=7001|DefaultFileName=/Welcome.html
MatchExpression *.html WebLogicCluster=weblogic1:7001,weblogic2:7002|Debug=ALL
<Location /weblogic>
WebLogicHost thankyou.com
</Location>
Where Location takes the precedence.
Anyway, 6.1 apache plugin should be a much better modules.
We also support apache2.0(beta) in 6.1. Unfortunately,
the apache2.0 binaries were unable to be included in the 6.1
beta installer. There might be a separate down-load for that.
Thank you for your great suggestions/comments.
thanks
Jong

IPlanet Plug in For WebLogic 5.1 SP9

At the client site we are using PeopleSoft 8.3, Weblogic 5.1 SP9 with iPlanet proxy
servers. The client is using 5.1ps6a plugin. The application does not function
with this plug in. The client has another plugin 6.1sp4 with that WL5.1 Sp 9
gives NASAPI plugin errror that follows:
Message from the NSAPI plugin:
No backend server available for connection: timed out after 10 seconds.
Build date/time: Sep 18 2002 16:55:57
Change Number: 208523
My questions, do BEA has 5.1Sp9 plugin?
Why NSAPI plugin errors while using 6.1sp4 plugin?
What else would fix the problem:
Thanks

A first step will be to enable logging for the proxy plugin. You do
this by adding the line Debug=ON in the obj.conf server directive.
Verify your steps in the following doc:
http://www.weblogic.com/docs51/admindocs/nsapi.html
This Debug creates a file /tmp/wlproxy.log. This file will help you
troubleshoot the issue for proxy-plugin for the 5.1 and 6.1 instances.
Post the log file and lets see what happens...
Good luck,
abdul
[email protected]
"Vidya Sagar" <[email protected]> wrote in message news:<3ea42831$[email protected]>...
At the client site we are using PeopleSoft 8.3, Weblogic 5.1 SP9 with iPlanet proxy
servers. The client is using 5.1ps6a plugin. The application does not function
with this plug in. The client has another plugin 6.1sp4 with that WL5.1 Sp 9
gives NASAPI plugin errror that follows:
Message from the NSAPI plugin:
No backend server available for connection: timed out after 10 seconds.
Build date/time: Sep 18 2002 16:55:57
Change Number: 208523
My questions, do BEA has 5.1Sp9 plugin?
Why NSAPI plugin errors while using 6.1sp4 plugin?
What else would fix the problem:
Thanks

Can iDSIE (Meta-directory) be used as a single authentication point from iPlanet Web Server for multiple databases using direct "or" indirect connectors?

Basically, the latest release of iPlanet Web Server forces the user/group information source to be an LDAP database. Currently, the user accounts are in Active Directory, NT, Oracle and NetWare Directory Service in this heterogeneous environment.
What I am looking for is a meta-directory product which can do two things:
1-Single authentiation point for users in mulitple databases from iPlanet Web Server.
2-Single administration point for all of the databases listed above.
For example, can I add/modify/delete a user account at the meta-directory level and have this propagate to all of the databases listed above reducing the administration to one meta-directory product?

With an Virtual Directory solution, you can authenticate Iplanet Web Server against nearly anything including any LDAPv3 Directory Server, Microsoft Active Directory, Windows NT Domains, Oracle RDBMS, IBM DB2 RDBMS, Microsoft SQL, and others.
All of this is done dynamically and doesn't require any heavyweight synchronization process. The Virtual Directory acts as a dynamic schema / DIT / data translation engine for different types of repositories.
OctetString's Virtual Directory Engine is one such example. You can download a 30 day evaluation copy at:
http://www.octetstring.com
It will take you all of 30 minutes to get iPlanet Web Server authenticated against and using groups from things like Oracle RDBMS, Windows NT Domains, or Active Directory.

5.1 version EAR built for WLS6.1

Hello all,
I have posted this in this ng before, but havent got a reply yet. I hope
somebody can help, cos I havent been able to progress further because of
this problem.
Im trying to install a EAR file built for EJB 1.1 spec on to WLS
6.1.3(running on Win2K Prof, with Oracle 8.1.7).
There are 2 problems:
1. I havent been able to succesfully deploy my ear file on WLS6.1 with
XADrivers. The cmp beans do not deploy. They fail with the following
exception :
Unable to deploy EJB: EntityBeanA from ejbJars.jar:
The Container-Managed Persistence Entity EJB failed while creating its SQL
TypeMap. The error was: null, Exception = null
Having experimented with a large number of configuration parameters for the
connection pool and TXdatasources, I finally have this in my config
file,which Ibelieve is right :
<JDBCTxDataSource EnableTwoPhaseCommit="false"
JNDIName="weblogic.jdbc.jts.default.eBanking" Name="eBankDs"
PoolName="eBanking" Targets="myserver"/>
<JDBCConnectionPool DriverName="weblogic.jdbc.oci.xa.XADataSource"
Name="eBanking"
Properties="user=ebank120;password=ebank120;dataSourceName=eBankDs;serverNam
e=ICARUS.EBANKING"
SupportsLocalTransaction="true" Targets="myserver"
TestTableName="bankusers"/>
Not that this works either..
2. So I have arrived at the (erroneous?) conclusion that something's wrong
with my application's descriptors. Im attempting to create an EJB1.1 bean
with WLS6.1 weblogic-ejb-jar and weblogic-cmp-rdbms-jar xml files.
2.1. Is this combination valid?
2.2 Ii try to run ejbc on such a jar file with one test bean (with an
ejb1.1 ejb-jar.xml and WLS 6.1 weblogic-ejb-jar.xml and wls6.1
weblogic-cmp-rdbms-jar.xml).
2.2.1 The weblogic-ejb-jar has the type-version tag as 5.1.0. I get
the following errors :
ERROR: Error from ejbc: Error while reading
'META-INF/weblogic-cmp-rdbms-jar.xml'. The error was: while processing
weblogic-rdbms-bean.xml file: encountered an unexpected version of xml
file. Make sure that your weblogic-rdbms-bean.xml file is the correct
version (e.g. a common error is to use a 6.0.0 CMP20 cmp xml file on a
5.1.0CMP11 Bean). Got xml processor:
weblogic.ejb20.dd.xml.WebLogicEjbJarLoader_WLS600
2.2.2 The weblogic-ejb-jar has the type-version tag as 6.0. I get
the following errors :
ERROR: Error from ejbc: Error while deploying EJB 'Ctpaclxrf'. The bean is
using container managed persistence version 1.x, but the bean's persistence
type is
using version 2.x. The types must be the same. ERROR: ejbc found errors
So Im at a loss currently. Nothing seems to be working. Im sorry for the
long post, but I'd be very grateful if somebody could help. Any help at all
is very welcome.
Thanks and regards,
Pavan

EJB 1.1 to EJB 2.0 conversion
http://e-docs.bea.com/wls/docs61/notes/migrate.html#1078938
pavan wrote:
Hello all,
I have posted this in this ng before, but havent got a reply yet. I hope
somebody can help, cos I havent been able to progress further because of
this problem.
Im trying to install a EAR file built for EJB 1.1 spec on to WLS
6.1.3(running on Win2K Prof, with Oracle 8.1.7).
There are 2 problems:
1. I havent been able to succesfully deploy my ear file on WLS6.1 with
XADrivers. The cmp beans do not deploy. They fail with the following
exception :
Unable to deploy EJB: EntityBeanA from ejbJars.jar:
The Container-Managed Persistence Entity EJB failed while creating its SQL
TypeMap. The error was: null, Exception = null
Having experimented with a large number of configuration parameters for the
connection pool and TXdatasources, I finally have this in my config
file,which Ibelieve is right :
<JDBCTxDataSource EnableTwoPhaseCommit="false"
JNDIName="weblogic.jdbc.jts.default.eBanking" Name="eBankDs"
PoolName="eBanking" Targets="myserver"/>
<JDBCConnectionPool DriverName="weblogic.jdbc.oci.xa.XADataSource"
Name="eBanking"
Properties="user=ebank120;password=ebank120;dataSourceName=eBankDs;serverNam
e=ICARUS.EBANKING"
SupportsLocalTransaction="true" Targets="myserver"
TestTableName="bankusers"/>
Not that this works either..
2. So I have arrived at the (erroneous?) conclusion that something's wrong
with my application's descriptors. Im attempting to create an EJB1.1 bean
with WLS6.1 weblogic-ejb-jar and weblogic-cmp-rdbms-jar xml files.
2.1. Is this combination valid?
2.2 Ii try to run ejbc on such a jar file with one test bean (with an
ejb1.1 ejb-jar.xml and WLS 6.1 weblogic-ejb-jar.xml and wls6.1
weblogic-cmp-rdbms-jar.xml).
2.2.1 The weblogic-ejb-jar has the type-version tag as 5.1.0. I get
the following errors :
ERROR: Error from ejbc: Error while reading
'META-INF/weblogic-cmp-rdbms-jar.xml'. The error was: while processing
weblogic-rdbms-bean.xml file: encountered an unexpected version of xml
file. Make sure that your weblogic-rdbms-bean.xml file is the correct
version (e.g. a common error is to use a 6.0.0 CMP20 cmp xml file on a
5.1.0CMP11 Bean). Got xml processor:
weblogic.ejb20.dd.xml.WebLogicEjbJarLoader_WLS600
2.2.2 The weblogic-ejb-jar has the type-version tag as 6.0. I get
the following errors :
ERROR: Error from ejbc: Error while deploying EJB 'Ctpaclxrf'. The bean is
using container managed persistence version 1.x, but the bean's persistence
type is
using version 2.x. The types must be the same. ERROR: ejbc found errors
So Im at a loss currently. Nothing seems to be working. Im sorry for the
long post, but I'd be very grateful if somebody could help. Any help at all
is very welcome.
Thanks and regards,
Pavan

IPlanet migration failure for Sun One Web server 6.1SP6

Recently we downloaded the Sun One Web server 6.1SP6 and we are having problem trying to upgrade our current version. We have been able to install the package and get the admin console running but we can not migrate the current instances across to the new version. We can successfully choose an instance to migrate however once we click the migrate button, absolutely nothing happens in the browser and nothing can be seen in any error logs and truss indicates a read of a pipe going nowhere, after which the cgi stub terminates.
We are migrating from
iPlanet-WebServer-Enterprise/6.0SP5 B10/31/2002 16:22
to
CORE1116: Sun ONE Web Server 6.1SP6 B05/07/2006 12:33

well, it is good that you have considered to upgrade considering 6.0 Sp5 has been EOL'ed for some time now.
here is the url that describes migrating to 6.1 from 6.0
http://docs.sfbay/app/docs/doc/819-6514/6n8h9dr61?a=view
now, if you are still having issues with migration using GUI, you can provide us the admin server error logs or call Sun tech support (if you have support contract) to help you with this.

Unable to set-up sybase connection pool for wls6.1

Hi All,
I am trying to set-up sybase connection pool in wls6.1 using the supplied jConnect driver (don't know the version of the driver). In diff places I am seeing diff opinions about the settings. It is really frustrating because BEA doc shies away from documenting just the sybase details although it provides details about Oracle, informix and SQL Server.
I just want to know these
1. the xml string for the connection pool
2. which config file should have it (web.xml or config.xml or something else?)
thanks a ton in advance
~rakesh

Hi,
I've already solve the problem. I did the following:
set the Url to be: jdbc:oracle:thin:@hostname:port:SID
set username
set password
add oracle.jdbc.drivers.OracleDriver into the JVM options -Djdbc.drivers
restart the server
test the connection
it works :)

Sample of weblogic.policy for WLS6.0

Dear all,
I had installed WLS6.0 on Solaris 2.6 and try to turn on
java security manager with this option
-Djava.security.policy==/usr/home/bea/wlserver6.0/lib/
weblogic.policy -Djava.security.manager
This make me unable to boot WLS. Here is contents of my weblogic.policy
grant {
// Permission "enableSubstitution" needed to run the WebLogic console
permission java.io.SerializablePermission "enableSubstitution";
// Permission "modifyThreadGroup" required to run the WebLogic Server
permission java.lang.RuntimePermission "modifyThreadGroup";
permission java.lang.RuntimePermission "setContextClassLoader";
// Permission "setIO" needed to start a server from the WebLogic console
permission java.lang.RuntimePermission "setIO";
// Permission "getClassLoader" needed for many EJB clients
permission java.lang.RuntimePermission "getClassLoader";
permission java.lang.RuntimePermission "stopThread";
permission java.net.SocketPermission "localhost:1024-", "listen";
permission java.util.PropertyPermission "*", "read,write";
permission java.io.FilePermission "${/}usr${/}home${/}bea${/}wlserver6.0${/}-",
"read,write,delete,execute";
And here is the error occurs
java.security.AccessControlException: access denied (java.io.FilePermission /usr/home/bea/wlserver6.0
read)
at java.security.AccessControlContext.checkPermission(AccessControlContext.java:272)
at java.security.AccessController.checkPermission(AccessController.java:399)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:545)
at java.lang.SecurityManager.checkRead(SecurityManager.java:890)
at java.io.File.exists(File.java:535)
at weblogic.utils.classloaders.ClasspathClassFinder.<init>(ClasspathClassFinder.java:61)
at weblogic.Home.getFileSource(Home.java:64)
at weblogic.Home.<init>(Home.java:29)
at weblogic.Home.getInstance(Home.java:82)
at weblogic.Home.getPath(Home.java:90)
at weblogic.security.internal.ServerAuthenticate.main(ServerAuthenticate.java:76)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:167)
at weblogic.Server.main(Server.java:35)
Could anyone give me what goes wrong. If you have a working version of weblogic.policy,
please share with me.
Regards,
Khemchart

Here's a snippet from upcoming release notes about the Java
security manager and the example weblogic.policy file.
Using the Java Security Manager with WebLogic Server
When you run WebLogic Server under Java 2 (JDK 1.2 or 1.3), WebLogic
Server can use the Java Security Manager in Java 2 to provide
additional access control for WebLogic Server resources. The Java
Virtual Machine (JVM) has security mechanisms built into it which can
be managed via a security policy file. The Java Security Manager can
enforce a set of permissions granted to CodeSource or SignedBy
classes. The permissions allow certain classes running in that
instance of the JVM to do or not do certain runtime operations. In
many cases, where the threat model does not include malicious code
being run on the JVM, the Java Security Manager is unnecessary. In
cases such as when an Application Service Provider uses WebLogic
Server and unknown classes are being run, the Java Security Manager is
necessary. To use the Java Security Manager with WebLogic Server,
specify the -Djava.security.manager property when starting WebLogic
Server.
Note: In past releases of WebLogic Server, the Java Security Manager
was enabled by using the -Dweblogic.security.manager property when
starting WebLogic Server. Please note the change in the property for
WebLogic Server version 6.0 and greater.
The Java Security Manager uses a security policy file that defines
permissions. The full pathname of security policy is specified in the
-Djava.security.policy property when starting WebLogic Server. If you
enable the Java Security Manager but do not specify a security policy
file, the Java Security Manager uses the default security policies
defined in the java.security and java.policy files in the
$JAVA_HOME/lib/security directory.
WebLogic Server includes an example security policy file named
weblogic.policy. This file contains a set of default permissions.
You need to make the following edits to the file in order to use the
file with your WebLogic Server deployment.
1. Edit the following lines in the weblogic.policy file, replacing the
specified location with the location of your WebLogic Server
installation:
grant codebase "file://BEA/-"{
permission java.io.FilePermission "D:${/}BEA${/}=", ...
Note: This change assumes your installation directory structure is the
same as the one described in the BEA Home Directory topic in the BEA
WebLogic Server Installation Guide.
2. If you want to run the Administration Console, add the following
grant block and permissions to the weblogic.policy file:
grant {
     permission java.io.FilePermission
"D:{/}BEA${/}wlserver600${/}weblogic${/}management${/}console${/}-",
"read";
     permission java.io.FilePermission
"D:{/}BEA${/}wlserver600${/}config${/}mydomain${/}applications${/}.wl_te\
mp_do_not_delete${/}weblogic${/}management${/}console${/}-", "read";
     permission java.util.PropertyPermission "user.*", "read";
3. If you have extra directories in your CLASSPATH or if you are
deploying applications in extra directories, you need to add specific
permissions for those directories to your weblogic.policy file.
BEA also recommends taking the following precautions:
? Make a backup copy of the weblogic.policy file and put the backup
copy in a secure location.
? Set the permissions on the weblogic.policy file such that the
adminstrator of the WebLogic Server deployment has write and read
privileges and no other users
To use the Java Security Manager and the weblogic.policy file with
your WebLogic Server deployment, use the following properties when
starting WebLogic Server:
$java... -Djava.security.manager \
-Djava.security.policy==D:/BEA/wlserver600/lib/weblogic.policy
For more information about the Java Security Manager, see the Javadoc
shipped with Java 2.
The RecordingSecurityManager utility can be used to detect permission
problems that occur when starting and running WebLogic Server. The
utility outputs permissions that can be added to your security policy
file to resolve the permission problems that the utility finds. The
RecordingSecurityManager is available at the BEA Developer's Center.

Is hotfix KB2275950 still valid for win7 sp1 64bit?

Hi All:
We tried to install Windows6.1-KB2275950-x64.msu on my win7 desktop (win7 sp1 64bit) to fix some DCOM/TLS issue,
We followed the instruction as below:
To use one of the hotfixes in this package, you must create a registry subkey. To do this, follow these steps:
Start Registry Editor.
Locate the following subkey in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LDAP
Create a new REG_DWORD value that is named UseHostnameAsAlias, and set the value to anything other than zero.
Exit Registry Editor, and then restart the computer.
however after restart pc, we failed to install this hotfix.
The error message is "The update is not applicable to your computer".
The error in setup of event viewer as below:
Windows update could not be installed because of error 2149842967 "" (Command line: ""C:\Windows\system32\wusa.exe" "C:\Downloads\Windows6.1-KB2275950-x64.msu" ")
is this hotfix still valid to windows 7 sp1 64bit?
thanks in advance.
fight for future!

Hi Mulder2008,
This Hotfix is only applied to Windows 7 Enterprise, Windows 7 Professional and Windows 7 Ultimate without Serveice pack 1.
Therefore it's indeed not valid to Windows 7 SP1.
Karen Hu
TechNet Community Support

NSAPI [iPlanet 6.0SP1] for WLS6.1 SP1

Similar Messages

Maybe you are looking for