Hi we are trying to enable wmqJmsClient-1.1,wmqJmsClient-2.0 feature in Liberty profile . We performed feature Intsall using InstallationUtility and Feature Manager as well.
On Installation it shows:
Step 7 of 7: Installation completed
CWWKF1017I: One or more features installed successfully: [wmqJmsClient-2.0].
Start product validation...
Product validation completed successfully.
But when we try to access the feature using Rational Software Architect it shows up Warning: Feature is not available.
But while accessing the same via eclipse it seems to be working.
What needs to be performed in case you want to use Rational Software Architect to perform the same. RSA version being used : 8.5.
You can try to refresh the server in RSA. Go to Servers view, double click the server, click Runtime Environment link, then Advanced options.. link and finally Refresh.
If this wont help, you could try install WebSphere Developer Tools (I didn't try that), run update on RSA , or install newer version as 8.5 is pretty old now.
Related
Downloaded source package of DotnetNuke and I am new in dotnetNuke. Can anyone help me to clarify the process of installing DotnetNuke.
I am following this Install DNN
I've got a tutorial on installing DNN8 found here.
You can also follow this text tutorial
Setting up your development environment can vary based on what your
end goal is. If you are doing module development for your own use, and
within your own DNN environments, you can ignore a few of the settings
below. If you are doing module development with the idea that you
might turn around and give the modules away, or sell them, then you
will likely want to follow the guidelines set forth below to support
the widest array of DNN installation environments.
I recommend that each developer have their own local development
environment, with a local IIS website running DotNetNuke, and a SQL
Server 2008/2012 (not express, though you can use it) database for the
website. Having an individual development environment makes group
module development far easier than if you share
environments/databases.
Choosing a DotNetNuke Version Choosing a version of DotNetNuke is
important when you start your development for couple of reasons. For
modules that you are developing for yourself, you need to ask, what is
the minimum version of DotNetNuke that you have in production. Are you
running DNN 5.6.1? Are you running 6.2.6, 7.0.0, 7.0.6? Based on the
answer you can determine what version of DNN you should setup as your
development environment. You shouldn't be developing on a newer
version of DNN than what you have running in production. As with
everything there are ways around this, but I am not going to go into
the details on that in this tutorial.
As a developer working to create modules and release those, you might
have production sites that are running on the latest and greatest
version of DNN, but what about your customers? Or your potential
customers? You have to ask yourself, do you want to provide support
for really old versions of DotNetNuke? From a development perspective
you will probably say no, but from a business perspective, you might
say yes, and here’s why. Not everyone upgrades DotNetNuke websites as
they should, and often times you will find that some people never
upgrade. While I don’t advise taking that approach to managing a
DotNetNuke website, it is a fact of life that people don’t always
upgrade and there are thousands of people, if not tens of thousands,
that have sites that aren’t running on the latest version of DNN. You
should take that into account when you are doing your module
development, if you compile your module against an older version of
DNN then your module should run on newer versions of as well, for
example. If you compile your module against DotNetNuke 6.2.6 it will
likely run on every version of DNN released since then. Though there
are extended cases where this won’t always work, DNN strives to
maintain backwards compatibility, this isn't always possible.
You might also want to use features that are only available starting
with a specific version of DotNetNuke, such as the workflow
functionality found starting in DNN 5.1, in that case you may choose
not to support older versions of the platform out of necessity. This
will minimize the market in which you can sell your modules, but also
can make for less support and an easier development cycle due to the
features that DNN provides.
Choosing a Package Now here’s one that may baffle you a bit. I’m going
to recommend that you use the INSTALL package for whatever version of
DotNetNuke that you download. What? The INSTALL package? What about
the SOURCE package? Well you can use the source, but you don’t need
it. The module development that I’m setting you up for doesn't require
the DNN source, and using the INSTALL package makes your development
environment cleaner. We aren't going to be opening the DotNetNuke
project when we do our module development, so why have the files
sitting around for nothing? Also, if you've ever tried to use the
SOURCE package for anything, you'll know it isn't easy.
The steps for setting up your development environment will apply to
both the Community and Professional editions of DotNetNuke.
Installation Configuration Once you have the version selection out of
the way you can go through the installation process. While I’m not
going to walk you through the minutest of details of each step of
installing DotNetNuke in this post, I will at least try to point you
in the right direction for each step.
Download the INSTALL package of the version of DotNetNuke you want to
use in your development environment.
Extract the files in the INSTALL package to a location of your
choosing, this location is where you will point IIS (the web server)
when we can configure the website. In my environment I typically use
c:\websites\dnndev.me\ (One item of note: you may need to right click
on the ZIP file and choose Properties before extracting, on the
properties window if you have an UNBLOCK option, click that. Some
versions of Windows have started blocking files within the DotNetNuke
ZIP files, which will cause you problems later during the actual
install.)
Setup IIS IIS is the web server that comes with Windows computers. DNN
7 requires IIS 7 or later (7,7.5,8.0), so you will need at least
Windows Vista, Windows 7, Windows 8, or Windows Server 2008 R2,
Windows Server 2012.
In IIS you should create a new website (Note: If you use an existing
website in IIS be sure to add the HOST binding for DNNDEV.ME), and
point to the folder where you extracted the INSTALL package.
Note: With DotNetNuke 7.0+, .NET Framework 4.0 is required, so be sure
that your application pool is configured to run under 4.0, and not
2.0.
Set File Permissions Setting up the file permissions for your DNN
install is often the step that causes the most trouble. You should
right click on the FOLDER in which you extracted DNN
(c:\websites\dnndev.me) and choose properties. Choose the Security
tab. You need to add permissions for the account in which your
website's application pool is running under. You will want to setup
the permissions to give the account Full or Modify permissions for the
DNNDEV.ME folder. Which account you will use will vary based on your
version of IIS, here’s a simple list of some of the default accounts
based on the version of IIS.
IIS Version Operating System Account IIS 7 Windows Vista, Windows
Server 2008 localmachine\Network Service IIS 7.5 Windows 2008 R2,
Windows 7 IIS AppPool\APPPOOLNAME IIS 8 Windows 2012, Windows 8 IIS
AppPool\APPPOOLNAME
Note: If you are using IIS7.5/8.0 you’ll notice in the above table
that we have APPPOOLNAME in the identity, this is because when you
setup a new website in IIS a new application pool is created. In place
of you should type in the name of the application pool that was
created. You can also bypass this and configure your application pool
to use the Network Service account instead of a dynamic account if you
would like.
Database Configuration In SQL Server you should go through and create
a new database. I always create a database with the same name as the
website, so in this case DNNDEV.ME. Once you have created the
database, create a user that can access that database. I always use
SQL authentication, turn off the enforce password requirements, and
give the user DB Owner and Public access to the DNNDEV.ME database.
Remember the username and password you create here as you will need
them when you walk through the Installation screen for DotNetNuke.
DotNetNuke Installation Screen Populate the installation screen with
the standard DNN information, Host username, password, etc. For the
Database option, choose Custom and configure your database connection,
providing the Server IP/Name, the Database name (dnndev.me). For the
database authentication you'll want to choose the option that allows
you to enter the username/password for the database user that you
created previously.
Now there are two additional options you can configure, normally I
would tell you not to modify these, but from a development environment
perspective I do recommend that you change the objectQualifier
setting. It should be blank by default, you should type in “dnn”
(without quotes), this will prepend “dnn_” to all of the objects that
get created by DNN such as Tables and Stored Procedures. This is not
something I recommend from a production stand point, but if you are
developing modules for sale, then supporting objectQualifier in your
development is recommended. It will save you time down the road if you
have a customer who has an objectQualifier defined on their production
databases.
Follow the following video and it has total two parts one and two part links are givenbelow
Part one
Part two
I have been looking around on the internet how to setup a local Portal environment together with the RAD IDE, I found threads like this but that's a thread of the ancient history (speaking in IT terms) or only refers to optimizing Portal with RAD (here). Currently I have RAD 8.0.4.1 running and I can run a WAS-instance, but I can't manage to get the Portal-environment run locally. I read that in the past there was some sort of specific Portal Test Environment, but with the newer RAD do I have to install a full Portal? And where to get it? I cannot find a good reference anywhere.
I want to debug my portlets locally in as local Portal-context. Currently the portlets are deployed on a remote Portal-server. This costs time (package WAR, upload, refresh nodes et cetera). So I want to run our Portal locally including its portlets.
In RAD I can define new servers and can see the option "WebSphere Portal v6.1 Server on WAS 7", but it requires me to define a Server runtime environment. This opens a new popup where I have to specify:
WebSphere Portal Location
WebSphere Application Server Location
I have my runtimes installed in "IBM\SDP\runtimes" which contains the following folders "base_stub, base_v6_stub, base_v7, base_v7_stub, base_v8_stub, base_v61_stub, portal_v61_stub, updi_v7x, updi_v70, wsdk". Whatever location I try to point to, it keeps giving an error message: "The Portal Server installation is not correct".
I have the following questions:
what do I need to run/debug my portal with its portlets locally?
the fact I see portal_v61_stub in my runtime directory, means a Portal server is not installed? My IBM installation manager doesn't specifically show an option to install a Portal Server.
is it possible to run portlet/portal locally and use hotswapping to immediately see the changes in the code/view?
where can I download/install the required software?
I heard that you need a very heavy machine to do portal/debug stuff locally (I am running on a 8 GB/Intel E8400 at 3.00 GHz.)
how can I transfer the current Portal-setup which is running on a remote server to my local system (mirroring/just copy files?)
Few things,
RAD is a tool to develop application developed on Eclipse. It doesn't come with any server application. You need to install your WAS/Portal Server.
RAD supports Portal development and hence it has got stubs but you wont be able to deploy an application without a server.
what do I need to run/debug my portal with its portlets locally?
You need an Application server installed on your machine. Or Connect to a remote server.
the fact I see portal_v61_stub in my runtime directory, means a Portal server is not installed? My IBM installation manager doesn't specifically show an option to install a Portal Server.
No. Server is not installed. You dont need IBM Installation Manager for installing server. It's for RAD.
is it possible to run portlet/portal locally and use hotswapping to immediately see the changes in the code/view?
Yes it is, if you have a server installed.
where can I download/install the required software?
You can download the express version of server. But if otherwise if you are IBM business partner you can download from their website.
I heard that you need a very heavy machine to do portal/debug stuff locally (I am running on a 8 GB/Intel E8400 at 3.00 GHz.)
3 GB is fine for running RAD and IBM Websphere Portal Server. ( I am running it right now with many other applications ) But for best result use 4 GB RAM.
how can I transfer the current Portal-setup which is running on a remote server to my local system (mirroring/just copy files?)
You need to open your RAD and attach a server to it. Go to windows->preferences->servers->Webpshere
Trying to install Redmine on Windows 8 on this tutorial. Getting this errors:
Tried Bitnami's installer too, but I already have IIS Web Server and don't need the bundled Apache webserver. The installer doesn't give me to choose it's components. It installs Apache by default. So, Bitnami's Redmine is not for me.
What am I missing?
Is there any other good bug & request tracking software? Please don't Google and advise me to some random results. Advise something that you used and really good as Redmine
Once you get the error above, make sure that new WebSite's AppPool has write access to site's folder on the harddrive to complete the install process.
Then open the website in a browser and the installation will complete.
Set security accordingly after the install completes.
Use WebIssues multi-platform bug & request tracking software that fits all your needs instead of Redmine.
WebIssues is an open source, multi-platform system for issue tracking and team collaboration. It can be used to store, share and track issues with various attributes, comments and file attachments. It is easy to install and use but has many capabilities and is highly customizable.
Main features:
The Desktop Client application can run natively on Windows, Linux
and OS X
The Web Client can be used to access the system using a web browser
The server can be installed on any host with PHP 5.2 or newer and
MySQL, PostgreSQL or SQL Server
Issues can be filtered using public and personal views with
configurable filtering criteria
Email notifications can be sent and the Desktop CLient can
periodically check for new and modified issues meeting various
criteria
Various reports can be printed directly from the Desktop Client or
exported as HTML and PDF documents
I'm trying to install WSRR on Linux (Ubuntu 11.04), but without success. I think I'm lacking some important information about installation. I've read that it's a prerequisite to have WebSphere Application Server (WAS) and DB2 installed, but when I downloaded WSRR package it has its own version of WAS and during installation it offers me Derby DB. In order to install it I had to change bash for dash (or vice versa). In the end I tried create profile of standalone WSRR in Profile Management Tool but with no success. Did anybody success in installation of standalone WSRR? Please help me, I need it for my thesis.
Thank you.
So finally I managed to install and run WSRR.
First of all you have to have OpenSuse installed.
Log in as root
Reinstall you web browser (I changed mozilla 4 to mozilla 6)
Launch installation ./launchpad.sh
Create profile with Profile Management Tool GUI
Run First steps console => change directory to profile_root/firststeps/wsrr, for example, opt/IBM/WebSphere/ServiceRegistry/profiles/WSRRSrv01/firststeps/wsrr and ./launchpad.sh
Run server
Start the WSRR Web UI (if you have stand-alone server)
Not a final answer... it seems you're installing on an unsupported platform. Never try this with commercial software, you will fail or will need hours and hours to get it up and running.
I am getting the following error while installing the IBMWebsphere Studio Application Developer 5.1.2 in WinXP Pro.
" The installation of WebSphere Studio cannot continue because the following required parts are missing from the electronic images. Download the required parts and run the installation program again.
C571ILML.bin "
I am installing from the local hdd (d:/temp/disk1, disk2,disk3 and disk4) of setup program.
Can any body help me what could be the problem and how to solve this to install the IBM WAS.
Two questions.
Does that file exist anywhere in your install tree?
Check it again please, most codes are only 7 characters. The closest I've found is C57I1ML but that's part of Websphere Studio Site Developer 5.1.2. And, on top of that, WSAD 5.1.2 seems to have the C80 prefix.
BTW, there's no C571ILML anywhere on the IBM intranet that I can see.
EDIT:
The standard Websphere Studio Application Developer 5.1.2 for Windows has five disk images located on IBM's Xtreme Leverage site, those being C802XML, C802YML, C802ZML, C8030ML and C804UML.
I suspect your missing file is due to the fact that you only have the contents of four of those disk images.
You'll need to go back to your source and get the other disk image (or contents).
Alternatively, you may have the Integration Edition, in which case I'll need to look again - please clarify which one you have.