I recently installed Rational Software Architect Designer for WebSphere Software (RSA4WS) 9.5. I am trying to create a WAS 8.5 server within RSA, but...
The version of Profile Management Tool that RSA launches is 7.0
The only WAS installed runtime that RSA recognizes is WAS 7.0
Although the New Server dialog lists WAS 7.0, 8.0 and 8.5...
When I select WAS 7.0, the Server Runtime Environment dropdown list is set to WAS v7.0
When I select either WAS 8.0 or WAS 8.5, the Server Runtime Environment dropdown list is set to "Create a new runtime environment"
Under Window | Preferences, Server | Runtime Environments, RSA lists:
Web Preview Server Runtime
WebSphere Application Server v7.0
WebSphere Application Server v8.0 stub
WebSphere Application Server v8.5 stub
The subdirectories of C:\Program Files\IBM\SDP\runtimes are:
base_stub
base_v7
base_v7_stub
base_v8_stub
base_v85_stub
nodejs
updi_v7X_64
wsdk
I suspect that I haven't installed some feature set for RSA, but I've not found any downloads on IBM's Passport Advantage site that seem like they'd be what I would need. Since RSA4WS is basically Rational Application Developer (RAD) plus extra stuff, maybe downloading a package for RAD would do the trick -- but I don't know whether that's the case.
To complicate matters, for security reasons, my development PC is not Internet-connected, so I have to guess which downloads I need, download them, transfer the files to the development PC, and point Installation Manager to the (local) repository.
Does anyone have any advice? Thanks in advance!
You need to install WAS 8.5.5.x runtime separately. WAS 8.x testing environment is no longer included in the RAD/RSA installation itself.
You can either:
download additional files with 8.5.5.x runtime from Passport Advantage labeled IBM WebSphere Application Server V8.5.5 (x of 3) for Multiplatform Multilingual
or just download WAS 8.5.5.x for developers from here
Related
For web application package vendors providing installer for some reason:
Would you share the "standard" approach to prepare fixed server environment for an asp.net application package? But some conditions I have:
1)My application requires iis, .net framework and sql server.
2)Windows Server itself, Sql Server licence and media is not provided by my company, end users provide them.(Usually standard edition.) When visiting end user site, Windows Os is already installed, but SQLserver media is not.
3)Install paths of sqlserver program, datas(mdf, ldf) can be changed by users according to server condition.
4)Users and my company officers don't want to change operational circumstances of endusers. Just want to change install procedure currently by manual manpower visiting physical sites of users.
5)Developper Environment:Visual Studio 2010.
6)We don't afford to buy Install Shield, or other non-free software.
I assume a concept that can be fulfilled by custom actions of WiX. But if such server environment should not be contained to a distributable installer which faces against the hostile circumstances of user servers ( install might fail for unknown reasons), I don't need uninstall function to my installer. But if WiX designers don't expect such installer, I might be in wrong path...
Any ideas?
A little background (before I get downvoted to oblivion!)
I'm working on an intranet-hosted ASP.NET web application in a highly secure environment. At the moment it's deployed by building a package in Visual Studio, the zip file is copied onto the server and installed in IIS using WebDeploy (right-click -> Deploy -> Import Application).
What I'd like to do is deploy a sanitised version of this application to an Azure Web Site for demonstration purposes, however most of the standard Azure deployment methods do not apply to me because:
I work on a secure network so Visual Studio is blocked from connecting to Azure (rendering 95% of documentation irrelevant!)
installable software is strictly controlled on this network so I cannot install the Azure SDK needed to create Service Definitions, Configurations and Packages
The only machine I have access to which can connect to Azure is woefully underpowered and can only run puTTY, PowerShell and basic text editors.
At the moment, I have a Windows VM in Azure just running IIS and WebDeploy - this works but seems like overkill (and a good way to burn through my credit) when Web Apps in theory do everything I need.
What can I do?
Another option may be to checkin the WebDeploy package to a free subscription of Visual Studio Team Services (VSTS = TFS in the cloud) and then create a deployment pipeline in VSTS using the new Release Management features.
https://www.visualstudio.com/features/release-management-vs.aspx
in that case:
1) FTP from your machine using your own FTP client or i would recommend to use PSFTP from Putty package.
2) Still WebDeploy, but use that to generate the needed files, then you can use PowerShell like that.
You can also use https://www.microsoft.com/web/webmatrix/ to connect to azure websites. It works with HTTP, only problem could be a corporate proxy.
I want to make an installer for a client which installs
a web app on IIS
a mssql db
a window service
I am totally naive to thinking of the solution for this automated deployment through an installer (msi or exe). The installer may hint the user for prerequisites for example MSSQL server and upgrading/installing IIS before the web app installation can proceed. Is it possible?
Yes, it is possible. You need to first select in an authoring tool for Windows Installer. Some examples are Windows Installer XML (WiX) and InstallShield (various editions from free to pricey). You'll have some kind of EXE bootstarpper/chainer where you can handle prerequisite installation such as windows features and database engines. Or you can choose to simply ship an MSI that detects and blocks if these are missing and put the effort on the user to manage their baseline environment. The actual MSI will then likely have features for web, service and sql. The web feature will install a bunch of files and configure the IIS meta. The windows service will install some files and create a windows service. The SQL feature will ask for connection string information, execute some sql scripts and possibly configure the web and service layers' connection strings.
Some of this can be deferred until after the installation and placed into a custom configuration utility to simplify the installer work.
There are various design decisions that can be made so it can't be answered in more detail in a simple question format.
Howcome I deploy my intranet ASP.NET MVC project?
What I've got so far:
project itself;
several client machines connected in a workgroup and server;
IIS Express 7.5, SQL Server 2008 R2 Express installed on a server.
It should be mentioned that though it's odd and unusual but server is just a machine without (even) server OS installed. Please note that it's not mine idea and is the environment I've got at the moment
I've read the instruction http://msdn.microsoft.com/en-us/library/gg703322(VS.98).aspx but it describes situation when you have Web Developer installed on the same machine.
Please help!
And Thanks!
This is the 100% manual approach, you might be able to access the remote web server via VS if authorization/permissions is lined up properly (much simpler, basically you just hit deploy):
Install IIS
Install .NET Framework 4
Install MVC
Register ASP.NET with IIS (just to be safe run it again)
Create Website via IIS Management Console (use a new directory for the website)
Put your files inside the new directory
Make sure permissions are setup properly
That's it
I'm deploying an ASP.NET application to Windows Server 2003 under IIS
IIS is serving html pages fine but I get a page not found when I try and serve IIS pages
You may need to "register" IIS for ASP.NET applications. As an administrator, run the command "%systemroot%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -i". In addition, you may need to convert your web site to an application through the IIS management console.
By default, IIS has ASP support disabled in IIS6.
A server running a member of the Microsoft® Windows® Server 2003 family supports application server functionality, with Microsoft ASP.NET as an option that you can enable when configuring the application server role. To deploy ASP.NET Web applications to a production server, you must be sure to enable the ASP.NET and Internet Information Services (IIS) roles on the production server before you distribute the application.
See here for instructions to enable it:
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/9fc367dd-5830-4ba3-a3c9-f84aa08edffa.mspx?mfr=true
Other possible reason could be Web Service Extensions, where ASP.NET version could have been disabled. My other post here explains steps to solve this.
Make sure the right .NET framework is installed properly
Make sure the ASP.NET extension is enabled
Under website properties, ASP.NET tab, make sure the right version is set.
After having this same issue and trying all of the above without any luck. We reinstalled SP2 for Windows 2003 and this resolved our issue. I too have seen this problem resolved a few times with the other answers. Most of the time just reinstalling .Net 2.0 resolves the issue but not this time.
For future reference, this could also be the issue:
IIS on a Windows Server 64-bit can only to run in either 32 or 64 bit mode.
In short you need to:
1) run adsutil.vbs to enable 32 bit asp.net apps on win 64
2) re-register IIS calling aspnet_regiis.exe
3) re-open IIS Manager, go into Web service extension list and ensure ASP.Net version {2/4.xxx} (32-bit) is set to Allowed
(You might need to do Steps 2 and 3 for both Framework 2.0 and 4.0 if you want to run asp.net apps on both versions)
Full details are in the following link: http://support.microsoft.com/kb/894435
Another future reference in case this is helpful to anyone who used a similar path to mine.
My back end for the ASP.NET app was MySql not Sql Server, which for me meant having a mysql connector, the reason my IIS was not serving the .aspx file is because on my development environment I was using a different version of the MySql connector than the one installed on my production environment, I updated the MySql connector on the production server to match the version Im using on the development environment and it worked great.