Error configuring the RAD WAS Portal runtime for a new server instance - websphere-portal

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

Related

Unable to uninstall SQL Server 2017 from an inherited work PC

I've got an inherited work PC that has SQL Server 2017 installed locally. The company is no longer on that version so I want to remove it, however, when I go to add/remove programs and try to uninstall it I get a popup that says:
This file does not have an app associated with it for performing this action. Please install an app or, if one is already installed, create an association in the default app settings page.
Anyone have any thoughts as to what the default app for uninstalling SQL Server should be? Or what file type it's referring to? I've never seen add/remove programs pop this message up before. The machine is Windows 10.
EDIT: I should note I am the admin of this machine.

Missing: Outlook 16.0 Object library (msoutl.olb)

I'm running an MS Access database with VBA code that has libraries for Microsoft Office 2010. Currently, there are users that are upgrading their machine to Windows 10 running Access 2016.
When the database is opened on a new machine running Access 2016 the libraries for the Outlook changes to 16.0.
When I try to open the file in the old Access 2010 environment, I run into this error:
Missing msoutl.olb.
Is there a way to make the database backwards compatible?
It sounds like the users share the same frontend hosted in a network folder.
If not done already, split the database to have a single shared backend database file. Then, to avoid your issue, distribute a separate copy of the frontend to each user's workstation.
On the workstation, let the user launch the frontend using a shortcut that runs a script to always keep the frontend current. This method is described in detail in my article:
Deploy and update a Microsoft Access application with one click

Rational Application Developer 9.1.1, unable to add runtime Websphere Portal runtime

I am unable to add Websphere Portal 8.5 CF07 installation as a runtime in Rational Application developer 9.1.1 client.
Selecting my 8.5 installation without any fixpacks works as expected.
For 8.5CF07 the runtime dialog gives no errors, but the finish button stays grayed out.
Both installations 8.5 and 8.5CF07 are installed on my local machine on the same drive.
Any idea how to solve or debug this issue? Do I need another server adapter? If so, where can I download newer adapters? I have checked the Eclipse Market place and several IBM Repositories.
I am using Windows 10 as OS.
Did you installed the Portal server adapters when installing RAD? did you installed RAD via Installation Manager? if so, launch IM and modify your installation to include the Portal adapters.
Can you please share the location of your Portal 8.5 CF07 directories (PortalServer and AppServer)?
Typically (you probably already know this) CF is installed on top of an existing Portal installation. Make sure that while defining a new server, you provide the correct path to the PortalServer directory in the WebSphere Portal location field and also the correct path to the underlying WAS server in the WebSphere Application Server location field.
See the image here http://i.stack.imgur.com/hoOHC.png
Also, you can try to restart RAD with a new workspace. RAD should automatically detect the Portal Servers.
Thanks,
Gaurav
A reinstall of the portal server, with the default was profile folder name: "wp_profile", solved the issue. In previous installs we used "WPProfile" as folder name.

Migrating dotnetnuke from development to test server

I am a newbie with DotNetNuke and have been stumbling on how to deploy from the development server to the deployment server. For starters my development and deployment servers are one and the same machine. Here are the steps that I did:
DNN Setup
Downloaded DNN using WebMatrix.
Launched DNN and proceeded with the installation wizard, which is basically just testing the environment and then creating the DNN database.
After the wizard's installation launching DNN will now proceed to the Getting Started page
Added "localhost/dnn" in the site alias list
Moving to ISS
In IIS I added application (folder) DNN in the web root
I copied all the files from the original webmatrix path to the dnn folder in c:\inetpub\webroot making sure that the file/folder hierarchies are the same
Result:
When launching DNN using my browser I am directed to the installation wizard page instead of the Getting Started page. What am I missing?
Thanks!
Confirm that the permissions on the folder containing DNN are the same on your test server as they are on your development server. (I give Network Service read/write and IUsr Read/Execute)
Confirm that the application pool running your application has the proper identity (Network Service is suggested) and is running the proper .NET Framework version; based upon your question, I think you are set on this.
Gain access to your web.config file. You will see a ConnectionStrings section. You probably need to update the connection strings.
If your test server runs off of a different database than your dev server, figure out the connection string of your test server and update your connection string accordingly
You may be able to restore a .BAK file of your DB to your test server
If you do this, you will probably need to (in SSMS) edit your Portal Alias table to include the host name that you are using in your test server environment. Examples: Maybe you access the site via localhost/ on your dev environment, but you access to test site via test.Ronald.com? test.Ronald.com would be your PortalAlias
If your test server runs off the same database server as your dev server, it sounds like you need to open up access in firewalls so that your test server has connectivity to your dev database
A word of advice
Once you get it running, you will be making changes to each database separately (assuming your test site and dev site use different DB Servers). This sync issue can be a royal pain with DNN, as your page structures, module assignments, html module contents, installed modules/extensions will get out of sync. While restoring backups is nice, it is not a very good long-term solution. I recommend database-syncing tools
The problem is most likely a problem with DNN not being able to find the Database. If it can't find the database, it will run the wizard in order to create one.

New to SSRS Configuration

I am trying to install and configure SSRS on SQL 2005.
When I click Reporting Services Configuration, I get a message saying
No report servers were found on the specified machine - Details
Invalid namespace.
How can I resolve this?
You don't "configure SSRS on SQL Server 2005", as such.
It's a component that you choose at install time (like Analysis Services, Integration Services etc). For SSRS, then you require IIS as a prerequsite and it won't be installed if IIS is not present.
The error itself is 100% correct if SSRS is not installed...
Is it actually installed?
Edit:
Just got this on one of my feeds: KB 960374 that describes the exact error above
Quite simple. Place your disc with SQL in and run setup. Add features to your existing instance and select Reporting Services. Once installed it would have created 2 databases on your SQL Server named ReportServer and ReportServerTempDB
Open the services configuration and you should be prompted to connect to an instance of Reporting Services.
If you see this screen then you are ready to go.
--Read this only if you might have questions to ask
Setup a service account for Network Service (save the .snk key and it will create your IIS entries etc. If you don't have IIS then upgrade your OS to a compatible version. It can be installed via Add or Remove Windows Features)
Make sure your new database is selected in the Database section. If not, then follow the screen to add it
Open the Report Manager URL and click on the link. (You may need to be in as an administrator)
When you want to deploy reports, simply update your solution properties with the TargetURL pointing to the Web Service URL that is available after setting up the Service Account)
Ask anything further if you need the guidance. I've done this to about 5 servers in the past month already, so I know what can go wrong.
Cheers,

Resources