If this email doesn't look like it's displaying properly, view it here.
Dear Mr Sollis,
OPEN GI USER GROUP AGM & MEMBERS' DAY
The Annual General Meeting of the Open GI User Group will be held at the Hilton Reading Hotel, Drake Way, Reading, RG2 0GQ, on Wednesday, 10th October, 2018.
The position of Chairman, Vice-Chairman, Secretary and Treasurer are up for re-election at the AGM, and nominations are now being received.
Marc Pons-Burt (Chairman), Mark Searcy (Secretary) and Mark Sollis (Treasurer) are all willing to stand again and are available for re-election.
Nominations for the posts of Chairman, Vice-Chairman, Secretary and Treasurer would therefore, be most welcome from all members of the User Group. User Group members should not be shy in putting other names forward.
We would ask that you forward any nominations to the Open GI User Group office within the next 14 days by either post or email. Nominations must be received no later than Monday, 13th August, 2018.
If any member wishes to raise an item under Any Other Business item similarly this should be communicated in writing to the Chairman at least 7 days prior to the AGM.
Click here for Nomination Form.
Marc Pons-Burt - National Chairman
The views and opinions expressed in this email may not represent the views
and opinions of the Open GI User Group and are made without prejudice and
subject to contract. Although this message and any attachments are believed
to be free of any virus or other defect that might affect any computer
system into which it is received and opened, it is the responsibility of the
recipient to ensure that it is virus free and no responsibility is accepted
by the Open GI User Group for any loss or damage in any way arising from its
The information contained in this message is correct at the time of going to
press. Any action taken as a result of the information should be checked
with the sender before taking action.
Hi Emily - that's a great use for XStream and there are lots of posts here in the Forum covering a range of areas on XStream use
Given where you are in the XStream process right now I'd suggest a couple of important steps ...
1 - Ask OGI support to confirm that the XStream service is still configured correctly and proven as working
You can waste hours, days and weeks trying to connect to the service and still have issues because it's no longer set up correctly or your infrastructure has changed. Get them to test it and to prove it and make sure you have the access details as well (IP and Port numbers etc)
2 - Use a tool like SOAPUI
This will allow you to test the processes outside of the web page and confirm the XStream service is working as expected
Step 1 is a must
Happy to assist further if I can!
I am building a new website for internal use, the main feature is to be a lead management system. I would like to use xStream to import client details from Open GI into the website, and to create prospects in Open GI directly from the website.
The problem is that we purchased xStream many years ago to use with a website built for us by a third party, and nobody in our company has had any training on it.
Generally, I think the online guides are excellent and I have always found them to contain enough information required to use any of the Open GI products. However, I've found them rather lacking in the case of xStream. There are example scripts to cover different scenarios for which you might use xStream, which I imagine will be very useful once I've established the link between OGI and our website, but I can''t find any information on how the XML data is actually transmitted between Open GI and a web application.
If any xStream users can give me some pointers I'd really appreciate it.
Thanks a lot, Emily
Great points made - and welcome to the Forum!
I’ve done a few loops round many a boardroom table on the cloud vs local debate. As you rightly point out - you can have as much redundancy as you want in the Datacentre - but what about accessing it in the first place?
As you mention, if you only have 1 firewall / switch / leased line / then there’s a point of failure inbuilt. Just because it’s “cloud” doesn’t mean to say it’s “Safe”
And let’s just overlook the whole local and remote SLAs to go with any architecture.