As I know solace use modified Linux , Is there anyway we can find the Linux version of Solace Appliance.
Show version displayed the Solace appliance TR-version but wanted to know the which veriosn/flavor of Linux is used for solace appliance.
This is dependent on the version of SolOS that the appliance is running. SolOS 7.2 uses a modified CentOS 7.2 for its control plane.
Related
I'm looking for a solution to run IBM MQ Client under a Windows Docker container. I know that Docker Hub only provides Linux implementations of MQ, however, I do not need full MQ Server capability. Instead, I'm hoping there's a means to install the MQ Client and simply connect to a Channel and Queues defined on another (non-Docker) system. To approach this, I've done the following:
Spun up a Windows Docker container running under a command prompt (For proof of concept)
Copied in and expanded MQ Client 9.0.0.8-IBM-MQC-Win64.zip
Silently installed MQ Client (e.g. msiexec /i "c:\temp\Windows\MSI\IBM MQ.msi" /l*v c:\temp\install.log /q TRANSFORMS="1033.mst" AGREETOLICENSE="yes" ADDLOCAL="Client").
Note: The installation was successful and without error
Established required environment variables(MQServer, etc.) and updated paths (classpath, lib, include, etc).
Pinged the MQ server system to verify connectivity.
I attempted to put a message on a working, verified queue using, amqsputc.exe MYDOCKER.DS.Q. The immediate return code is MQCONNX ended with reason code 2195. Unfortunately, 2195 is pretty generic and there are no other logs available to review.
I understand the differences between running MQ under a VM versus a container, however since I only need Client access, I was hoping MQ Client was lightweight enough to be usable.
If MQ Client is not a viable direction, is there an MQ solution which might be doable via a Cloud connection? My legacy application is Windows-based and relies on MQ for job messaging.
Instead of installing the Full client install using msiexec, I would recommend that you use the IBM MQ Redistributable client install. This is packaged as a simple zip file for windows which you can extract into any location you choose.
You can find more information about the Redistributable client on the Knowledge Center page Redistributable IBM MQ clients.
You can download the IBM MQ Redistributable clients using the links below:
IBM MQ 9.1 Redistributable client.
IBM MQ 9.2 Redistributable client.
Note: IBM MQ 8.0 is out of support as of April 30th 2020 and IBM MQ 9.0 is going out of support on September 30th 2021.
The IBM Knowledge center page
Limitations and other considerations for redistributable clients gives these requirements:
Windows C runtime libraries
You might have these libraries on your machine already, but if you do not, you need to download and install the following Microsoft C/C++ runtime libraries:
Microsoft Visual C++ Redistributable 2008
Microsoft Visual C++ Redistributable 2012
The download links for the redistributable downloads for each of these libraries can be found at The latest supported Visual C++ downloads.
A possible alternative (and lighter) approach: Write a Go app using the IBM mq-golang package and deploy that in your Windows docker container.
https://github.com/ibm-messaging/mq-golang
Is there a way to run a Docker container in Windows IoT Core? I have seen it can be used in Azure, Windows Server and desktop W10 but there is no evidence about Windows IoT Core and I am not sure if some of the already existing installations of docker-engine is compatible with IoT Core or it is just not possible.
Last Friday, Azure IoT Edge v2 launched in Public Preview yesterday with out-of-box support for native Windows containers! There is even a how-to for deploying on Windows IoT Core with a compatible x64-based board*.
First party modules like Azure Functions, Azure Stream Analytics, Modbus and a cool developer experience in VS Code for authoring custom modules all work great with Windows containers on both Windows 10 and IoT Core.
*Note: Windows containers require x64-based processor support, they won’t work on ARM32-based devices like Raspberry Pi.
As of IoT Core version 16299, released on 17 October, this feature is in preview.
https://developer.microsoft.com/en-us/windows/iot/docs/whatsnew
You can run Nano Server Core containers on 64-bit Windows 10 IoT core. It is likely to be amd64 only at this point.
The short answer is, no. This is because Windows 10 IoT Core is an OS that supports a set of features that overlap with Windows 10 desktop, but there is no version of Docker that runs on that currently. Off the top of my head, there would be a few concerns with creating such a version. First, the implementation of Docker would have to be runnable (use features that the OS supports), and second, the features utilized in the container would need to be virtualized by Docker in form that are supported in Windows 10 IoT Core. Third, the hardware running Windows 10 IoT Core (and Docker and its container) would have to support all these functions. Maybe some do and some don't. The problem might be whether or not the hardware such as a Raspberry Pi or Minnowboard supports virtualization in a way that this would be a practical scenario.
My thingsboard service does not start or can't find one after installing the rpm package in amazon ami. There is no .sh file in find only a jar and yaml file.
The Thingsboard RPM package you are using is verified on CentOS 7. The issue is that Amazon Linux AMI is not compatible with CentOS 7. See this AWS forum thread for more details.
Maybe we will support AWS Linux in future releases, but for now, I suggest to use officially supported Linux versions.
You can get started with Thingsboard using our free live demo server or by using pre-defined AMIs that are available for all regions.
Thanks,
Andrew
We are currently running Red Hat 5. But I saw documentation that says docker is only supported on Red Hat 7. So we have to upgrade to Red Hat 7 or we can't use docker at all on RHEL 5? Alternatively we can consider to switch to Ubuntu.
How do others solve the similar issue?
You will need to upgrade from RHEL5 to use Docker.
The official Docker release deprecated RHEL6 support from 1.7 (and inadvertently broke it in 1.7.0 but fixed in 1.7.1). Support for RHEL6 was dropped in Docker 1.8. Since then, a RHEL7 based distro with a 3.10+ kernel has been required.
There is a docker-io-1.7.1-2 package available on EPEL for RHEL6.5+ based distros. RHEL6 runs an older 2.6 kernel with back ported fixes so docker can work. This kernel must be at 2.6.32-431 or higher.
RHEL doesn't support AUFS which is the most commonly used Docker storage driver. By default RHEL uses a loopback storage driver which is not production ready. The EPEL packages provide docker-storage-setup to setup thin provisioned LVM. You need to do this setup manually if you want to run the docker.com packages.
Personally I would recommend going with a recent debian based distribution running the official docker packages for timely updates. If you are on EC2, Amazons AMI will do nicely though.
Is it possible to develop 3rd party apps that will be run on the ESXI 5.0 host machine? For example, daemon that monitor the ESXi machine.
Is it possible to compile application on Red Hat Linux and then install them on the ESXi machine? Should we use specific development environment?
Where can I get information regarding development for ESXi?
You can use the toolchain provide by VMware. WMware provides 3 different version toolchains for their OSes.
ex. ESXi 5.5 toolchain
https://my.vmware.com/web/vmware/details?downloadGroup=ESXI550_OSS&productId=353
Yes, only what you need to do is to compile your application with static. And yet one: with vmware esxi, there is only a very limited /proc!
If my understanding is correct, you probably want to do kernel module or userworld development.
Typically, only vmware partner can get the vShpere kmdk devkit. Please find more info here https://developercenter.vmware.com/dcpn-faq.