Hiring for Cloud-savvy architects, administrators and developers

Please share your resume with me --- hiring for the Army Private Cloud Enterprise team in Huntsville, Alabama. Thank you, Jen Loeffler Sr. Program Manager/AFSO jen.loeff...@qbe.net Office Line: 571-248-7490 ext. 1001 Cell: 571-455-9132 [qbe_logo] 14600 Washington S

Re: Server Group Clarification

Kevin, You should not have Admin01 in the same DB as the rest of the servers if it's not in the server group, for exactly the type of thing you are discussingbeing in the server group allows the server group to manage what element are enabled how/when/etcso yesthe escalations would be r

Server Group Clarification

There are 5 admin servers. For my question I will refer to them as the following: Admin01 - Not in Server Group Admin02 - In Server Group Admin03 - In Server Group Admin04 - In Server Group Admin05 - In Server Group Admin04 is configured as the primary for Escalations in the Operation Ran

Re: Updating Incident Work info via webservice problem

One Midtier for our testing environment. The field is Client_type, When I load the forms up on apptier they all show the new client types Kevin Candelaria Senior Technical Support Specialist Temple University Computer Services • 215.204.3095 | •

Re: Updating Incident Work info via webservice problem

You got just one mid-tier or more? What field type is your field? How do you check for updates? > On 24 Jan 2017, at 18:00, Kevin M Candelaria wrote: > > ** > ** I flushed the cache and even restarted the midtier but the WSDL does not > update the client type when I try to look at the publishi

Re: Updating Incident Work info via webservice problem

** I flushed the cache and even restarted the midtier but the WSDL does not update the client type when I try to look at the publishing location http:///arsys/WSDL/public//HPD_IncidentInterface_WS The form it links to is HPD:IncidentInterface Which has the new client types listed. Kevin C

Re: Updating Incident Work info via webservice problem

If this is just a drop down field, then all you need to do is to flush the mid-tier cache. Then the changes will become visible in your WSDL. The consumer of your web service will then need to consume the new WSDL to see the changes. But again, try with the flush cache first. > On Jan 24, 2017

Re: Updating Incident Work info via webservice problem

** Thomas I added 3 new client types. to Field 100022 These were updated in every form. All I have left to do is the WebService to update it because when I go visit the service it is not listed https://***/arsys/WSDL/public/*/HPD_IncidentInterface_WS Kevin Candelaria Senior

Re: Updating Incident Work info via webservice problem

Kevin, what kind of changes were made to the form? What is the type of operation you want to change? What exactly do you want to change? Thomas > On Jan 24, 2017, at 4:51 PM, Kevin M Candelaria wrote: > > ** > I discovered that I need to make the change to the Webservice. The Primary > form

Re: Updating Incident Work info via webservice problem

I discovered that I need to make the change to the Webservice. The Primary form it calls has the changes already. How can I update the webservice to get the new data from the primary form that I changed? Kevin Candelaria Senior Technical Support Specialist Temple University Computer Services *