Wso2 carbon/apimgt open source code download - wso2-api-manager

I have downloaded the wso2 open source of master branch from github, but the build is failing. Can anyone guide me in the right direction? How do I get the publisher and store of wso2 api mananager up?

Make sure you install nodejs and java8(or higher) to your computer. you can try with any version after checking out to the particular tag or if you want the latest release pack, go with the master branch. First build the carbon repo(https://github.com/wso2/carbon-apimgt) and after you build the carbon repo then take the version(it's in main pom file()) of that and update carbon version(<carbon.apimgt.version>) of the product-apim(https://github.com/wso2/product-apim/) main pom file(it's already included a carbon version, replace it to your version). Then build the product-apim.

The master branch is the ongoing development branch. Hence could you please refer this link [1] to get start the WSO2 APIM. This will guide you on how to start publisher and developer portals.
[1]. https://apim.docs.wso2.com/en/latest/getting-started/quick-start-guide

What is the maven version you have in your windows machine? When working with windows it is highly suggested to use compatible versions rather than the latest versions.

Related

Migrate Jforg repository from version 5.1.0 to newer version 7.x

I would like to replace a physical jfrog server with a virtual one with a newer version of jfrog.
But I want to move the old repositories, not all of them, just some.
Does anyone know how I can achieve that?
I am reading the documentation which doesn't recommend exporting and importing from two different versions.

How do I install pglogical extension on Windows machine?

I need to migrate an enterprise production database from a Windows source machine running Postgres 9.5 to an Ubuntu destination machine running Postgres 11.6 with < 15 mins downtime. I plan to do this with pglogical, which requires the extension being loaded on both source and destination. I am having trouble with the source side because it is Windows.
I have very little Postgres-Windows experience and can neither find any helpful literature on the specific situation nor can I figure out for myself how to presumably install from source.
I've dug and dug and so far the only answer I've been able to find is "ugh... Windows". It seems like the only way to build from source is using Visual Studio, which I don't have or know how to use.
Sources:
https://www.2ndquadrant.com/en/blog/compiling-postgresql-extensions-visual-studio-windows/
https://postgrespro.ru/list/thread-id/1835275
Alex, the 2ndQuadrant article you link to in your own comment solves this. A few of the project or build options noted there have moved a little bit in the newer VisualStudio Community editions, so I can see where you got hung-up.
Just for kicks I compiled 32-bit DLL on my oldest Windows instance. I included the /Release path so you can grab my DLL & see if it works for you. It's (a) 32-bit because I'm assuming worst-case for an old v9.5 install, and (b) targets Postgres 9.6 because that's what I had installed. Unless there were major API changes though, it should connect to v9.5 without any issues:
https://github.com/mbijon/winpglogical/tree/master
If you find you need a version that entirely matches Postgres 9.5, grab my solution files & VS Community 20xx. Load the project & update the Additional Include Directories in Project Config to target your v9.5 paths. That should be all that's needed to link v9.5 Postgres libs.

Msi installer stopped working

I previously installed a website on the server by running an msi package and everything worked fine. Now, when I try to run the same msi file (to Repair/Uninstall), I get a message:
When I click Cancel, I get the following message:
Anybody has an idea what happened and how it can be fixed?
I would recommend that you run the MSI with logging enabled. This can be done by using the /l*v C:\mylog.txt switch or by modifying the registry. The log will provide you with more precise information as to what is going wrong during the msi process.
The articles below describe how to enable logging and the logging process in more detail
http://support.microsoft.com/kb/223300
http://technet.microsoft.com/en-us/library/cc759262(v=WS.10).aspx
http://msdn.microsoft.com/en-us/library/aa372847(v=vs.85).aspx
Once you have the log you can use a set of MSI tools like the Orca installer database editor tool on the Windows SDK to correct any issues.
This is the link for Windows 7 SDK which contains the msi tools.
http://www.microsoft.com/en-us/download/details.aspx?id=8279
Sorry for answering my own question, but I found the problem and I want to share the solution:
After I installed the old version on the server, I changed the name of the msi file. Consequently, I could not run the old version to repair/update. I could not even install a newer version over the old version, as the installer needed the old msi to uninstall the old version.
When I changed back the filename of the old version, it allowed me to install the new version.
CONCLUSION: Don't change the name of the msi file after installation.

Cloudera-manager 4.7

Has anyone else had trouble with the new release of Cloudera manager? '4.7' With brand clean ubuntu vm nodes it seems to be placing a file in /etc/apt/sources.list.d called cloudera-manager.list with "http://archive.cloudera.com/cm4/ubuntu/precise/amd64/cm/ precise-cm4.7.0-SNAPSHOT contrib pointed" to as the source, however this url does not exist and when ever it tries to install my nodes if fails.
Does anyone know where this url is kept on the manager so I could change it before it sends it to my nodes?
Greg,
The repository URL is constructed based on the version of the CM server that you are running. So if the server is reporting itself as "4.7.0-SNAPSHOT", then that's what the node installer will use. Now, we've not published any release that describes itself as 4.7.0-SNAPSHOT, so I'm left scratching my head as to how you got into this situation. If you still have that installation, I would recommend that you:
1) Check the reported version of the server from the Support menu at the top right.
2) Check the full package version(s) as reported by "dpkg -l | grep cloudera"
so that we can establish where the build came from.
Thanks.
PS: The installer url you reference in your update is the latest installer and not a 4.6 installer. It's the one people should use for sure.

Is There A Way To Install Unstable Version of Plugin via Built-in Plugin Installer

I'm wondering if there is a way to install an unstable version of a published plugin.
Let's say I updated my plugin version 1.0 to 1.1.
Then I put Stable tag: 1.0 in the readme.txt file so that everyone downloads the stable version v1.0.
Now my question is that if I want to test the unstable version on one of the remote servers, isn't it possible to install v1.1 with the built-in plugin installer?
I'm currently doing this way:
deactivate the old version
delete the plugin
upload the unstable version
activate it.
If the updating process could be shorten this way, it would really save my time.
search and find the plugin name to install in the Add New page.
click on the unstable version link.
Thanks for your information.
I'm not sure that this is the answer you are looking for but...
I was running into the same issue and instead what I have chosen to do is actually edit my plug-in on a "test-bed" site. I have a site that I test all of my modifications on before publishing and I access the files directly via FileZilla FTP Client.
This allows me to take the most up to date file from the server, edit it on my machine (using Notepad++) and upload the change to the server for testing. If it breaks the site in some way I can always re-upload the original via FTP and everything is back online.
Hope this helps!

Resources