How can I configure the WSO2 DAS 3.0.1 to get through Proxy server in organization because it cannot download Google library when starting?
Cheers,
Sean
You can pass below properties as JVM options when starting the server to configure the proxy settings.
./wso2server.sh -Dhttp.proxyHost=10.100.1.100 -Dhttp.proxyPort=8088 -Dhttp.nonProxyHosts="localhost|127.0.0.1"
Alternatively you can append those parameters to the existing JVM options in the wso2server.sh.
-Dhttp.proxyHost=10.100.1.100 \
-Dhttp.proxyPort=8088 \
-Dhttp.nonProxyHosts="localhost|127.0.0.1" \
Related
I'm using WSO2 3.2.0 APIM on Windows platform and have a need to change the default HTTP/HTTPS ports from 9443/9763 to 9080/9090. This means that the offset won't work for me. I did some searching here and got some hits. However, some answers are quite old and some answers don't seem to work with 3.2.0.
The most promising answer is to update the connectors in <API-M_HOME>/repository/conf/tomcat/catalina-server.xml. I tried it, but it didn't work. When I started up WSO2, the bootstrap showed messages on the console that it detected the configuration changes and the ports got reverted back to the default ones.
The messages on the console look like this
C:\Programs\wso2am-3.2.0\bin>wso2server.bat --run
JAVA_HOME environment variable is set to C:\Java\openjdk-1.8.0.191-1.b12.redhat
CARBON_HOME environment variable is set to C:\Programs\WSO2AM~1.0\bin\..
[2021-04-26 22:22:18,514] WARN {org.wso2.config.mapper.ConfigParser} - Configurations Changed in :repository\conf\tomcat\catalina-server.xml
[2021-04-26 22:22:18,514] WARN {org.wso2.config.mapper.ConfigParser} - Overriding files in configuration directory C:\Programs\WSO2AM~1.0\bin\..
[2021-04-26 22:22:19,802] INFO {org.wso2.config.mapper.ConfigParser} - Writing Metadata Entries...
andes [org.wso2.andes.wso2.internal.QpidBundleActivator] INFO : Setting BundleContext in PluginManager
callhome [org.wso2.carbon.callhome.internal.CallHomeActivator] DEBUG : Activating CallHome agent
[2021-04-26 22:22:29,530] INFO - CarbonCoreActivator Starting WSO2 Carbon...
...
Any thoughts or ideas?
From API Manager v3.0 onwards, you only need to change the deployment.toml file which resides in the wso2am-3.2.0/repository/conf location. You can't change any xml files that reside in the conf directory. To change the ports, you can add the following config in the deployment.toml
[transport.https.properties]
port = 9080
[transport.http.properties]
port = 9090
The port offset will append to these base values.
I'm implementing one-way (server to client) replication with SymmetricDS and I'm a bit confused about the configuration to apply to the client node. Should I install SymmetricDS and start the service on the destination server/node?
The servers are CentOS + Oracle 12c database
Yes, you should install a SymmetricDs in server mode at the source node and another SymmetricDs in client mode at the destination node. The server node shouldn't be having a registration URL as it is the source of configuration
yes, you have to install it. Both server and client have their own properties files, by which the SymmetricDS will configure the server and the client. After installing, start the service. Go to your installation folder and check
bin/sym_service install
bin/sym_service start
bin/sym_service status
On Windows systems, using VMware PowerCLI, I can connect to a vCenter server using appropriate credentials:
Connect-VIServer myvcenter.example.com
Once connected, I can run Get-VM to see a list of registered VMs. Note that I need not know names of ESX hosts connected to this vCenter server.
When using vmware-cmd, for the similar -l option, both these options need to be provided:
-H <host>
Specifies an ESX/ESXi host or a vCenter Server system.
-h | --vihost <esx_host>
Specifies a target host if the host specified by -H <host> is a vCenter Server system.
Why is that so?
How to list VMs if one does not know the ESX hosts on this vCenter (without using VMware PowerCLI)? I am trying to get this working over SSH on a GNU+Linux system.
Versions:
vSphere SDK for Perl version: 6.5.0
Script 'vmware-cmd' version: 6.5.0
I simply discarded VMware CLI and started using https://github.com/snobear/ezmomi. After having a config.yml file with only connection related options, I was able to list VMs (without knowing ESX hosts).
vmware-cmd is the legacy way that was provided back in the 3.x days to do CLI tasks directly from the ESX service console.
Since you're using vSphere 6.5, I would look at the new CLI called Datacenter CLI (DCLI) instead: http://pubs.vmware.com/vsphere-6-5/index.jsp?topic=%2Fcom.vmware.dcli.cmdref.doc%2Fintro.html
Consecutively to WSO2 API Manager 2.0.0 : white screens after installing https certificate, I've just installed a fresh new WSO2 API Manager (single node) from the 2.0.0 zip distribution using MySQL Database to try to avoid problems related to H2 database.
After the install is complete, it starts with no warning and no error (after a few tries to get all things right in master-datasources.xml).
In publisher, I can log in as admin, create a new API, import swagger json contract, finalize API with no problem.
In store, I can log in as admin, view the API I've just created, create a new application via the right-side drop down menu, subscribe to it.
BUT when I try to open an application in order to generate keys and token, I just get a white empty screen. Nothing can help me in the logs :
[29/Nov/2016:16:17:33 +0100] "GET /store/site/pages/application.jag?name=MyNewApp&tenant=carbon.super HTTP/1.1" 200 3 "https://10.22.106.101:9443/store/site/pages/applications.jag?tenant=carbon.super" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0"
EDIT :
A few minutes after I get the page crash (maybe not related ?) I have this printing repeatedly in wso2carbon.log :
WARN {sun.rmi.transport.tcp.TCPTransport$AcceptLoop} - RMI TCP Accept-11111: accept loop for ServerSocket[addr=0.0.0.0/0.0.0.0,localport=11111] throws {sun.rmi.transport.tcp.TCPTransport$AcceptLoop}
java.lang.OutOfMemoryError: unable to create new native thread
Again, this is a basic installation (unzip) plugged into MySQL database with no customization/configuration.
EDIT 2 : So I think I have found the cause, but not the solution. This problem does not occur when I launch via direct command line, it occurs only when I launch through systemd service :
sudo sytemctl start wso2am.service
/etc/systemd/system/wso2am.service :
[Unit]
Description=WSO2 API Manager
[Service]
User=linc
ExecStart=/bin/bash -c ". /etc/profile.d/setenv.sh; /home/linc/wso2am-2.0.0/bin/wso2server.sh start"
Type=forking
[Install]
WantedBy=multi-user.target
So is WSO2 not compatible with systemd launching ? or am I missing some parameter ?
I have followed this blog post to run APIM as a Linux service. Please have a look. It should work without a problem. (Make sure to add #!bin/sh at the top of myService.sh)
Finally I have WSO2 API manager running as a Systemd service.
This is my 'wso2apim.service' file
[Unit]
Description=WSO2 API Manager
[Service]
Environment= JAVA_HOME=/usr/lib/jvm/java-8-oracle
WorkingDirectory=/opt/wso2/wso2am-2.0.0
User=wso2
ExecStart=/bin/bash /opt/wso2/wso2am-2.0.0/bin/wso2server.sh
ExecStop= /bin/bash -c '/opt/wso2/wso2am-2.0.0/bin/wso2server.sh stop'
ExecReload=/bin/bash -c '/opt/wso2/wso2am-2.0.0/bin/wso2server.sh restart'
[Install]
WantedBy=multi-user.target
It's simple, but tricky
The service type is simple (not fork or either). (Default value)
The ExecStart has not to include the 'start' option. With the
start option, it tries a nohup, that is not working
But, the stop has to include the stop options
Hope it helps
I am trying to run APIM 1.6.0 in a remote server. It gives following exception - http://pastebin.com/HTAsbpsQ. Is it a configuration fault in APIM or problem in the server configuration ?
If you have changed the HostName and MgtHostName properties in carbon.xml try first by giving the IP of the server. It seems the server is bound to an unresolvable host name.