https://docs.wso2.com/display/AM210/Upgrading+from+the+Previous+Release
I am following this to upgrade WSO2 API-M 2.0.0 to 2.1.0.
My 2.0.0 API-M has custom url configured and https certificates configured to map the url.
If i follow the migration as in the document , Will these things gets automatically migrated? Or will i have to manaully change the url in all the configuration files and also do the changes for https ?
I believe you are referring to [1] which is configuring custom URLs per tenant. If so you do not have to redo these configuration in the registry since the new deployment will be pointing to the same registry database as given in the migration documentation.
The changes done to configuration files in the file system, has to be re done in the APIM 2.1.0 pack. You can do a diff of the file system and do those changes.
The SSL certificates also have to be imported again. As an alternative, you can copy the keystores and truststores to the APIM 2.1.0 from the older version instead.
[]https://docs.wso2.com/display/AM200/Customize+the+API+Store+and+Gateway+URLs
Related
I have deployed WSO2 API manager4.0.0 All-in-one on my vm, which was downloaded from WSO2 API Manager website, “click TRY IT NOW, and then click Zip Archive to download the API Manager distribution as a ZIP file”.
I could find component versions from pom.xml , which were under the path of \repository\deployment\server\webapps. Most of the war or jar were built from carbon-apimgt and identity-governance、identity-apps.
But I can't find where was the front version, I don't know what' difference between repo apim-apps and jaggery.
If apim-apps is the front source of apim, what's the version or tag it build from?
I am searching for a long time on net. But no use. Please help or try to give some ideas how to achieve this
UI source code was moved to apim-apps repository after the WSO2 APIM 4.0.0 release. So, if you want to access the UI source code of APIM 4.0.0 you have to refer to carbon-apimgt-v9.0.174. Following are the links to each portal.
Publisher Portal
Developer Portal
Admin Portal
I'm pulling my hair out. I've got an On Prem installation of Azure DevOps, and a pair of build agents. We're trying to move to .net core, but we have never been able to get it to work to push the nuget packages into DevOps feed. This should be straight forward.
The whole environment is hidden behind corporate firewall and proxy, and while the proxy config is good for nuget pull, and any other activity you care to name, we cannot invoke nuget push (or dotnet push) to our internal package repository. The only error I get is a 502 (bad gateway) from tunnel.js, but I've explicitly set the address of the DevOps server in NO_PROXY (environment variables, .proxy & .proxybypass for the devops agent, netsh winhttp proxy, build agent user internet connection settings, and %AppData%\Nuget\Nuget.Config file). Git works, nuget restore works, build works, packaging works, but the dotnet push (or nuget push) fail with this error.
Can anyone suggest any other places I might need to set a proxy bypass or no_proxy setting?
There can be many reasons why you are getting this problem, which may be related to your organization network, users roles and permissions or even task may be restricted by any policy.
But if above mentioned things are not true in your case then you should configure NuGet tools to authenticate with Azure Artifacts and other NuGet repositories. If all of the Azure Artifacts feeds you use are in the same organization as your pipeline, you can use the NuGetAuthenticate task without specifying any inputs. Check this Restore and push NuGet packages within your organization document for more information.
This task must run before you use a NuGet tool to restore or push packages to an authenticated package source such as Azure Artifacts. This task installs the Azure Artifacts Credential Provider into the NuGet plugins directory if it is not already installed.
If your agent is behind a web proxy, the NuGetAuthenticate will not set up nuget.exe, dotnet, and MSBuild to use the proxy. Then set the environment variable http_proxy and optionally no_proxy to your proxy settings as shown below.
nuget.exe config -set http_proxy=http://my.proxy.address:port
nuget.exe config -set http_proxy.user=mydomain\myUserName
Check this NuGet CLI environment variables for more information.
Is the a configuration file for Cloudera Management Service?
I'd like to have the service roles' configuration stored in repository. This way, service configuration can be shared between environments without the need to change the configuration via CM ui or rest API on each environment.
Cloudera deploys configs for those dynamically when service is started by agent, for example Service Monitor will end up in /run/cloudera-scm-agent/process/XXXXX-cloudera-mgmt-SERVICEMONITOR
Config itself is stored in database, in configs table.
So I would say that your only solution (sadly) is to manage config via api. Client libraries for that are pretty friendly though.
I'm trying to configure WSO2 Identity Server as a key manager for WSO2 Api Manager by following this tutorial.
In that, under step-4, following instructions are there.
For this purpose open the /repository/conf/api-manager.xml
file and change the element that appears under the
section, so that it points to the API Manager server.
But there is no api-manager.xml file inside <IS_KM_HOME>/repository/conf/. I'm using WSO2 Identity Server 5.6.0.
Does anyone know where can I find this api-manager.xml file?
This XML file exists only in WSO2 IS as a Key Manager (WSO2 IS-KM). Please refer[1][2]. You can download the IS as KM from [2]. For API Manager 2.6.0, IS as KM version is 5.7.0. IS 5.6.0 is not a Key manager hence it will not include that configuration file.
[1]https://docs.wso2.com/display/AM260/Configuring+WSO2+Identity+Server+as+a+Key+Manager
[2]https://wso2.com/api-management/install/key-manager/
Thanks
Bamboo supports shared credentials.
I would like to use these shared credentials to commit tags to git using the artifactory maven addon.
According to this ticket: https://www.jfrog.com/jira/browse/BAP-189 it should work.
I do however not know where to configure it.
We are using bamboo 5.14.3.1
Artifactory plugin 2.1.0
Was this feature removed?