Frequently Asked Questions
Can I get WSO2 Updates free?¶
You can use a trial subscription for 90 days.
Find out more about WSO2 Subscriptions
What are the benefits I get from a subscription?¶
A paid subscription allows you to:
- Deploy updates into your production environment immediately, without waiting for an open source release.
- Receive 24x7 support from WSO2 to resolve issues quickly.
- Help fund our ongoing R&D and operations.
Find out more about WSO2 Subscriptions
How often WSO2 Updates will be releases to the user?¶
Updates will be released bi-weekly as new update levels. Follow the updates commands in Updates command page
In production environments, WSO2 will announce urgent security fixes to customers via support JIRAs. In addition, WSO2 will announce all security updates, if any, to the customers monthly. Therefore, It is recommended to update your production environments monthly.
How can I update my product pack if my environment doesn't have Internet access?¶
First, update the product pack in an environment that has Internet access. Thereafter, transfer the updated pack to the lockdown environment.
Do I need a key to unlock updates for production?¶
No. We trust our customers to adhere to the license terms. We make the terms clear to avoid accidental violations and reserve the right to remove access to updates or take other means to enforce the license against intentional violators.
Find out more about the EULA license.
Can I choose which updates to install?¶
You can choose to update your product into a specific update level. This will update the product from the existing level to the chosen level, applying the updates in between.
What license are WSO2 updates on?¶
We are releasing WSO2 updates with a commercial EULA license. Find out more about the EULA license.
Should I test my updates and hotfixes?¶
WSO2 takes accountability to test all updates and hotfixes thoroughly in systems where all previous updates are installed. However, it is best to install the updates or hotfixes to either your development, staging or testing environment that has the same product distribution that runs on your production environment, execute test run and thereafter apply to the production environment.
How do I know when updates are available?¶
You can be aware of the latest updates from WSO2 by logging into Updates Portal.
Where can I find description and instructions related to specific updates and hotfixes?¶
What can I do in case of an issue?¶
If you encounter any issues when using WSO2 updates, report a ticket at Support JIRA. Please be sure to attach the
details of the error when you report it. You can get the details by getting the log files in
updates/logs in the product directory.
How can I know what changes are included in an update?¶
You can check the changelog of an update by log into the Updates Portal.
I get the error as 'invalid credentials. Please enter valid WSO2 credentials'. What should I do?¶
Check whether you have given the correct WSO2 credentials. If yes, check whether your password has the $ sign. If yes, escape the $ sign using escape character '\'.
Example Password - 123$abc Should be entered as 123\$abc
Should I change configurations when a proxy server/firewall is running?¶
Yes. WSO2 updates are received by connecting to the
https://product-dist.wso2.com and https://wso2.com. If your system connects to
the Update service through a proxy server/firewall, whitelist the above-mentioned endpoints.
Since WSO2 update tool is a command-line tool, the proxy should be configured from your command-line using below command:
If you are behind an NTLM proxy, you can use a third party tool like CNTLM to do the NTLM proxy authentication. See the CNTLM documentation for instructions.
Do I have to run the update tool in all the servers in my environment?¶
This is not a WSO2 recommended approach. If you have several servers running in your environment, it is prudent to use a Configuration Management System. In this way, you update the product pack once and distribute the same using the Configuration Management System to other servers.
What are the recommended configuration management tools to deploy configurations to client nodes?¶
WSO2 recommended configuration tools to work with when using WSO2 updates are Ansible and Puppet.
WSO2 APIM: https://github.com/wso2/ansible-apim/blob/master/README.md WSO2 EI: https://github.com/wso2/ansible-ei/blob/master/README.md WSO2 IS: https://github.com/wso2/ansible-is/blob/master/README.md
WSO2 APIM: https://github.com/wso2/puppet-apim/blob/master/README.md WSO2 EI: https://github.com/wso2/puppet-ei/blob/master/README.md WSO2 IS: https://github.com/wso2/puppet-is/blob/master/README.md
How to use update commands in automation scripts?¶
Update tool client supports use of flags for user input values and exit codes for commands.
- Use user input commands
- Use exit codes
Are the updates I get from the Updates Client is secure and assures authenticity?¶
The Update tool communicates with the WSO2 Update Service to get details of the updates that need to be downloaded and applied. During this communication,
the following information is obtained from the WSO2 Update Service:
1. Artifacts to be downloaded.
2. md5sum values of the artifacts.
3. Several other metadata required for the next invocations.
After getting information on the updated files, the Update tool makes an authenticated invocation to the CDN to download the necessary updates. The client’s communication with the WSO2 Update Service and CDN are secured through HTTPS.
After the necessary files have been downloaded, the Update tool validates the authenticity of the files by comparing their md5sum values with the values obtained from the WSO2 Update Service in the initial step. This ensures that the files have not been tampered with after the download is complete. Thereafter, the Update tool applies the downloaded updates and creates an updated product distribution.
How can I get docker images with updates and how will those be distinguished?¶
Navigate to official WSO2 Docker Repository observe all the docker images for that chosen product listed,
select the docker image based on
<update-level> and the optional
<docker-file-version> represents the docker file version that was used to build this image for reference purposes (you may disregard this value).
Naming conversion of docker images is as follows: