I followed the official guide to set up a cluster (Clustering AS 5.3.0) (https://docs.wso2.com/display/CLUSTER44x/Clustering+AS+5.3.0).
and also configured the SVN-based Deployment Synchronizer.
but i cannot found the "Deployment Synchronizer" page on mgt console (https://localhost:9443/carbon/deployment-sync/index.jsp.)
<DeploymentSynchronizer>
<Enabled>true</Enabled>
<AutoCommit>true</AutoCommit>
<AutoCheckout>true</AutoCheckout>
<RepositoryType>svn</RepositoryType>
<SvnUrl>https://10.13.46.34:8443/svn/repos/as</SvnUrl>
<SvnUser>svnuser</SvnUser>
<SvnPassword>svnuser-password</SvnPassword>
<SvnUrlAppendTenantId>true</SvnUrlAppendTenantId>
</DeploymentSynchronizer>
So, anyone can tell me how to find the deployment-sync page?
Similar page(WSO2 4.1.2 ):
thanks!
That page is not longer exist in any of the WSO2 products.
When you have a cluster of WSO2 products, the master node will notify the worker nodes through a cluster message when there is a change in artifacts, so that, worker nodes will synch up the changes through SVN based deployment synchronizer.
You can achieve it through cronjob. You don't really need to have SVN-Based Deployment Synchronizer.
Related
I Google Cloud's ErrorReporting the "Seen in" section doesn't show anything useful for my GKE deployments. It's either empty or says gke_instance which is pretty useless. I have set the serviceContext correctly in my logs and the container name is also set in the labels of the log entries and yet it's not showing up. Is this a bug or am I missing something obvious here?
To resolve your issue try below 3 solutions :
Solution 1 : If you're using Legacy Stackdriver disable it and enable Stackdriver Kubernetes Engine Monitoring, for more information refer to the similar Stack Question.
Solution 2 : As stated by this release notes, the stackdriver agent actually becomes disabled by default in 1.15. To activate it again you need to edit the cluster following these instructions. Also refer to this Stack Question.
Solution 3 : If a new GKE cluster has Cloud Operations for GKE set to System and workload logging and monitoring, however no application logs are showing up refer to this Stack Question.
Note : Issue was the node pool using the default service account (which no longer existed). Created a new node pool following the document.
I am trying to setup Active-Active setup for the WSO2 API Manager by following this url:Configuring an Active-Active Deployment
Everything is working fine except step 5 where I am trying to setup NFS. I moved /repository/deployment/server folder to another drive. For e.g. at location:
D:/WSO2AM/Deployment/server
so that both nodes can share deployment folder together.
Now not knowing what config files to change to point deployment folder to location other than default, I made changes to carbon.xml and made changes to an element "RepositoryLocation" and set it to D:/WSO2AM/Deployment/server but uit looks like it is not enough. When I start the server, I get the following error messsage:
FATAL - SynapseControllerFactory The synapse.xml location .\.\repository/deployment/server/synapse-configs\default doesn't exist
[2019-03-12 15:54:49,332] FATAL - ServiceBusInitializer Couldn't initialize the ESB...
org.apache.synapse.SynapseException: The synapse.xml location .\.\repository/deployment/server/synapse-configs\default doesn't exist
I will appreciate if someone can help me setup NFS so that both nodes can share same deployment folder and I don't have to worry about syncing them through some other mechanism.
Thanks
After struggling for almost a day, I found a solution in WSO2's completely separate thread.
Enable Artifact Synchronization
In this thread, they are asking to create a SMB share (for Windows) for Deployment and tenants directory, for APIM purpose, we need to create SMB share for the directory /repositiry/deployment/server directory.
It is just one command away to create a symbolic link as seen below:
mklink /D <APIM_HOME>/repositiry/deployment/server D:\WSO2\Shared\deployment\server
We need to create symlink in both nodes to point to the same location.
Once done, no configuration changes needed on APIM side. It will work by default and you have following scenario configured.
As per the documentation https://docs.wso2.com/display/AM250/Deployment+Patterns#DeploymentPatterns-Pattern2 I am trying to setup WSO2 similar to Pattern 2. But from the documentation it is not quite clear what are the steps that needs to be followed.
Question:
1. How can I start Store, Publisher and Traffic Manager on same server?
Do I have to start them in single startup script or start them independently? When I try starting them independently I see there are conflicts. How to resolve those conflicts?
Regards,
Deepak
Question: 1. How can I start Store, Publisher and Traffic Manager on same server? Do I have to start them in single startup script or start them independently?
If you start the default WSO2 API Manager (without any profile parameter), it starts the "all-in-one" mode. This mode contains all features (store, publisher, key maanger, gateway, traffic manaager, ..). You don't have to do anything with it.
For the key manager and gateway, you should specify the profile parameter which should disable some non-essential feature for the specified profile.
For 3.0.0-M6, installing as per
https://docs.wso2.com/display/AM300/Installation+Guide
and then publishing the pet store api described at:
https://docs.wso2.com/display/AM300/Create+and+Publish+an+API
Then, when trying to start the gateway, this message is received:
ballerina: no bal files in the package: org/wso2/carbon/apimgt/gateway
I've seen a an older post at
unable to start ballerina as gateway
where some developer suggested adding an environment variable to have the publisher copy data directly into the file structure of the gateway, but it doesn't describe how to set the environment variable.
Is this still a viable solution? Is there any point in installing and running the five processes locally and expect deployment of apis to work locally? It seems to me the milestone is still a few milestones away from proper testing on localhost.
The docs on this are still a bit sparse...
The documentation has been updated now on how to start the gateway [1].
[1] https://docs.wso2.com/display/AM300/Installation+Guide
I'm following along with the instructions on Cloudera's website to set up a cluster using Cloudera Director. However, when I get to the step where I'm supposed to "Add an Environment," I'm presented with two issues. First, the region I selected (us-east1-b) when configuring my Google Compute instance is not available for selection on the Cloudera Director software. Second, there is no option for me to upload Client ID JSON Keys, as the documentation says we should be able to do. I've attached a screenshot of what I'm looking at. Any clues?
My Cloudera director software is reporting itself as version 2.1.1, and the docs I'm looking at are for version 2.1.x. Am I somehow working with an older version of the software? Or are the Cloudera docs not in line with the current version? Can anyone else running Cloudera 2.1.1 confirm that they're seeing something similar or different?
There is a field to load the Client ID JSON keys in the "Advanced Options" section under General Information. Click the > to expand the Advanced Options.
You should be able to type in the region you want even if it isn't provided as a value in the drop-down.