Version History:
...
NOTE: As per Admin Distribution specifications, EDXL-Distribution Element does not define a response. Hence a successful response will be a standard HTTP 200 for all below test cases . Meaning, the actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request, the response will contain an entity describing or containing the result of the action.
| Info |
|---|
| title | Important note regarding UDDIConnectionInfo.xml and internalConnectionInfo.xml |
|---|
|
As of CONNECT 5.1, both files have been replaced with the more versatile exchangeInfo.xml and internalExchangeInfo.xml files. For users of CONNECT 5.0 and earlier versions, substitute references to these new files with the original uddiConnectionInfo.xml and internalConnectionInfo.xml files |
...
Preparation & Execution:
- Make sure to copy CONNECT common properties from \\CONNECT\Product\Production\Common\Properties\src\main\resources to application server properties folder. (If using WildFly 8.2.1 , copy into \\wildfly-8.2.1.Final\modules\system\layers\base\org\connectopensource\configuration\main).
- In AuditRepositoryProxyConfig.xml make sure to have securedImplementation or javaImplementation.
- Make sure to enable Standard mode for AD service in gateway.properties. Note: By default all services will be in Standard mode in gateway.properties as of CONNECT-4.6 release.
- Restart application server.
- Deploy CONNECT ear (mvn clean install -P AD,PD,DQ,DR,DS)
- In SoapUI, make sure to have GatewayPropDir value set either by using global SOAPUI properties or by setting custom SOAPUI property at the project level.
- In SoapUI, load Admin-Distribution-Standard project and execute.
- Make sure all test cases are passed and green.Test in Standard mode.