Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automate Hastus export #34

Open
dfaulken opened this issue Jun 13, 2017 · 8 comments
Open

Automate Hastus export #34

dfaulken opened this issue Jun 13, 2017 · 8 comments

Comments

@dfaulken
Copy link
Contributor

No description provided.

@dfaulken
Copy link
Contributor Author

Need more info here. Referencing other objects isn't documented, and I can't figure out how to do it.

@dfaulken
Copy link
Contributor Author

dfaulken commented Jul 7, 2017

Hastus export works, but not automatedly yet. Need to talk to GIRO about that.

@dfaulken dfaulken changed the title Hastus export Automate Hastus export Jan 18, 2018
@dfaulken
Copy link
Contributor Author

Worth noting that with batch export functionality, this may not be required.

@dfaulken
Copy link
Contributor Author

We do this at MBTA. Definitely feasible.

@dfaulken
Copy link
Contributor Author

dfaulken commented Jan 12, 2019

The low-tech way we've done this at MBTA is:

  1. Agree on a location that can be accessed (via SFTP or directly via UNC path) by both the incidents server and HASTUS.
  2. When an incident is marked for export, place the XML file in the location.
  3. Set up a Windows Task Scheduler job (or similar) that periodically checks for files in that location, loading them and archiving the file in a separate location once loaded.

If still desired, I'd be happy to work with Jim on setting this up. I have developed, and now administrate, several such jobs for MBTA.

@sherson
Copy link
Member

sherson commented Jan 14, 2019

Will check with PVTA

@dfaulken
Copy link
Contributor Author

I don't believe I've heard any more on this topic.

@sherson
Copy link
Member

sherson commented Sep 26, 2019

Me neither. We didn't bring it up because both they and we have been busy with other things. Let's come up with a list of things to remind PVTA about.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants