Avaya Support Forums

Avaya Support Forums (http://support.avaya.com/forums/index.php)
-   Avaya Breeze™ Collaboratory (http://support.avaya.com/forums/forumdisplay.php?f=77)
-   -   SMS Svc Web Services in our Collaboratory (http://support.avaya.com/forums/showthread.php?t=12381)

jwindb 02-13-2017 11:20 AM

SMS Svc Web Services in our Collaboratory
 
We have a lab, Lab174.

I have downloaded the "SMS Web Services SDK"
and am following the instructions to connect using the sample application.
"Avaya Aura Application Enablement Services Web Services Programmer's Guide".

The sample app class is called "SMSXMLTest.java"

In order to get java to talk to the host, I downloaded the "aes-labUseOnly" certificate, and them used that as the hostname (the certificate required it), bu putting the ip address of the host in my /etc/hosts file.
I have verified that I can programmatically download the wsdl, so that's clear.

I'm unclear what to use for the values is smsxml.properties
sms.root
cm.login
sm.password

Especially as within the test, the string cm.login comes in the form:
loginid@cmaddress[:port]


My web service url ends up as :
https://aes-labUseOnly/smsxml/System...entService.php
aes-labUseOnly is in my hosts file as 10.0.0.17
I've been using our cust#####@dev-174.collaboratory.avaya.com

Best I have ever gotten is OSSI connection errors.

I need to know what I ought be using for the properties, how to verify that our lab service is actually installed correctly (the documentation mentions looking in the logs, but doesn't bother to say how to get to them), also mentioned going to the "OAM" pages, but I don't know what that means.

lucas3 02-14-2017 07:29 AM

Hi jwindb,

I'll follow up with design on this issue and get back with you shortly.

jwindb 02-14-2017 01:18 PM

Excellent.

I've discovered that I can ssh into the machine that is actually running the smsxml web service. I can even read the php code.
I cannot, however, gain access to the log directories, as my documentation says I should. They are root only.

I'm beginning to believe that box referred to as our CM, is also the box I would use for OSSI.

ssh cmhost -p 5022

Does that seem correct?

None of my lab credentials work on that host though.

lucas3 02-15-2017 08:09 AM

The Breeze development team is going to add the universal account (cust#####) to the CM server and change the permissions on the directories in the AES server so you can access the log files. Will send you an email once this is updated.

lucas3 02-15-2017 02:25 PM

The CM account was provided to you in a separate email. You should now have access to the AES directories /var/log/avaya/aes/apache & /var/log/httpd using the universal cust account.

jtb1 02-15-2017 04:33 PM

mentioned going to the "OAM" pages, but I don't know what that means.

that would be a reference to the web interface on AE Services that you do operations administration and maintenance.


All times are GMT -7. The time now is 11:00 AM.