I would like to install servlet 3.1 on Websphere Liberty Core 8.5.5.7.
I cannot reach the the Liberty repository so I can't use :
installUtility install servlet-3.1
How can I install servlet-3.1 manually without connection ?
You need a other computer with Liberty Profile 8.5.5.2 or higher and internet connection.
You can download in this computer the needed features with featureManager utility with --downloadOnly option.
bin/featureManager install feature_shortName1 feature_shortName2 --downloadOnly=[all|required*|none]
You can specify a local destination directory with --location optinon.
Then copy the download directory in your computer without internet connection and install the feature:
bin/featureManager install feature_shortName1 feature_shortName2 --location=directoryPath
More information in:
https://www.ibm.com/support/knowledgecenter/SSAW57_8.5.5/com.ibm.websphere.wlp.doc/ae/t_install_assets_cmd.html?lang=en
you can download the .esa file form IBM website then install it with the command
installUtility install localrepo3\com.ibm.websphere.appserver.servlet-3.1.esa
where localrepo3/ is a directory in the bin directory of WebSphere
Related
I want to install the "Web Server Plug-ins for IBM WebSphere Application Server V9.0" without the IBM InstallationManager just with an archive file.
The archive installation was already possible for the "IBM HTTP Server V9.0" from e.g.: https://ak-delivery04-mul.dhe.ibm.com/sar/CMA/WSA/086do/0/9.0.0-WS-IHS-ARCHIVE-linux-x86_64-FP011.zip and just run the postinstall.sh. But for the aforementioned Web Server plugin, I cannot find an archive to download.
Does anyone know if such an Installation is possible?
The "IHS" archive install includes the WAS Plug-in files you need for IHS in a plugins/ sub-directory off the root. No 2nd download is required.
If you need the WAS WebServer Plug-ins for some other webserver, the IM install is your only option.
We need to configure MQ QUEUE PLUG-IN connecting a RHEL Linux server. Below is version details.
Name: WebSphere MQ
Version: 8.0.0.5
Level: p800-005-160516.2
BuildType: IKAP - (Production)
Platform: WebSphere MQ for Linux (x86-64 platform)
Mode: 64-bit
O/S: Linux 2.6.32-754.2.1.el6.x86_64
http://resources.itrsgroup.com/docs/geneos/4.4.0/Netprobe/middleware/mq-queue.html
As per ITRS support we need libmqic.so - which is part of MQ Client Package. But since the server has MQ server installed we are not keen to install MQ Client.
So question is.
Can MQ Server and Client co-exist in same server ?
Its not logical that MQ server do not have equivalent of libmqic.so package. What is the equivalent of this in server installation ?
Can we just copy libmqic.so from a client installation and use ?
Any input on this would be great. Thank you.
Regards,
Dwija
The MQServer bundle from IBM includes RPMs for both client and server libraries.
You can check what is installed with this command (sort/paste/column just format it nice):
rpm -qa | grep MQSeries | sort | paste -s -d' \n' | column -t
You should see something like the following:
MQSeriesClient-8.0.0-4.x86_64 MQSeriesClient-U8005-8.0.0-5.x86_64
MQSeriesGSKit-8.0.0-4.x86_64 MQSeriesGSKit-U8005-8.0.0-5.x86_64
MQSeriesJava-8.0.0-4.x86_64 MQSeriesJava-U8005-8.0.0-5.x86_64
MQSeriesJRE-8.0.0-4.x86_64 MQSeriesJRE-U8005-8.0.0-5.x86_64
MQSeriesMan-8.0.0-4.x86_64 MQSeriesMan-U8005-8.0.0-5.x86_64
MQSeriesRuntime-8.0.0-4.x86_64 MQSeriesRuntime-U8005-8.0.0-5.x86_64
MQSeriesSamples-8.0.0-4.x86_64 MQSeriesSamples-U8005-8.0.0-5.x86_64
MQSeriesSDK-8.0.0-4.x86_64 MQSeriesSDK-U8005-8.0.0-5.x86_64
MQSeriesServer-8.0.0-4.x86_64 MQSeriesServer-U8005-8.0.0-5.x86_64
The 8.0.0-4 packages are the base install and the U8005 packages are the update to fixpack 8.0.0.5.
As long as you have the MQSeriesClient* packages installed you will have access to the libraries required by ITRS NetProbe MQ QUEUE PLUG-IN.
I do not know of any reason why a MQ Admin would have an issue with installing those packages that come as part of the MQ Server bundle.
If there is some reason they do not want to install those packages then another work around is to download the redistributable client (google MQC8 for the download link). You can just extract the tar into any location on the server and then make sure the LD_LIBRARY_PATH points to the locate you extracted the files to either the lib (32bit) or lib64 (64bit) sub directory. You can run file netprobe to check if it is 32bit or 64bit to see which is appropriate. If you need more details on this option let me know and I can add more.
I'm trying to deploy a Vaadin 7 example.war file in tomcat 7, using an EC2 server. I upload the file to /var/lib/tomcat7/webapps but then when I go to myIp:8080/example it doesn't find the resource.
Any idea why?
Thanks!
You have to use the tomcat manager (usually http://[YourHost]:8080/manager) to add a new webapp / war file, it is not just uploading the file to the webapps folder.
To install tomcat, the manager webapp, and configuring access credentials (debian or debian based distros), check this tutorial: https://www.digitalocean.com/community/tutorials/how-to-install-and-configure-apache-tomcat-on-a-debian-server
Solved!...
To install the manager:
sudo yum install tomcat7-webapps tomcat7-docs-webapp tomcat7-admin-webapps
To solve the Java Version mismatch, org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/prueba2]]:
On Eclipse:
Preferences >> Java >> Installed JREs
On EC2 server:
sudo yum remove java-1.7.0-openjdk
sudo yum install java-1.8.0
Then reinstall Tomcat7 and restart
Thanks #BlunT for all the help!!
Our security team has scanned our production server and identified vulnerabilities with Apache Tomcat server v 6.0.20.
They have recommended that Apache be upgraded to 6.0.24. Reading through the forums, I believe this is the process to do so
Take a backup of httpd.conf file
Using add remove programs, uninstall version 6.0.20
Install 6.0.24
But, I have some questions depending on a quick test I did to install 6.0.20 and upgrade it to 6.0.24
Where do I get Tomcat administrator login information?
Is it enough just to backup the HTTPD.CONF file? I was thinking to back up everything in the Apache folder instead.
Is it possible not to upgrade 6.0.20 to 6.0.24 by running the MSI installer over the same Apache folder? Is it due to the HTTP/1.1 Connector Port being busy/used that doesn't allow an update of Tomcat on the same port?
Is a restart of the server required after upgrade?
Last but not the least, I am using these executables to test the upgrade. 6.0.20 gets installed fine but when I run 6.0.24, it prompts me for the JRE path and directing it to 6.0.20 JVM Path gives me a message that "JVM is not found". The JVM info on the Apache manager is in this directory
What am I missing here?
I need your thoughts and advice to make this as easy as possible since this is a production server.
I have installed WAS 8.5 Trial version on Windows 7. I would like to deploy and run Java 7 application. Is it possible to do it?
I can not see "IBM WebSphere SDK for Java Technology Edition 7" in the IBM Installation Manager's feature list and there is no SDK 7 installed, yet.
>managesdk.bat -listAvailable
CWSDK1003I: Available SDKs :
CWSDK1005I: SDK name: 1.6_64
CWSDK1001I: Successfully performed the requested managesdk task.
>
Has somebody managed to make WAS 8.5 Trial and Java 7 work together on Windows 7?
Thanks in advance!
I've just found one of the possible solutions...
Select the method "Download Director or HTTP" instead of "Installation Manager (Recommended)" at the download page of Evaluate: IBM WebSphere Application Server. Then you get a list of products to download which contains "IBM WebSphere SDK Java 7, Installation Manager repository".
Select and Download all parts of the product and extract the three part to the same directory.
Start your previously installed Installation Manager and add the directory as a new repository under File > Preferences > Repositories, then press OK.
Now you can choose Install and you can select IBM WebSphere SDK Java Technology Edition (Optional) from the list of available packages.
After the installation is completed you can check if everything went well.
>managesdk.bat -listAvailable
CWSDK1003I: Available SDKs :
CWSDK1005I: SDK name: 1.6_64
CWSDK1005I: SDK name: 1.7_64
CWSDK1001I: Successfully performed the requested managesdk task.
>
The Java SDK 1.7 is installed and you can set it as the default SDK in the Administrative Console of your server.
Server > WebSphere application servers > server > Server Infrastructure > Java SDKs
Sorry for the stupid question, I wasn't careful enough...
Firstly install the JDK 1.7 or any required version supported.(find the available using the command - managesdk.bat -listAvailable)
Then Go to the Installed WAS Server DIR and then navigate to bin folder
C:\Program Files (x86)\IBM\WebSphere\AppServer\profiles\AppSrv02\bin
For ALL Profiles
managesdk -enableProfileAll -sdkname SDK_Name -enableServers
From there execute this command(In Windows)
C:\Program Files (x86)\IBM\WebSphere\AppServer_2\profiles\AppSrv02\bin>managesdk
.bat -enableProfile -profileName AppSrv02 -sdkname 1.7_64
It gives this message to confirm.
CWSDK1017I: Profile AppSrv02 now enabled to use SDK 1.7_64.
CWSDK1001I: Successfully performed the requested managesdk task.
(In Linux)
/opt/IBM/WebSphere/WSRR/v8.5/bin/managesdk.sh -enableProfile -profileName AppSrv02 -sdkname 1.7_64
Note: AppSrv02 is the server name used in my local. Replace the name with your actual thing.