tracker issue : CF-4203345

select a category, or use search below
(searches all categories and all time range)

Unable to parse API Manager config file. wsconfig on Linux

| View in Tracker

Status/Resolution/Reason: To Track//PRNeedInfo

Reporter/Name(from Bugbase): Peter Freitag / ()

Created: 09/18/2018

Components: API Manager, Connector

Versions: 2018

Failure Type: Incorrectly functioning

Found In Build/Fixed In Build: 2018.0.0.310739 /

Priority/Frequency: Normal / Most users will encounter

Locale/System: ALL / Linux

Vote Count: 0

Problem Description: Running wsconfig on a linux server, getting an error "Unable to parse API Manager config file."

Steps to Reproduce: Installed api manager 2018 and started apimanager on a CentOS Linux release 7.5.1804 server. Tried to run wsconfig using the following: 

wsconfig/wsconfig -ws Apache -dir /etc/httpd/conf -bin /usr/sbin/httpd -vhost All 

The contents of conf/cluster.xml is:

<?xml version="1.0" encoding="UTF-8"?><Cluster>

I have not modified any of the config xml files after installing. 

Actual Result: "Unable to parse API Manager config file."

Expected Result: configures the connector.

Any Workarounds: no



Pete, I'm on CentOS Linux release 7.5.1804 (Core), and i'm seeing the connector configures correctly for me. Using Apache/2.4.6 - the one distributed by YUM.    Here's how the cluster.xml must look, post installation and post connector configuration.  <?xml version="1.0" encoding="UTF-8"?> <Cluster> <nodes> </nodes> <context> </context> </Cluster> Was any other configuration in the APIM administrator changed, prior to connector configuration? 
Comment by Immanuel N.
29834 | October 22, 2018 06:52:43 AM GMT
I don't think any configuration was changed, I did login to the apimanager portal to make sure it was working, but that's about it. Why do we have different cluster.xml files?
Comment by Peter F.
29841 | October 24, 2018 04:33:31 PM GMT