Hi All and thanks in advance.
I have an application developed in WebDev 22, and I was able to successfully upload it to my own personal Home Web server, The Application works fine however it cannot read the data because it does not have the analysis.
This application Analysis uses an MSSQL Server Database via the Analysis utilizing MSQL Server Machine ODBC (Means that I am not using the PCSoft Native MS SQL Drivers).
How can place the analysis when creating the Deployment Setup Install File, and how to configure it so that when I am installing the Application in the Site it will talk to the same database I have installed on the Windows Web Server at Home?
Does anyone knows, can this be possible?
Thanks
Regards,
Carlos
I got my own situation resolved.
It turns out that when a Setup Disk is created in PC Soft WebDev, it will automatically include the Database analysis inside the package, in my case I used the option of creating a Media Setup disk to run it in the Web Server, and install the application there. I thought that a very special configuration was needed to be done to connect the Analysis to the MS SQL Data Server in the Web Server, and is none of that.
Let me explain how I got it solved and I would like to explain that everything
was done in the Analysis connection to make possible this connection.
Open the Analysis and Click Connections.
These are the Parameter:
Name: Your Connection Name.
Caption: Your Connection Name here if you want.
Connection By: SQL Server (Microsoft OLE DB Provider for SQL Server).
Data Source: Your MSSQL Database Server Name.
Database: Your Database Name.
User Name: User you created to connect to this database.
Password: The User Password for the User.
Click on Test, if the Connection is successful you are good to Go.
MAKE SURE YOU HAVE VISUAL ON THE SERVER YOU ARE TRYING TO CONNECT
Save the Analysis and Synchronize.
Create the Setup disk and install on the Web Server.
That is it.!!
Why?
Because of when the WebDev application starts, it will Automatically open the Analysis.
The Analysis will then automatically look at the settings you have provided in the Analysis Connection Settings, and it makes the connection.
That is it, I hope this has help.
Best regards,
Carlos
I have two solaris servers.
One server is for clearcase licenses and another is for source code repository.
Unfortunately, somehow licensing server is not working with telnet (its running in single user mode).
As a result, I cannot open ClearCase Explorer as the licensing server is not working.
Now, I wanted to get the sourcecode from the repository server to my local (windows) system.
How can we get that?
I have installed IBM Rational Application Developer version 9.1 from the installation media. The media launches and installs the IBM Installation manager and I've selected the RAD 9.1 package for install. Among the options, I've requested that the "WebSphere Application Server v8.5" be installed, as well as the "WebSphere Portal Server v8.5" and all the options underneath.
Once I launch RAD, I go to the server tab (as instructed by the IBM Portal Developer course) and attempt to create a new WebSphere Portal server. The server wizard wants to know where the installation directory of the server runtimes are located for both WAS 8.5 and Portal 8.5.
For WAS this is simple, I point to the profile "AppSrv01" at the following location:
C:\Program Files\IBM\SDP\runtimes\base_v85_stub\profiles\AppSrv01
For the Portal Server, I assume there would be a default profile created, but there is not. There are several directories inside the stub directory, but no profiles. The best I can do is provide the following location:
C:\Program Files\IBM\SDP\runtimes\portal_v85_stub
Seems straightforward right? It complains of the following problem:
The Portal Server installation directory is not correct
Am I missing something here? Are there fix packs I need? Is the portal server runtime included with RAD 9.1 not enough to create and use a local portal server? DO I need to simply create a profile and if so where is the tool needed to do so? (I really really wish someone from IBM would explain this to me and how I am supposed to be indicated to the correct course of action)
IBM is, as usual, being very straightforward and easy to use/understand. Does anyone have any ideas about how I am supposed to proceed? The IBM Developer course that was bought and paid for assumes this step already and before you suggest it, yes I've already sent and am awaiting a response from the organization I am taking the course from.
Not sure I'm getting your description right. From what I can see, you installed RAD using IM from a media. Also, you selected WebSphere Application Server development tools and all underneath it as well as WebSphere Portal development tools.
These development tools options are stubs only, not the actual servers. With this I mean that they're useful for development and compiling purposes only, but not for deployment and testing because they are not the actual servers.
Here is the part that I don't understand. In the media that has IM and RAD, does it also have WebSphere Application Server and Portal Server available for installation? If not, then you need to get them and install them and then your can create the servers pointing to the install location of both servers in RAD. Once you do this, you can use RAD to create the profiles.
Hope this helps.
A few things, Install portal by itself and DO NOT install to a C:\Program Files make it something short like c:\IBM\WebSphere
it sounds like only portal stub got installed, did you have the portal media available as well.
If you install it using the same installation manager, RAD will be able to find it
i have been having this problem and wondering if u guys could steer me in the right direction. i have created a web app, and i have the .mdf files in the App_Data folder. i have create a web setup project for this. everything installs 100%. But because the server( or machine ) that i install the project on doesnt have user instances because this is disabled by default. how then can i deploy a Database with my installer? bare in mind that this must be a simple installation process, as the end users 9/10 times will not have a DBA, or even knowledge of what a Database is?
Any Ideas?
Thanks in advance...
EDIT: Appearantly user instances are on by default, but only available in SQL Server Express 2005 and earlier. For it to work, it depends on the connection string, which you control:
Data Source=.\SQLEXPRESS;
AttachDbFilename=|DataDirectory|\Database1.mdf;
Integrated Security=True;
User Instance=True
You still have to make sure the web server has SQL Server Express installed; if they have SQL Server, you're screwed.
The full details can be found in this MSDN Article.
By the way, you know that user instances is a feature that's being deprecated?
I'm not sure whether I'm asking the question correctly, but I've been told SQL Server cannot run on a Novell server. Is this true? If yes, why not?
Your problem is your directory service, whether it's Microsoft's Active Directory or Novell's Directory Services (I think it's called).
Sounds to me like your DNS is broken if your clients can't resolve names to IP address.
NOW I see your problem! Sorry dude!
Yes, VERY easy. Kinda.
SQL Server used to be able to talk IPX (the netware protocol) but I think Netware will now talk TCPIP, and you can run IPX and TCP/IP on the same network without an issue - windows clients can run both at the same time, 99% of routers handle all protocols etc.
Windows (XP/2003/etc) can run the netware client, so it can talk to shares etc.
Use the SQL Server logins (rather than windows integrated logins), and it'll work from anything - we have Java on Linux talking to SQL Server on windows just fine :) It's all in the connection string: userid=username;pwd=whatever;server=yourserverhere; etc. But you MUST use the SQL Server Configuration Manager to set these up - the default is shared memory, so you have to enable TCPIP etc.
You may have to be more specific about what a "novell server" is. From what I understand, Novell servers run some form of Suse linux. Sql Server is a windows only product.
My company, however, does have clients that run Novell networks, and we do run Sql Servers on their network. But they're hosted on a win box...
SQL Server is a Windows app. Novel is either one of:
Novell
or
Linux
Neither of these are windows :) It's like asking "why can't I run this Mac application on my windows box". Or "why will my petrol car not run on diesel?"
There are old version of Sybase, which SQL Server sprang from, which COULD run on Novell Netware, but you'd need to find a software museum to find one, I think!
If you need a SQL Server, I'd suggest you either get Small Business Server, which comes with MSSQL, or install one of the free editions of SQL Server on XP or windows 2003 server. Or use something like MySql, Postgress etc on Linux.
I'm not sure what you are asking. Are you looking for software to allow NetWare applications to talk to a SQL Server running on Windows? The wording of your original question implied that you want SQL Server to run on the NetWare machine.
The question of why SQL Server doesn't support NetWare is best asked of Microsoft, but AFAIK SQL Server doesn't support any non-Windows OS.
As someone else said, SQL Server originally came from Sybase's SQL Server (now called Adaptive Server Enterprise), which supported NetWare at one time but dropped it a long time ago. Sybase's other RDBMS, SQL Anywhere, dropped NetWare as of version 11, but versions 9 and 10 are still supported on NW.
OK, now I think I understand. I was thinking "client" as in database client application, not the Novell client.
I don't think you'll need the Novell client on the Windows machine, for a couple of reasons:
If the client is trying to connect over TCP/IP, it doesn't matter whether or not the Windows machine has the Novell client installed
Windows shares aren't affected by the Novell client, though you need some kind of Novell client for the Windows machine to map NetWare volumes
If the Windows machine does need to map NetWare volumes, I have found in the past that the Client Service for NetWare service (which ships with Windows but isn't installed by default) is sufficient, and doesn't have all the overhead of the Novell client.
It sounds like your Windows SQL Server is in fact a second class citizen on your networks. (I imagine you are using SQL Authentication instead of AD based.) If you have to connect via IP rather than name, then your Windows boxes aren't participating in an Active Directory authentication + DNS setup like is the case in most "windows" networks verus the "netware" network that you are running into. Netware has it's own form of directory services that is independant of Microsoft.
If you want your Microsoft SQL Server to be a integral part of your network, then you need Microsoft Active Directory installed with integrated windows authentication and DNS services running on a Domain Controller. But, this would conflict with your directory services (if used) on your netware server.
If your Netware network is running just fine, then I wouldn't change it. Simply add the microsoft sql server's network name to your local DNS services and it won't appear like it's a second class citizen. You could install the netware client on the SQL machine but that would make most DBA's cringe. But, it would register the machine in Netware's directory.
SQL Server, although rooted in a Sybase/Unix/VMS background, is a native windows application. Apart from the compact edition (which runs on some Windows mobile platforms), SQL Server runs on Windows desktop and server operating systems.
More informaiton can be found at wikipedia.
Sorry to be prickly, but I'm not a noob: I know you can't install SQL Server on Linux. Do you guys have customers running Netware trying to connect to a SQL Server? That is what I am dealing with.
We have customers, mostly school systems, that use Netware as the "network OS" with many Windows workstations running the Netware client. Our app uses SQL Server which is usually installed on a Windows 2003 server, but the server is always a second class citizen on the network. Users often must use the IP address rather than machine name to connect the SQL Server.
#Will: Do your Novell customers have trouble accessing SQL Server on the Windows server? Can you install the Netware client on the Windows server to enable file sharing?
#Graeme: Thanks for helping me refine my question. My employer somehow has the impression that a Windows server is a second-class citizen on a NetWare network. Would installing the NetWare client on the Windows server make it easier for NetWare clients (with some form of Windows OS) connect to the SQL Server? Would installing the NetWare client on the Windows server allow the server to share directories and files like a Novell server?
#geoffcc: The app uses SQL Authentication to connect to SQL Server.
The core issue is how are you authenticating to the SQL database. If you have an Active Directory tree, and an eDirectory you can easily link the two via Novell Identity Manager, which will synchronize users, groups, etc (any object you care to map between the two systems) as well as passwords.
Thus the same object exists in both locations so each system can use it as much it needs too. The license for Identity Manager is included with the Open Enterprise Server license (OES can run on Netware or on SUSE Linux Enterprise Server (SLES)).
Then you could use the Active Directory integrated authentication.
Beyond that, your Netware server likely does not need to connect to the database directly. If it does, you will be writing or using an application that includes the database connectivity. At which point it becomes a question of is there a client for this OS or not.
#flipdoubt Well if you are using SQL Authentication, then you are using a SQL Client of some kind to connect to it, and the fact you have Novell in the picture is as unrelated as if you had Banyan Vines. (There you go! Now a search will show at least ONE reference to Banyan Vines!! Every good technology site needs at least one, and probably not more than one!)
As others have noted, what are you trying to do?
If they need to use the IP address of the SQL server to connect to it via a SQL client, then you have a DNS problem.
If you want to connect to the MS SQL server box to put a file on it, then that is somewhat unrelated to the SQL aspect of the issue. There again, DNS can solve your woes, if you register the name of the server (Say it is SQLSERV1) with the default DNS name (say acme.com) tacked onto the end of it, so that the IP Name sqlserv1.acme.com resolves to the IP Number you want it to point at.
Next comes the question of where are the user identities stored? You are using SQL Authentication, so that means you are creating accounts in SQL for each user.
The basic alternatives are to use Active Directory and have MS SQL server use those identities. If you are in a non-AD shop, you can investigate Novell Identity Manager product which has a JDBC driver that can do a fair bit, One thing it can do is synchronize users from eDirectory to be SQL Server users. (Or to Active Directory, Lotus Notes, most LDAP directories, AS400's, mainframes, NIS/NIS+ and many more systems).