I'm trying to get TeamCity v7.1 to notify me about build events via Jabber. I have TeamCity on a server at work and I've setup an OpenFire XMPP server on my desktop machine. To complete the picture I have a Pidgin client running on my desktop listening for messages.
I've configured TeamCity to connect to the OpenFire server via an OpenFire user I called "teamcity" and when I "test connection" I am told that the connection is ok. When I'm testing the connection I'm sending to an OpenFire user I called "pidgin".
The problem is that Jabber messages sent from TeamCity never reach the "pidgin" user. TeamCity gives no indication of a problem and I see no sign of a problem in the TC notification log. Much the same way no notification from build events ever gets through to the "pidgin" user (fairly confident I've setup the Jabber notification rules correctly).
Any idea why this is or what I should try next?
I'm pretty sure I've resolved my problem by specifying the "full" XMPP username in TeamCity. In my example: pidgin#urisopenfire (where uriopenfire is the name of my OpenFire server instance).
When I used this full form when testing the connection and in the Jabber Notifier settings for my TC project, I did get notification from TeamCity coming into my Pidgin client.
Oddly enough, this full form is not needed when setting up the "teamcity" user in TeamCity's global Jabber Notification settings.
Related
Developing WPF application and using Redmine issue tracker to send reports to.
If Redmine issue tracker is hosted on server where there is not installed valid SSL certificate, NBug crashes because it can not send reports to server...
What if user does not have internet?
I do not want for NBug to crash application because it can not do what it wants to do.
Is there a setting for NBug that if can not send error reports, just allow application gracefully to continue running?
Enable release mode as per documentation:
NBug.Settings.ReleaseMode = true;
This catches all internal exceptions and logs them instead of throwing them.
I've followed the instructions here: http://guac-dev.org/doc/gug/installing-guacamole.html
This says
Guacamole is separated into two pieces: guacamole-server, which provides the guacd proxy and related libraries, and guacamole-client, which provides the client to be served by your servlet container, usually Tomcat.
guacamole-client is available in binary form, but guacamole-server must be built from source. Don't be discouraged: building the components of Guacamole from source is not as difficult as it sounds, and the build process is automated. You just need to be sure you have the necessary tools installed ahead of time. With the necessary dependencies in place, building Guacamole only takes a few minutes.
And then proceed to describe how to install guacamole-server and use it. I can now go to http://localhost:8080/guacamole/ and access the server and see which clients have connected.
How do I connect a client though? I see no documentation of where the remote desktop needs to browse to in order to run the guacamole-client?
Or have I totally misunderstood this?
The key phrase in the quoted documentation is:
... guacamole-client, which provides the client to be served by your servlet container, usually Tomcat.
"guacamole-client" is the web application and the client. When a user visits the URL for your Guacamole server, logs in, and clicks on a connection, they are connected to the corresponding remote desktop via Guacamole's JavaScript client which is served to their browser like any other web application.
I can now go to http://localhost:8080/guacamole/ and access the server and see which clients have connected.
The list you see when you first log in to your Guacamole server is not the list of clients that have connected; it is the list of connections to remote desktops which are available. If you click on one of those connections, you will be connected using Guacamole's own built-in JavaScript client.
How do I connect a client though? I see no documentation of where the remote desktop needs to browse to in order to run the guacamole-client?
The remote desktop does not need to do anything - Guacamole will simply connect to it. You can see a video of the overall user experience on the Guacamole website which may hopefully clear things up for you:
https://vimeo.com/116207678
Overall:
You deploy guacamole-client (the web application) and install guacamole-server (the remote desktop proxy that the web application uses in the backend). The combination of these two pieces of software makes up a typical Guacamole server.
You and your users can log in through the web application and connect to remote desktops using a web browser.
You do not need to explicitly run a client.
It looks like this
Internet -> Guacamole server (on the local network) -> Desktop pc
I installed Guacamole in a vmware enviroment on Ubuntu.
There is a file in /etc/guacamole what is called user-mapping.xml
In that file you add or edit the connections available to the user you want.
A connection for that user must be set between the <connection> tags
I am using IBM MobileFirst 6.3, with Apple, Android, Blackberry and Windows Environments.
I have enabled Push Notifications for Apple, Android and Windows environment. I mistakenly uploaded application with sandbox certificate on my production server. On noticing the mistake, I removed the version with Sandbox certificate and uploaded the production certificate version properly and restarted the Websphere Liberty server.
After the restart, push notification is NOT WORKING for any platform.
Earlier I got APNS SSL connection error in my logs, but now I can not see any Push related error in my logs, I enabled trace on com.ibm.pushworks.server.notification.apns.*=all, and still got nothing back.
The only error I get is of could not piggyback ... , which I believe even IBM is suggesting to suppress. I have attached the finest level trace here
I have checked through Wireshark, and server receives request on HTTP GET method and replies with status 200. But what happens after that is a mystery.
P.S. The push notification worked once while the SandBox certificate version was enabled, but didn't work after the restart at all.
#eshaa when you use to change in certificate related settings in client side code you need to take new build i means new .wlapp files to be upload to the server then it will be effect whatever changes you done.
I am very new to splunk and trying to set up domain account, but with the custom options the installation rollbacks. I want to receive data from remote system by a universal forwarder. I have provided the same port number as the receiving port which is forward data configurations in remote system. What am I missing here? Can I do so with local system installation?
same question is asked here ...
http://answers.splunk.com/answers/232340/why-am-i-unable-to-set-up-the-domain-account-for-s.html
but there is no answer..
Please help..
The service account must be entered as "domain.name\username" rather than just "username".
I experienced the same problem, having everything configured correctly for running the Universal Forwarder as a service account. However, I failed to enter the service account as "domain.name\username". Just specifying "username" does not work, either when running the installer interactively or silently.
I have created a server in liberty and installed IBM Worklight in it.
Everything was working fine till I protect the console.
After protecting the IBM Worklight console the authentication is asked
twice.
First Login Screen with URL localhost:9080
After Login Successful.Again the login is being asked with the hostmachines URL 192.168.10.16:9080
My questions are
Why login appears twice?
Why my hostmachine ip is being revealed?
You are accessing the console with address localhost, whereas in your code you are either using publicWorklightHosname=192.168.10.16 or while building you are using build for remote machine and then putting in IP of the server.
Here is what you need to do:
Make sure a DNS entry of the hostname is present in the server and client machine
Change the publicWorklightHostname property in worklight.properties file to a proper address eg
mymachine.mydomain.com
while building for Remote Server, use the same address as above i.e. mymachine.mydomain.com
redeploy the new war file
Worked perfectly for me.
P.S> I believe you are using local machine, in this case also you can use the machine name in worklight.properties file and make sure that the address you are using is same as the one you used to build. Nonetheless, it doesn;t matter in production or application deployment.