URGENT ! Using Sun's J2EE RI Server with MS SQL Server 2000

I'm using the J2EE Server that comes with the J2EE 1.3.1 package from Sun. I'm trying to load a datasource using the free MS SQL Server 2000 Driver for JDBC, but I'm always getting this error (I've run out of ideas so maybe someone in this forum can help):
java.rmi.ServerException: RemoteException occurred in server thread; nested exception is: java.rmi.RemoteException: nested exception is: javax.ejb.EJBException: Unable to connect to database. No suitable driver; nested exception is: javax.ejb.EJBException: Unable to connect to database. No suitable driver ...
I'm using MS SQL Server 2000 Driver for JDBC, my classpath setting is:
CLASSPATH=D:\j2sdk1.4.0_01\jre\lib\ext\mysql-connector-j-2.0.14;D:\MS-JDBC-Driver\lib\msbase.jar;D:\MS-JDBC-Driver\lib\mssqlserver.jar;D:\MS-JDBC-Driver\lib\msutil.jar;E:\Installers\Java Related\jdbc dirvers\JSQLConnect3_27\JSQLConnect.jar
I have the same J2EE_CLASSPATH setting in my userconfig.bat file.
I've loaded this driver class in deploytool:
com.microsoft.jdbc.sqlserver.SQLServerDriver
and my connection url is:
jdbc:microsoft:sqlserver://localhost:1433;databasename=test
What's weird is that I've also tested these settings with a simple Java Application and they worked fine, but when I try to use the same for the j2ee server from sun, I always get the annoying "no suitable driver" error.
If anyone has ever come up with a solution that works, please help. You may post you reply here or better yet, email me at [email protected]
Thanks a lot in advance !

Hi,
The error "no suitable driver" occurs when something goes wrong with the connection URL.so make sure that u are using the correct URL format (check if any of the info is case sensitive etc) or atleast try other URL alternatives (for MS jdbc driver).
try these changes only through deployment tool->tools->server configuration->datasources->standard.(instead of editing resource.properties directly).
last not the least - make sure that there is NO "rem" keyword before "set J2EE_CLASSPATH" in the userconfig.bat file :)
HTH,
- asharafkk

Similar Messages

Install MS SQL Server Web Edition on a server with MS SQL Server Express

Hi,
We have a VPS cloud server on which there is an instance of SQL Server Express.
Since we need more resources, I consulted with the hosting provider and they offered us to use SQL Server Web Edition (SPLA Lisence).
My question is - the hosting company claims that it is not possible to keep the SQL Server Express instance along side with the SQL Server Web Edition, and that we must do ugrade and remove the SQL Server Express instance.
This will cause us a long downtime, since there are multiple DBs on the SQL Server Express that we will have to backup, and then restore them one by one on the Web Edition after it is installed.
Is this correct? Can't we install the SQL Server Web Edition Instance and gradually move the DBs to it?
Thanks!

The 50 instances per machine is a setup check rule as opposed to a hardware limitation. From this perspective, there would be no difference between a VM or a physical server.
In the line from the documentation that you referenced, the "stand-alone server" refers not to VM vs. Physical, but instead a stand-alone instance vs. a clustered instance. That is, in a non-clustered environment, you can have up to 50 instances.
In the past when I helped with setup testing and automation, we'd run VMs with 20-ish instances, including instances from 2012, 2008 R2, 2008, and 2005, including multiple editions (Enterprise, Standard, Express, Web, etc.).
One other potential option if your provider cannot support multiple instances is to do an in-place upgrade (edition upgrade) of your existing Express instance. This would retain the current instance and upgrade the existing instance from Express
to Web without the need to migrate databases. Here is more info on the supported version and edition upgrade paths (including Express to Web):
http://technet.microsoft.com/en-us/library/ms143393.aspx
Thanks,
Sam Lester (MSFT)
http://blogs.msdn.com/b/samlester
This posting is provided "AS IS" with no warranties, and confers no rights. Please remember to click
"Mark as Answer" and
"Vote as Helpful" on posts that help you. This can be beneficial to other community members reading the thread.

Issues using BitLocker in Windows 8 Emedded with 2012 SQL Server Express

I was told that this forum may be able to help me with my issues (see original thread here:
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/8c81fde1-e91b-46eb-8d2f-b79426805ddd/using-sql-server-2012-express-with-bitocker?forum=sqlexpress).
Background:
To summarize, I have an OS that is partitioned into two volumes: C and D.
C drive contains the running software, SQL Server install, and the OS.
D drive is the encrypted partition via BitLocker. The SQL Server files are stored here (logs, backup, and mdf).
Problem:
The software cannot connect to the database stored on the encrypted D volume when BitLocker is turned on. The user account that I use to enable BitLocker is the same SQL Server Service account and has is also part of the Local Admin Group. As soon as I disable
BitLocker, the software works fine and the database connection succeeds. I am currently using the SQL System Admin account to login (SA) and BitLocker is being used with a TPM.
The error I am experiencing when connecting through the software is 'login
failed for user sa'.
Thank you for the suggestions/help.

Hi HMLunger,
Did you install the SQL Server instance successfully? If not, please help to post the summary and detail logs for analysis. By default, the logs can be found in: C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log.
However, if you fail to start SQL Server Express service after successfully installing SQL Server,
you might have to change the paths of the files by running the following scripts from the command prompt. For more details, please review this similar
thread.
NET START MSSQL$SQLEXPRESS /f /T3608
SQLCMD -S .\SQLEXPRESS
ALTER DATABASE model MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
ALTER DATABASE model MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
go
exit;
ALTER DATABASE msdb MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
ALTER DATABASE msdb MODIFY FILE (NAME = logical_name , FILENAME = 'new_path\os_file_name');
NET STOP MSSQL$SQLEXPRESS
In addition, you can follow the steps in this KB article to uninstall SQL Server.
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support

Portal 4.0 with MS SQL Server 2000 using CLOBs

Hello,
I'm driving Portal 4.0 with MS SQL Server 2000. I have encountered serious
problems when trying to persist events (e.g. RuleEvent) to database. In my
application-config.xml file I have JdbcHelper attributes
ShouldUseClobsForReads & -Writes set to 'false' as they should be or
mssqlserver4v70 driver.
It seems that when it is time to write the event to database, Portal4.0
can't find JdbcHelper MBean configuration values and therefore it uses
default values (=true) for both attributes.
Otherwise reading and writing works fine with MS SQL Server 2000 (at least
DATA_SYNC_ITEMs).
Any help appreciated.
Regards,
JR
P.S.
Here are some excerpts from the console output:
[BufferManager$PersistenceRequest.execute():247]
PersistenceRequest::execute -> write to database
[AbstractDatabasePersister.persist():135] Persister::persist -> write the
events. size=2
*** com.bea.p13n.util.jdbc.JdbcHelper.getInstance() @ JdbcHelper.java:122
[JdbcHelper.getInstance():139] No instance found for
sun.misc.Launcher$AppClassLoader@71732b
[JdbcHelper.<init>():111] Unable to find JdbcHelper Configuration ...using
defaults: java.lang.IllegalStateException: Not in application context
at
com.bea.p13n.management.ApplicationHelper.getApplicationName(ApplicationHelp
er.java:119)
at
com.bea.p13n.management.ApplicationHelper.getApplicationConfigurationMBean(A
pplicationHelper.java:440)
at
com.bea.p13n.management.ApplicationHelper.getServiceConfigurationMBean(Appli
cationHelper.java:318)
at com.bea.p13n.util.jdbc.JdbcHelper.<init>(JdbcHelper.java:102)
at
com.bea.p13n.util.jdbc.JdbcHelper.getInstance(JdbcHelper.java:141)
at
com.bea.p13n.util.jdbc.JdbcHelper.getConnection(JdbcHelper.java:265)
at
com.bea.p13n.tracking.internal.persistence.AbstractDatabasePersister.getConn
ection(AbstractDatabasePersister.java:202)
at
com.bea.p13n.tracking.internal.persistence.AbstractDatabasePersister.persist
(AbstractDatabasePersister.java:140)
at
com.bea.p13n.tracking.internal.persistence.BufferManager$PersistenceRequest.
execute(BufferManager.java:250)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
*** com.bea.p13n.util.jdbc.JdbcHelper.getInstance() @ JdbcHelper.java:122
[JdbcHelper.getInstance():131] Got instance for
sun.misc.Launcher$AppClassLoader@71732b
[JdbcHelper._setClob():412] ######## JdbcHelper: String length = 496
[JdbcHelper._setClob():420] ######## JdbcHelper: setting CLOB String with
setCharacterStream()
<7.1.2002 14:27:41 GMT+02:00> <Error> <Tracking> <Error persisting event to
database. java.sql.SQLException: java.sql.SQLException: This JDBC 2.0 method
is not implemented
at
weblogic.jdbc.rmi.SerialPreparedStatement.setCharacterStream(SerialPreparedS
tatement.java:428)
at com.bea.p13n.util.jdbc.JdbcHelper._setClob(JdbcHelper.java:424)
at com.bea.p13n.util.jdbc.JdbcHelper.setClob(JdbcHelper.java:404)
at
com.bea.p13n.tracking.internal.persistence.BehaviorTrackingPersister.setPrep
aredStatementData(BehaviorTrackingPersister.java:93)
at
com.bea.p13n.tracking.internal.persistence.AbstractDatabasePersister.persist
(AbstractDatabasePersister.java:157)
at
com.bea.p13n.tracking.internal.persistence.BufferManager$PersistenceRequest.
execute(BufferManager.java:250)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

Hi,
I would suggest better to have a backup of existing database remove your existing SQL server. Install the one given by SAP. And restore your previous databases.
--Ragu

Problem using DG4ODBC with named SQL Server instance

I am running DG4ODBC on a 64 bit LINUX machine with the Microsoft SQL Server driver installed. I have successfully tested this with a SQL Server instance that was not named (GENERALI_DSN).The named instance gives the following when trying to query:
ORA-28500: connection from ORACLE to a non-Oracle system returned this message:
[unixODBC][Microsoft][SQL Server Native Client 11.0]Login timeout expired {HYT00}[unixODBC][Microsoft][SQL Server Native Client 11.0]SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. {08001,NativeErr = -1}[unixODBC][Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online. {08001,NativeErr = -1}
ORA-02063: preceding 2 lines from DEVMISC
odbc.ini
[GENERALI_DSN]
Driver                  = SQL Server Native Client 11.0
Server                  = CLTDMJCWBYZ.eu.scor.local
User                    = everest
Password                = everest
Database                = Everest_Generali
[DEVMISC_DSN]
Driver                  = SQL Server Native Client 11.0
Server                  = [USVCLTDEVSQL02\DEVMISC]
User                    = link_user
Password                = password1
Database                = DBA
initDG4ODBC2.ora
# HS init parameters
HS_FDS_CONNECT_INFO = DEVMISC_DSN
HS_FDS_TRACE_LEVEL = DEBUG
HS_FDS_SHAREABLE_NAME = /usr/lib64/libodbc.so
# ODBC specific environment variables
set ODBCINI=/home/oracle/.odbc.ini
listener.ora
SID_LIST_LISTENER_GW =
   (SID_LIST =
      (SID_DESC =
       (SID_NAME=DG4ODBC)
      (ORACLE_HOME=/home/oracle/product/11.2.0)
      (ENV=LD_LIBRARY_PATH=/usr/lib64:/home/oracle/product/11.2.0/lib:/opt/micro
soft/sqlncli/lib)
      (PROGRAM=dg4odbc)
      (SID_DESC =
       (SID_NAME=DG4ODBC2)
      (ORACLE_HOME=/home/oracle/product/11.2.0)
      (ENVS=LD_LIBRARY_PATH=/usr/lib64:/home/oracle/product/11.2.0/lib:/opt/micr
osoft/sqlncli/lib)
      (PROGRAM=dg4odbc)
LISTENER_GW =
(DESCRIPTION_LIST =
    (DESCRIPTION =
      (ADDRESS = (PROTOCOL = TCP)(HOST = usvcltprdoragw)(PORT = 1521))
tnsnames.ora
DG4ODBC =
   (DESCRIPTION=
      (ADDRESS=(PROTOCOL=tcp)(HOST=usvcltprdoragw)(PORT=1521))
      (CONNECT_DATA=(SID=DG4ODBC))
      (HS=OK)
DG4ODBC2 =
   (DESCRIPTION=
      (ADDRESS=(PROTOCOL=tcp)(HOST=usvcltprdoragw)(PORT=1521))
      (CONNECT_DATA=(SID=DG4ODBC2))
      (HS=OK)
I can't figure out why the named instance does not work but the other one does. Any help would be greatly appreciated!

Did you check with the ODBC test utility isql (it is installed by default when you install the unixODBC Driver manager) if your ODBC driver can connect at all to that named instance? I have some doubts that it will work either as there was a blog commented by a MS engineer:
Introducing the new Microsoft ODBC Drivers for SQL Server - Microsoft SQLNCli team blog - Site Home - MSDN Blogs
who states that named instance connections are not supported using that driver.
- Klaus

XDK APIs (C/C++/Java) and tools can also be used with MS SQL Server

I want to know if XDK APIs (Java or C/C++ APIs especially) and tools can be used with MS SQL Server or not?
I want to write a simple application that updates XML ( acordXML used for insurance) document into SQL Server tables. Of course I am assuming to transform into appropriate XSU APIs format.

No. Use SQLXML instead on a SQL Server.

Anyone successfully set up connection pool in s1as with ms sql server 2000?

As subject. Since I have seen a lot of posts about the NoSuchMethodException issue with various dbms providers, and the only "official information" I found thru different forums, google, different sun/javasoft sites and forums are this:
http://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=fsunone%2F8172&zone_32=NoSuchMethodException&wholewords=on
Which is wonderfully vague and provide not-so-much useful information...
As for the information and suggestion posted by other forum members, most or all of them have experience with setting up Oracle, DB2, mySQL, etc., not aimed for MS SQL Server 2000 (you may think, I am just asking for it running MS SQL server with Java... oh well, not my choice)
I still haven't seen any positive feedbacks on how this exception was caused and how to resolve it. I have literally exhausted all leads on how to fix this issue, so right now I'm only interested to know whether anyone in the forum actually have a successful connection pool set up with MS SQL server 2000.
My platform:
w2k sp3
SunOne app server, update1, JDK 1.4.1
latest MS SQL 2000 JDBC driver
This fails with the NoSuchMethodException error:
try {
InitialContext ic = new InitialContext();
DataSource ds = (DataSource) ic.lookup("test_db");
con = ds.getConnection();
System.out.println( "con is created -> " + con );
} catch (Exception ex) {
System.out.println( "failed -> " + ex.getMessage() );
This works just fine:
try {
Class.forName("com.microsoft.jdbc.sqlserver.SQLServerDriver");
con = DriverManager.getConnection("jdbc:microsoft:sqlserver://xxx.xxx.xxx.xxx:1433;DatabaseName=testdb;SelectMethod=cursor", "username", "password");
System.out.println( "con is created -> " + con );
} catch (Exception ex) {
System.out.println( "failed is fucked -> " + ex.getMessage() );
thanks,
--kuan

Hi,
Thanks for pointing out that article, I did not find it previously. After following the directions in the artile and your advise, now dbping seems to be able to connect to SQL server.
Thank you very much.
--kuan

Problems configuring Platform Domain with MS Sql Server

Hi,
We are having problems configuring a Platform Domain with MS Sql Server 2000.
We are using Weblogic version 7.0.0.2. These are the steps we followed
1.We manually created a database called TestDB and created a user account called
"system", pwd ==>> "weblogic" in SQL server and assigned him as the DB owner for
the TestDB created.
2. Changed dbsettings_properties files (Commented pointbase entries and uncommented
SQL Server entries. I gave the connection parameter as connection=jdbc:weblogic:mssqlserver4:localhost:1433
in this file.
3. Modified Config.xml and changed properties for DataSyncPool, WLIPool, CommercePool,WLIPool
and modified the RDBMS realm properties to point to the database.
4. ran the create_db script and it seemed to have run fine looking at the log
file.
5. I then tried to start the BEA Server instance and I get the following error.
I am also attaching the config.xml file for reference.
Appreciate any help/suggestions. Thanks in Advance.
Vikram
<Apr 9, 2003 2:57:45 AM EDT> <Error> <RDBMSRealm> <000000> <An error occured cre
ating a database connection for the realm.
java.sql.SQLException: Invalid port: weblogic:mssqlserver4:localhost:1433
at weblogic.jdbc.mssqlserver4.ConnectionInfo.<init>(ConnectionInfo.java:
193)
at weblogic.jdbc.mssqlserver4.ConnectDriver.parse(ConnectDriver.java:333
at weblogic.jdbc.mssqlserver4.ConnectDriver.connect(ConnectDriver.java:1
02)
at com.bea.p13n.security.realm.RDBMSDelegate.<init>(RDBMSDelegate.java:1
69)
at com.bea.p13n.security.realm.RDBMSDelegate$DFactory.getInstance(RDBMSD
elegate.java:962)
at com.bea.p13n.security.realm.internal.Pool.<init>(Pool.java:53)
at com.bea.p13n.security.realm.RDBMSRealm.createPool(RDBMSRealm.java:153
at com.bea.p13n.security.realm.RDBMSRealm.<init>(RDBMSRealm.java:140)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:232)
at weblogic.security.acl.Realm.getRealm(Realm.java:87)
at weblogic.security.acl.Realm.getRealm(Realm.java:65)
at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
a:353)
at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
itialize(AuthorizationProviderImpl.java:72)
at weblogic.security.service.SecurityServiceManager.createSecurityProvid
er(SecurityServiceManager.java:1875)
at weblogic.security.service.AuthorizationManager.initialize(Authorizati
onManager.java:206)
at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
nager.java:127)
at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
eManager.java:1613)
at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
rityServiceManager.java:1426)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
rviceManager.java:1365)
at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
urityServiceManager.java:1487)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1207)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
>
<Apr 9, 2003 2:57:45 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
in
itialize the server: Fatal initialization exception
Throwable: java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.R
DBMSException: An error occured creating a database connection for the realm.]
java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
on: An error occured creating a database connection for the realm.]
at weblogic.security.acl.Realm.getRealm(Realm.java:94)
at weblogic.security.acl.Realm.getRealm(Realm.java:65)
at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
a:353)
at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
itialize(AuthorizationProviderImpl.java:72)
at weblogic.security.service.SecurityServiceManager.createSecurityProvid
er(SecurityServiceManager.java:1875)
at weblogic.security.service.AuthorizationManager.initialize(Authorizati
onManager.java:206)
at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
nager.java:127)
at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
eManager.java:1613)
at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
rityServiceManager.java:1426)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
rviceManager.java:1365)
at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
urityServiceManager.java:1487)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1207)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
>
The WebLogic Server did not start up properly.
Exception raised:
java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
on: An error occured creating a database connection for the realm.]
at weblogic.security.acl.Realm.getRealm(Realm.java:94)
at weblogic.security.acl.Realm.getRealm(Realm.java:65)
at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
a:353)
at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
itialize(AuthorizationProviderImpl.java:72)
at weblogic.security.service.SecurityServiceManager.createSecurityProvid
er(SecurityServiceManager.java:1875)
at weblogic.security.service.AuthorizationManager.initialize(Authorizati
onManager.java:206)
at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
nager.java:127)
at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
eManager.java:1613)
at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
rityServiceManager.java:1426)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
rviceManager.java:1365)
at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
urityServiceManager.java:1487)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1207)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
Reason: Fatal initialization exception
Throwable: java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.R
DBMSException: An error occured creating a database connection for the realm.]
java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
on: An error occured creating a database connection for the realm.]
at weblogic.security.acl.Realm.getRealm(Realm.java:94)
at weblogic.security.acl.Realm.getRealm(Realm.java:65)
at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
a:353)
at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
itialize(AuthorizationProviderImpl.java:72)
at weblogic.security.service.SecurityServiceManager.createSecurityProvid
er(SecurityServiceManager.java:1875)
at weblogic.security.service.AuthorizationManager.initialize(Authorizati
onManager.java:206)
at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
nager.java:127)
at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
eManager.java:1613)
at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
rityServiceManager.java:1426)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
rviceManager.java:1365)
at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
urityServiceManager.java:1487)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1207)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
[config.xml]

Try removing the server section from the SchemaProperties line.
Preferrably do not use localhost or hostnames in the server
configuration file.
<RDBMSRealm
Name="wlcsRealm"
DatabaseDriver="weblogic.jdbc.mssqlserver4.Driver"
DatabasePassword="weblogic"
DatabaseURL="jdbc:weblogic:mssqlserver4:yourIPAddress:1433"
RealmClassName="com.bea.p13n.security.realm.RDBMSRealm"
SchemaProperties="user=system;password=weblogic"/>
Also consider ...
If you have a new Portal database created in SQL Server?
Does the user system have the Portal database as his default database?
-- Jim
Vikram wrote:
Hi,
We are having problems configuring a Platform Domain with MS Sql Server 2000.
We are using Weblogic version 7.0.0.2. These are the steps we followed
1.We manually created a database called TestDB and created a user account called
"system", pwd ==>> "weblogic" in SQL server and assigned him as the DB owner for
the TestDB created.
2. Changed dbsettings_properties files (Commented pointbase entries and uncommented
SQL Server entries. I gave the connection parameter as connection=jdbc:weblogic:mssqlserver4:localhost:1433
in this file.
3. Modified Config.xml and changed properties for DataSyncPool, WLIPool, CommercePool,WLIPool
and modified the RDBMS realm properties to point to the database.
4. ran the create_db script and it seemed to have run fine looking at the log
file.
5. I then tried to start the BEA Server instance and I get the following error.
I am also attaching the config.xml file for reference.
Appreciate any help/suggestions. Thanks in Advance.
Vikram
<Apr 9, 2003 2:57:45 AM EDT> <Error> <RDBMSRealm> <000000> <An error occured cre
ating a database connection for the realm.
java.sql.SQLException: Invalid port: weblogic:mssqlserver4:localhost:1433
at weblogic.jdbc.mssqlserver4.ConnectionInfo.<init>(ConnectionInfo.java:
193)
at weblogic.jdbc.mssqlserver4.ConnectDriver.parse(ConnectDriver.java:333
at weblogic.jdbc.mssqlserver4.ConnectDriver.connect(ConnectDriver.java:1
02)
at com.bea.p13n.security.realm.RDBMSDelegate.<init>(RDBMSDelegate.java:1
69)
at com.bea.p13n.security.realm.RDBMSDelegate$DFactory.getInstance(RDBMSD
elegate.java:962)
at com.bea.p13n.security.realm.internal.Pool.<init>(Pool.java:53)
at com.bea.p13n.security.realm.RDBMSRealm.createPool(RDBMSRealm.java:153
at com.bea.p13n.security.realm.RDBMSRealm.<init>(RDBMSRealm.java:140)
at java.lang.Class.newInstance0(Native Method)
at java.lang.Class.newInstance(Class.java:232)
at weblogic.security.acl.Realm.getRealm(Realm.java:87)
at weblogic.security.acl.Realm.getRealm(Realm.java:65)
at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
a:353)
at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
itialize(AuthorizationProviderImpl.java:72)
at weblogic.security.service.SecurityServiceManager.createSecurityProvid
er(SecurityServiceManager.java:1875)
at weblogic.security.service.AuthorizationManager.initialize(Authorizati
onManager.java:206)
at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
nager.java:127)
at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
eManager.java:1613)
at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
rityServiceManager.java:1426)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
rviceManager.java:1365)
at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
urityServiceManager.java:1487)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1207)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
<Apr 9, 2003 2:57:45 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
in
itialize the server: Fatal initialization exception
Throwable: java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.R
DBMSException: An error occured creating a database connection for the realm.]
java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
on: An error occured creating a database connection for the realm.]
at weblogic.security.acl.Realm.getRealm(Realm.java:94)
at weblogic.security.acl.Realm.getRealm(Realm.java:65)
at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
a:353)
at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
itialize(AuthorizationProviderImpl.java:72)
at weblogic.security.service.SecurityServiceManager.createSecurityProvid
er(SecurityServiceManager.java:1875)
at weblogic.security.service.AuthorizationManager.initialize(Authorizati
onManager.java:206)
at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
nager.java:127)
at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
eManager.java:1613)
at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
rityServiceManager.java:1426)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
rviceManager.java:1365)
at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
urityServiceManager.java:1487)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1207)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
The WebLogic Server did not start up properly.
Exception raised:
java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
on: An error occured creating a database connection for the realm.]
at weblogic.security.acl.Realm.getRealm(Realm.java:94)
at weblogic.security.acl.Realm.getRealm(Realm.java:65)
at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
a:353)
at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
itialize(AuthorizationProviderImpl.java:72)
at weblogic.security.service.SecurityServiceManager.createSecurityProvid
er(SecurityServiceManager.java:1875)
at weblogic.security.service.AuthorizationManager.initialize(Authorizati
onManager.java:206)
at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
nager.java:127)
at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
eManager.java:1613)
at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
rityServiceManager.java:1426)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
rviceManager.java:1365)
at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
urityServiceManager.java:1487)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1207)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
Reason: Fatal initialization exception
Throwable: java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.R
DBMSException: An error occured creating a database connection for the realm.]
java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSExcepti
on: An error occured creating a database connection for the realm.]
at weblogic.security.acl.Realm.getRealm(Realm.java:94)
at weblogic.security.acl.Realm.getRealm(Realm.java:65)
at weblogic.security.SecurityService.initializeRealm(SecurityService.jav
a:353)
at weblogic.security.providers.realmadapter.AuthorizationProviderImpl.in
itialize(AuthorizationProviderImpl.java:72)
at weblogic.security.service.SecurityServiceManager.createSecurityProvid
er(SecurityServiceManager.java:1875)
at weblogic.security.service.AuthorizationManager.initialize(Authorizati
onManager.java:206)
at weblogic.security.service.AuthorizationManager.<init>(AuthorizationMa
nager.java:127)
at weblogic.security.service.SecurityServiceManager.doATZ(SecurityServic
eManager.java:1613)
at weblogic.security.service.SecurityServiceManager.initializeRealm(Secu
rityServiceManager.java:1426)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecuritySe
rviceManager.java:1365)
at weblogic.security.service.SecurityServiceManager.initializeRealms(Sec
urityServiceManager.java:1487)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:1207)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:723)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:594)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:282)
at weblogic.Server.main(Server.java:32)
<Domain Name="epmsDomain">
<Log
FileName="logs/wl-domain.log"
Name="epmsDomain"
/>

<Server
Name="platformServer"
     ListenAddress="localhost"
ListenPort="7501"
NativeIOEnabled="true"
TransactionLogFilePrefix="logs/"
>
<SSL
Name="platformServer"
ListenPort="7502"
Enabled="true"
ServerCertificateChainFileName="ca.pem"
ServerCertificateFileName="democert.pem"
ServerKeyFileName="demokey.pem"
/>
<Log
FileName="logs/weblogic.log"
/>
<WebServer
DefaultWebApp="splashPage"
LogFileName="./logs/access.log"
LoggingEnabled="true"
Name="platformServer"
/>
</Server>

<JDBCConnectionPool
Name="commercePool"
DriverName="weblogic.jdbc.mssqlserver4.Driver"
URL="jdbc:weblogic:mssqlserver4:localhost:1433"
Properties="user=system;password=weblogic;server=jdbc:weblogic:mssqlserver4:localhost:1433"
Password="weblogic"
InitialCapacity="20"
MaxCapacity="20"
CapacityIncrement="1"
RefreshMinutes="0"
ShrinkingEnabled="false"
Targets="platformServer"
TestConnectionsOnReserve="false"
TestTableName="WEBLOGIC_IS_ALIVE"
/>

<JDBCConnectionPool
CapacityIncrement="2"
DriverName="weblogic.jdbc.mssqlserver4.Driver"
InitialCapacity="8"
LoginDelaySeconds="1"
MaxCapacity="36"
Name="wliPool"
Properties="user=system;password=weblogic;server=jdbc:weblogic:mssqlserver4:localhost:1433"
Password="weblogic"
RefreshMinutes="0"
ShrinkPeriodMinutes="15"
ShrinkingEnabled="true"
Targets="platformServer"
URL="jdbc:weblogic:mssqlserver4:localhost:1433"
/>
<JDBCTxDataSource
EnableTwoPhaseCommit="false"
JNDIName="weblogic.jdbc.jts.commercePool"
Name="commercePool"
PoolName="commercePool"
Targets="platformServer"
/>
<JDBCDataSource
JNDIName="weblogic.jdbc.pool.commercePool"
Name="commercePool"
PoolName="commercePool"
Targets="platformServer"
/>
<JDBCDataSource
JNDIName="WLAI_DataSource"
Name="WLAI_DataSource"
PoolName="wliPool"
Targets="platformServer"
/>
<JDBCTxDataSource
EnableTwoPhaseCommit="true"
JNDIName="com.bea.wlpi.TXDataSource"
Name="TXDataSource"
PoolName="wliPool"
Targets="platformServer"
/>
<JDBCTxDataSource
EnableTwoPhaseCommit="true"
JNDIName="WLCHub.DS"
Name="WLCHub.DS"
PoolName="wliPool"
Targets="platformServer"/>
/>

<JDBCTxDataSource
     EnableTwoPhaseCommit="true"
JNDIName="cgDataSource"
Name="cgDataSource"
PoolName="commercePool"
Targets="platformServer"/>
<JDBCTxDataSource
EnableTwoPhaseCommit="true"
JNDIName="cgSampleDataSource"
Name="cgSampleDataSource"
PoolName="commercePool"
Targets="platformServer"/>
<JMSConnectionFactory JNDIName="weblogic.jws.jms.QueueConnectionFactory"
Name="cgQueue" Targets="platformServer"/>
<JMSJDBCStore ConnectionPool="commercePool" Name="cgJDBCStore" PrefixName="WEBLOGIC"/>
<JMSServer Name="cgJMSServer" Store="cgJDBCStore" Targets="platformServer">
<JMSQueue JNDIName="jws.queue" Name="cgJWSQueue" StoreEnabled="default"/>
</JMSServer>
<JTA Name="epmsDomain" TimeoutSeconds="3600"/>


<JDBCConnectionPool
Name="dataSyncPool"
DriverName="weblogic.jdbc.mssqlserver4.Driver"
URL="jdbc:weblogic:mssqlserver4:localhost:1433"
Properties="user=system;password=weblogic;server=jdbc:weblogic:mssqlserver4:localhost:1433"
Password="WEBLOGIC"
InitialCapacity="1"
MaxCapacity="5"
CapacityIncrement="1"
RefreshMinutes="0"
ShrinkingEnabled="false"
TestConnectionsOnReserve="false"
TestTableName="WEBLOGIC_IS_ALIVE"
Targets="platformServer"/>
/>
<JDBCTxDataSource
EnableTwoPhaseCommit="false"
JNDIName="weblogic.jdbc.jts.dataSyncPool"
Name="dataSyncPool"
PoolName="dataSyncPool"
Targets="platformServer"/>
/>

<Security
GuestDisabled="false"
Name="epmsDomain"
PasswordPolicy="wl_default_password_policy"
Realm="wl_default_realm"
CompatibilityMode="true"
/>
<PasswordPolicy
Name="wl_default_password_policy"
/>
<Realm
Name="wl_default_realm"
CachingRealm="wlcsCachingRealm"
FileRealm="wl_default_file_realm"
/>
<CachingRealm
BasicRealm="wlcsRealm"
CacheCaseSensitive="true"
Name="wlcsCachingRealm"
/>
<RDBMSRealm DatabaseDriver="weblogic.jdbc.mssqlserver4.Driver"
DatabasePassword="weblogic"
DatabaseURL="jdbc:weblogic:mssqlserver4:localhost:1433"
SchemaProperties="user=system;password=weblogic;server=jdbc:weblogic:mssqlserver4:localhost:1433"
Name="wlcsRealm"
RealmClassName="com.bea.p13n.security.realm.RDBMSRealm"/>
<FileRealm
Name="wl_default_file_realm"
/>
<StartupClass
ClassName="com.beasys.commerce.ebusiness.security.KeyBootstrap"
FailureIsFatal="false"
Name="KeyBootstrap"
Targets="platformServer"
/>

<JMSConnectionFactory Name="WLI_B2B_TopicFactory"
JNDIName="com.bea.wli.b2b.server.TopicConnectionFactory"
AllowCloseInOnMessage="true"
UserTransactionsEnabled="true"
Targets="platformServer"
/>
<JMSConnectionFactory
AllowCloseInOnMessage="true"
JNDIName="com.bea.wli.b2b.rosettanet.QueueConnectionFactory"
Name="RNQueueFactory"
Targets="platformServer"
UserTransactionsEnabled="true"
/>
<JMSConnectionFactory
AllowCloseInOnMessage="false"
DefaultDeliveryMode="Persistent"
DefaultPriority="4"
DefaultTimeToLive="0"
JNDIName="com.bea.wlai.JMSConnectionFactory"
MessagesMaximum="10"
Name="WLAI_JMSConnectionFactory"
OverrunPolicy="KeepOld"
UserTransactionsEnabled="true"
Targets="platformServer"/>
/>
<JMSConnectionFactory
AllowCloseInOnMessage="true"
JNDIName="com.bea.wlpi.TopicConnectionFactory"
Name="wlpiFactory"
Targets="platformServer"
UserTransactionsEnabled="true"
/>
<JMSConnectionFactory
AllowCloseInOnMessage="true"
JNDIName="com.bea.wlpi.QueueConnectionFactory"
Name="wlpiQueueFactory"
Targets="platformServer"
UserTransactionsEnabled="true"
/>
<JMSJDBCStore
ConnectionPool="wliPool"
Name="JMSWLIStore"
PrefixName="PBPUBLIC"
/>
<JMSServer Name="WLIJMSServer"
Targets="platformServer"
TemporaryTemplate="TemporaryTemplate"
Store="JMSWLIStore">
<JMSTemplate Name="TemporaryTemplate"/>

<JMSQueue Name="WLI_B2B_RNEncoderQueue"
JNDIName="com.bea.wli.b2b.rosettanet.EncoderQueue"/>
<JMSTopic Name="WLI_B2B_Topic"
JNDIName="com.bea.wli.b2b.server.B2BTopic"/>
<JMSQueue Name="WLI_B2B_OutboundQueue"
JNDIName="com.bea.b2b.OutboundQueue"/>

<JMSTopic Name="wlpiEvent"
JNDIName="com.bea.wlpi.EventTopic"/>
<JMSQueue Name="WLI_BPM_Timer"
JNDIName="com.bea.wli.bpm.TimerQueue"
StoreEnabled="true"
Template="WLI_JMSTemplate"/>
<JMSQueue Name="WLI_BPM_Event"
JNDIName="com.bea.wli.bpm.EventQueue"
StoreEnabled="true"
Template="WLI_JMSTemplate"/>
<JMSQueue Name="WLI_BPM_ValidatingEvent"
JNDIName="com.bea.wli.bpm.ValidatingEventQueue"
StoreEnabled="true"
Template="WLI_JMSTemplate"/>
<JMSTopic Name="WLI_BPM_Error"
JNDIName="com.bea.wli.bpm.ErrorTopic"/>
<JMSTopic Name="WLI_BPM_Audit"
JNDIName="com.bea.wli.bpm.AuditTopic"/>
<JMSTopic Name="WLI_BPM_Notify"
JNDIName="com.bea.wli.bpm.NotifyTopic"/>

<JMSQueue Name="WLAI_ASYNC_REQUEST_QUEUE"
JNDIName="com.bea.wlai.ASYNC_REQUEST_QUEUE"/>
<JMSQueue Name="WLAI_ASYNC_RESPONSE_QUEUE"
JNDIName="com.bea.wlai.ASYNC_RESPONSE_QUEUE"/>
<JMSQueue Name="WLAI_EVENT_QUEUE"
JNDIName="com.bea.wlai.EVENT_QUEUE"/>
<JMSTopic Name="WLAI_EVENT_TOPIC"
JNDIName="com.bea.wlai.EVENT_TOPIC"/>
     
     <JMSQueue JNDIName="com.bea.wlai.WORKSHOP_ASYNC_RESPONSE_QUEUE" Name="WLAI_WORKSHOP_ASYNC_RESPONSE_QUEUE"/>
     <JMSQueue JNDIName="com.bea.wlai.WORKSHOP_EVENT_QUEUE" Name="WLAI_WORKSHOP_EVENT_QUEUE"/>

<JMSQueue Name="WLI_FailedEvent"
JNDIName="com.bea.wli.FailedEventQueue"
StoreEnabled="true"/>
<JMSTemplate Name="WLI_JMSTemplate"
ErrorDestination="WLI_FailedEvent"
RedeliveryDelayOverride="60000"
RedeliveryLimit="10"/>
</JMSServer>
<JMSJDBCStore Name="JMSWLIStore"
ConnectionPool="wliPool"
PrefixName="platformServer"/>






<Application
Deployed="true"
Name="taxWSApp"
Path="C:/bea/user_projects/epmsDomain/beaApps/taxWSApp"
TwoPhase="true"
>
<EJBComponent
Name="tax"
URI="tax.jar"
Targets="platformServer"
/>
<WebAppComponent
Name="tax-webservice"
URI="tax-ws"
Targets="platformServer"
/>
</Application>
<Application
Deployed="true"
Name="paymentWSApp"
Path="C:/bea/user_projects/epmsDomain/beaApps/paymentWSApp"
TwoPhase="true"
>
<EJBComponent
Name="payment"
URI="payment.jar"
Targets="platformServer"
/>
<WebAppComponent
Name="payment-edit webservice"
URI="pay-ws"
Targets="platformServer"
/>
</Application>

<Application
Deployed="true"
Name="wlpDocsApp"
Notes=""
Path="C:/bea/weblogic700/portal/lib"
TwoPhase="true"
>
<WebAppComponent
IndexDirectoryEnabled="false"
Name="wlpDocs"
Targets="platformServer"
URI="wlpDocs.war"
ServletReloadCheckSecs="300"
/>
</Application>

<Application
Deployed="true"
Name="portalApp"
Notes=""
Path="C:/bea/user_projects/epmsDomain/beaApps/portalApp"
TwoPhase="true"
>
<ApplicationConfiguration
Name="portalApp"
Targets="platformServer"
URI="META-INF/application-config.xml"
/>
<EJBComponent
Name="events"
Targets="platformServer"
URI="events.jar"
/>
<EJBComponent
Name="pipeline"
Targets="platformServer"
URI="pipeline.jar"
/>
<EJBComponent
Name="property"
Targets="platformServer"
URI="property.jar"
/>
<EJBComponent
Name="rules"
Targets="platformServer"
URI="rules.jar"
/>
<EJBComponent
Name="usermgmt"
Targets="platformServer"
URI="usermgmt.jar"
/>
<EJBComponent
Name="customer"
Targets="platformServer"
URI="customer.jar"
/>
<EJBComponent
Name="ebusiness"
Targets="platformServer"
URI="ebusiness.jar"
/>
<EJBComponent
Name="portal"
Targets="platformServer"
URI="portal.jar"
/>
<EJBComponent
Name="campaign"
Targets="platformServer"
URI="campaign.jar"
/>
<EJBComponent
Name="catalogws"
Targets="platformServer"
URI="catalogws.jar"
/>
<EJBComponent
Name="document"
Targets="platformServer"
URI="document.jar"
/>
<EJBComponent
Name="ejbadvisor"
Targets="platformServer"
URI="ejbadvisor.jar"
/>
<EJBComponent
Name="mail"
Targets="platformServer"
URI="mail.jar"
/>
<EJBComponent
Name="placeholder"
Targets="platformServer"
URI="placeholder.jar"
/>
<WebAppComponent
Name="toolSupport"
Targets="platformServer"
URI="toolSupport"
ServletReloadCheckSecs="300"
/>
<WebAppComponent
Name="tools"
Targets="platformServer"
URI="tools"
ServletReloadCheckSecs="300"
/>
<WebAppComponent
Name="datasync"
Targets="platformServer"
URI="datasync"
ServletReloadCheckSecs="300"
/>
<WebAppComponent
Name="splashPage"
Targets="platformServer"
URI="splashPage"
ServletReloadCheckSecs="300"
/>

</Application>
<Application
Deployed="true"
TwoPhase="true"
StagedTargets="platformServer"
Name="p13nConsoleApp"
Path="C:/bea/weblogic700/portal/lib"
>
<WebAppComponent
Name="p13nConsole"
ServletReloadCheckSecs="300"
Targets="platformServer"
URI="p13nConsole.war"
/>
</Application>

<Application Deployed="true" LoadOrder="900" Name="EAI" Path="C:/bea/weblogic700/samples/workshop/wlai/ear/" TwoPhase="true">
<EJBComponent
DeploymentOrder="100"
Name="repository-ejb.jar"
     Targets="platformServer"
URI="repository-ejb.jar"/>
<EJBComponent Name="WLI-B2B Startup"
DeploymentOrder="200"
Targets="platformServer"
URI="b2b-startup.jar"/>
<EJBComponent DeploymentOrder="300" Name="b2b-rosettanet.jar" Targets="platformServer" URI="b2b-rosettanet.jar"/>
<WebAppComponent DeploymentOrder="400" Name="b2b.war" Targets="platformServer" URI="b2b.war"/>
<WebAppComponent DeploymentOrder="500" Name="b2bconsole.war" Targets="platformServer" URI="b2bconsole.war"/>
<EJBComponent DeploymentOrder="600" Name="WLI-AI Server" Targets="platformServer" URI="wlai-server-ejb.jar"/>
<WebAppComponent DeploymentOrder="700" Name="wlai" Targets="platformServer" URI="wlai.war"/>
<EJBComponent DeploymentOrder="800" Name="WLI-AI Async Processor" Targets="platformServer" URI="wlai-asyncprocessor-ejb.jar"/>
<EJBComponent DeploymentOrder="900" Name="WLI-AI Event Processor" Targets="platformServer" URI="wlai-eventprocessor-ejb.jar"/>
<EJBComponent DeploymentOrder="1000" Name="wlpi-ejb.jar" Targets="platformServer" URI="wlpi-ejb.jar"/>
<EJBComponent DeploymentOrder="1100" Name="wlpi-master-ejb.jar" Targets="platformServer" URI="wlpi-master-ejb.jar"/>
<EJBComponent DeploymentOrder="1200" Name="wlpi-mdb-ejb.jar" Targets="platformServer" URI="wlpi-mdb-ejb.jar"/>
<EJBComponent DeploymentOrder="1300" Name="WLXTEJB.jar" Targets="platformServer" URI="WLXTEJB.jar"/>

How to get JDev 10.1.2/ADF working with MS SQL Server Identity Column

Hello JDevTeam & JDevelopers,
I want to use JDev/ADF with a MS SQL Server 2005 database that contains tables employing IDENTITY Columns.
Using JDev/ADF and DBSequence with an Oracle database employing before triggers/sequences accomplishes what I am trying to do except I want to accomplish the same thing using a MSSQL Server 2005 database. Unfortunately I cannot change the database.
I have been able to select records but I am unable to insert records (due to my lack of knowledge) when using MS/SQL Server Identity Columns with JDev/ADF.
The following are the steps taken thus far.
Step1: Create table named test in the 2005 MSSQL Server (see script below).
Step2: Register 3rd Party JDBC Driver with JDeveloper; Using use Tools/Manage Libraries. Create a new entry in User Libraries with the following;
     Library Name     = Ms2005Jdbc
     Class Path     = C:\dev\Ms2005Jdbc\sqljdbc_1.0\enu\sqljdbc.jar
     (note: Latest TYPE 4 JDBC driver for Microsoft SQL Server 2005 - free at http://msdn.microsoft.com/data/ref/jdbc/)
Step3:Create New Database Connection;
     Connection Name = testconn1
     Type = Third Party JDBC Driver
     Authentication Username = sa, Password = password, Check Deploy Password
     Connection
          Driver Class = com.microsoft.sqlserver.jdbc.SQLServerDriver
          Library = Ms2005Jdbc
          Classpath = C:\dev\Ms2005Jdbc\sqljdbc_1.0\enu
          URL = jdbc:sqlserver://192.168.1.151:1433;instanceName=sqlexpress;databaseName=test
     Test Connection = Success!
Step5: Create a new application workspace using Web Application default template
Step6: In Model project, Create new Business Components Diagram.
Step7: Create new Entity Object. Goto to connections/testconn1, open tables and drag table test onto the diagram.
Step8: Generate Default Data Model Components by right-clicking on Entity Object. Except all the defaults.
When I test the Appmodule I select the view object and can scroll through all the records without error. If I try to insert a record, I get JBO-27014: Attribute testid in test is required.
Going back to the EntityObject I deselect the Mandatory attribute and re-run the test. Now when I try to insert it accepts the value for testname but it does not update the PK testid like it would using an "JDev/ADF/DBSequence/Oracle database/before trigger/sequence" solution.
Going back to the EntityObject and selecting refresh on insert does not solve this problem either. Changing the URL connection string and adding "SelectMethod=cursor" did not help and changing the SQl Flavor to SQLServer produced errors in the Business Components Browser. I've tried overriding isAttributeChanged() and other things as well.
I am totally stuck! Can anyone provide a solution?
Thanks for you help,
BG...
Create table named test
use [testdb]
go
set ansi_nulls on
go
set quoted_identifier on
go
create table [test](
     [testid] [int] identity(0,1) not null,
     [testname] [nvarchar](50) collate sql_latin1_general_cp1_ci_as not null,
constraint [pk_test] primary key nonclustered
     [testid] asc
)with (pad_index = off, ignore_dup_key = off) on [primary]
) on [primary]

Figured it out!
When using the MS SQL Server 2000 Database with the MS JDBC 2000 Driver you specify the SQL Flavor to SQLServer. However setting the SQL Flavor to SQLServer with MS SQL Server 2005 Database and the MS JDBC 2005 Driver will *** fail ***.
When working with the MS SQL Server 2005 Database and the MS JDBC 2005 Driver you set the SQL Flavor to SQL92 and the Type Map to Java.
If using a named instance like I am you would specify the URL = jdbc:sqlserver://<db host ip address>:<listening port>;instanceName=<your instance name>;selectMethod=cursor;databaseName=<your database name> (note: leave out the < >)
The 2005 Driver Class is different then the 2000 and is specified as com.microsoft.sqlserver.jdbc.SQLServerDriver
Note: In a default MS SQL Server 2005 installation the listening port will change *** everytime *** the host is restarted! You can override this though.
For the primary key you need to deselect the Mandatory attribute in the EntityObject editor.
Set Refresh on insert/update = no.
Set Updateable = never.
Now my Primary Keys which get their values from the Identity Column are working with ADF in a predictable way.
Simple enough but I have been away from this stuff for awhile.
BG...

Is it possible to Deploy a SSIS package to catalog with a Sql Server Identity in SQL Server 2012 programmly ?

Hi,
how can I deploy a SSIS package with a SQL SERVER identity to the catalog in SQL Server 2012 programmly?
I tried to use the [SSISDB].[catalog].[deploy_project], but the error said that it could only be used with a WINDOWS identity.
This question has worried me for days.
Is there any way to make the catalog.deploy_project available for a SQL SERVER identity ?
Or just an new solution instead of using the catalog.deploy_project?
best wishes from Qingyuan Lee.

Sorry, my description may be confusable.
I use EXECUTE AS , not EXECUTE WITH, to solve the problem.
In fact, I don't care about the authority.
I want to execute the stored procedure using a SQL SERVER Authentication Account , since my codes run on a linux OS and it is hard to connect to SSIS using a Windows Authentication Account.
so, using EXECUTE AS to change the execution context is accaptable.
The requirement for a Windows Authentication Account makes sense.
I consider that the SSIS executes outside the context of SQL Server and as part of an OS process, which means that a Windows account is necessary in order to deploy a package.
Thanks very much for your help.

Replacing a windows server with a Mac server

Hi all,
So this is a big company with about 150 employees using PC's (win xp and 7), considering replacing the current Windows server with a Mac server.
Is it possible to give users profiles once they log in like Windows server does? So when the user logs in they get to their own personal stuff? Can Mac server do that?
Can the user also get to the default printer and send prints to it regardless where they log in from inside the company?
And can the home directory to each user NOT be copied anywhere on the local machine where they log in? Meaning that after they log out there will be no traces to their files on that local PC..
Thanks a lot in advance!!

By some standards, 150 is not "big" but a large small business :-)
Regardless, please plan and test and plan some more, very carefully !
The picture for what you want to do once looked far better with 10.6 server but that had its limitations as well.
With 10.6 server, Apple was using Samba - they are no longer doing so,
but/and the version of Samba they were using only provided NT-Domain level support.
So that would not work with your Win 7 stations either. But could be made to work relatively well with XP workstations. You can no longer buy any new Mac that runs 10.6 server and 10.6 server would be hard to obtain.
Not a great route to go.
Bear in mind that the key problem with Apple's Samba was that Samba changed their licensing,
and there's not a thing in the world Apple could do to implement a current version of Samba without violating their own operating principles and the licensing requirements.
You'll be heading into heavily uncharted territory here. Odds are good that any desired domain-functionality is not going to work for you.
Honestly, Apple appears to have thrown in the towel on directory-level support for Windows,
and the best way to support Windows workstations in that regard is with Windows server and AD.
Basic filesharing works, with some caveats.
If there's no AD involved at all, then have a look at my earlier post,
https://discussions.apple.com/thread/3206725?start=47
Which worked a-ok for me but your mileage may vary.
Samba new current versions and GPL3 licensing issue:
https://discussions.apple.com/thread/3206725?start=75&tstart=0
"GPLv3 makes it impossible to provide signed binaries without also providing the signing keys. A few seconds of thought will reveal why Apple is unwilling to provide copies of the keys they use to sign system software. Part of locking down OS X security profile required removing anythign that used GPLv3.
Short version: GPLv3 is specifially desinged to be anti-company, and you are going to see a ever widening schism in the FSS/OSS community between GPL and all the other licenses, and you will be seeing less and less GPL code in commercial OSes and more BSD/Apache/&c code."
http://discussions.apple.com/thread.jspa?messageID=12494378

Problem with NW04s SR2 installation with MS SQL Server 2000 SP4

Im struggling with the NW04s installation with MS SQL Server 2000.
The installation stops at the step Create/modify database schema SAPJ2EDB.
The following error/info from log file,
INFO       2007-06-06 12:02:33 [iaxxgenimp.cpp:632]
           showDialog()
Execute step doConfiguration of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|NW_MSS_SRVCFG|ind|ind|ind|ind|6|0.
INFO       2007-06-06 12:02:35 [iaxxgenimp.cpp:632]
           showDialog()
Execute step doTempdb of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
INFO       2007-06-06 12:02:36 [iaxxgenimp.cpp:632]
           showDialog()
Execute step doSwitch of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
INFO       2007-06-06 12:02:36 [iaxxgenimp.cpp:632]
           showDialog()
Execute step doTempDBAnalyze of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
INFO       2007-06-06 12:02:37 [iaxxgenimp.cpp:632]
           showDialog()
Execute step doTempDBBeforeRestart of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
INFO       2007-06-06 12:02:38 [iaxxgenimp.cpp:632]
           showDialog()
Execute step doRestartServer of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
INFO       2007-06-06 12:02:58 [ianxbservi.cpp:697]
           CIaNtServices::stop(const map<iastring,iastring>&)
The service 'MSSQLSERVER' stopped successfully on host 'GBCZ672C'.
INFO       2007-06-06 12:03:10 [ianxbservi.cpp:632]
           CIaNtServices::start(const map<iastring,iastring>&)
The service 'MSSQLSERVER' started successfully on host 'GBCZ672C'.
INFO       2007-06-06 12:03:21 [ianxbservi.cpp:632]
           CIaNtServices::start(const map<iastring,iastring>&)
The service 'SQLSERVERAGENT' started successfully on host 'GBCZ672C'.
INFO       2007-06-06 12:03:21 [iaxxgenimp.cpp:632]
           showDialog()
Execute step doTempDBAfterRestart of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
INFO       2007-06-06 12:03:22 [iaxxgenimp.cpp:632]
           showDialog()
Execute step doChangeTempSetNewSize of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssDowntimeConfig|ind|ind|ind|ind|7|0.
INFO       2007-06-06 12:03:39 [iaxxgenimp.cpp:632]
           showDialog()
Execute step CheckParameters of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0.
INFO       2007-06-06 12:03:39 [iaxxgenimp.cpp:632]
           showDialog()
Execute step CreateDirectories of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0.
INFO       2007-06-06 12:03:40 [iaxxgenimp.cpp:632]
           showDialog()
Execute step CreateDatabase of component |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0.
ERROR      2007-06-06 12:03:40 [iaxxgenimp.cpp:731]
           showDialog()
FCO-00011 The step CreateDatabase with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0|CreateDatabase was executed with status ERROR .
ERROR      2007-06-06 12:03:40
           lib=iamodmssql module=CIaNtMssDmo
MDB-05053 Errors when executing sql command: <p nr="0"/> If this message is displayed as a warning - it can be ignored. If this is an error - call your SAP support.
INFO       2007-06-06 12:04:04 [iaxxgenimp.cpp:774]
           showDialog()
An error occured and the user decided to retry the current step: "|NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0|CreateDatabase".
ERROR      2007-06-06 12:04:05 [iaxxgenimp.cpp:731]
           showDialog()
FCO-00011 The step CreateDatabase with step key |NW_Onehost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_CreateDB|ind|ind|ind|ind|0|0|NW_MSS_DB|ind|ind|ind|ind|2|0|MssSchemaCreate|ind|ind|ind|ind|9|0|CreateDatabase was executed with status ERROR .
Please let me know if you can help or if there is any other way around.
Many Thanks in advance.
Ritin Jain

Hi All,
I was not able to solve the problem with MS SQL 2000, but I was able to resolve the issue with MS SQL 2005.
You have to chhose the following settings while instalation,
Service Account - Select one of the following options:
1) Use the built-in System account for each service and choose Local system or Network Service.
2) Use a domain user account, and enter the user name and password.
Under Start services at the end of setup make sure that SQL Server and SQL Server Agent are selected.
Authentication Mode
1) Select Mixed Mode (Windows Authentication and SQL Server Authentication).
This mode is required for a Java or ABAP+Java system.
If you choose this mode, you have to set the password for the sa login.
Note: The password for the sa login must comply with the Windows password policy.
Collation Settings
1) Select SQL collations (used for compatibility with previous versions of SQL Server).
2) From the drop-down list select Binary order based on code point comparison, for use with the 850 (Multilingual) Character Set.
I hope this helps!

Oracle Connectivity with MS SQL Server. ORA-00972: identifier is too long

I have linked Oracle Database with MS SQL Server using HS and DB Link.
DB Link Script:
CREATE DATABASE LINK "FCHH"
CONNECT TO SA
IDENTIFIED BY <PWD>
USING 'LISTENER_FCHH';
Links tested successfully.
Now "SA" user in Microsoft SQL Server has multiple databases i.e. Master,SecurePerfect,SecurePerfectHistory. when I try following command
select * from "SecurePerfectHistory.DBO.BadgeHistoryTable"@FCHH
ORA-00972: identifier is too long

ORA-00972: identifier is too long
Cause: An identifier with more than 30 characters was specified.
Action: Specify at most 30 charactersAman....

Installing BAM with Biztalk Server 2013 and SQL server 2012

Hello All,
I have to work on BAM with BizTalk Server 2013 and SQL server 2012 , is BAM already comes with BizTalk server installation ?
Will I needs to explicitly install that ? from where I can get the installer for BAM ?
What else I will needs to work on BAM ?
Note : I want to handle Exceptions in BAM ....how to do that ?
Thanks,
Nitin.
Thanks and Regards, Nilesh Thakur.

Hi,
BAM is available with BizTalk, all you need is to select it and install .
Refer the
Installation Guide available on MSDN or follow the blog: http://sandroaspbiztalkblog.wordpress.com/2013/05/05/biztalk-2013-installation-and-configuration-important-considerations-before-set-up-the-server-part-1/
Maheshkumar S Tiwari|User
Page|Blog|BizTalk
Server : Scheduling Orchestration using Trigger Message

How to create CATALOG with MS SQL Server?

Connection class has getCatalog(strCatalog) method. In order to use it, we must create CATALOG in Database?
How to create CATALOG with MS SQL Server?
Help me, please!!!

You do not create these for any database, this is part of the Connection metadata.
The Catalog is the third level of table-like database object qualification as in "Catalog.Schema.Table". For SQLServer the qualification scheme is "Database.Owner.Table" and I would be surprised if they reported anything for the current connections getCatalog() method call.
What many people do is avoid table qualification altogether by setting the connection's context in a database proprietary manner and then keeping the SQL as clean as possible. For many ODBC and JDBC drivers this can be set in the configuration. For MS SQLServer you can also execute a "USE dbname" statement on the connection to avoid table qualification.

URGENT ! Using Sun's J2EE RI Server with MS SQL Server 2000

Similar Messages

Maybe you are looking for