All
Accepted answers
Fabian Haupt · Sep 23, 2018 go to post

Did you put in the private apache's port? Is the port reachable (windows firewall on your server?) Note that you need to make sure to have only password authentication on the /atelier/api webapp enabled.

Fabian Haupt · Aug 22, 2018 go to post

I didn't even know the first version was valid syntax. But based on your testing, I only would have produced slower code anyways :)

Fabian Haupt · Aug 22, 2018 go to post

This kind of error is known to come up when using very outdated browsers with current versions of ZEN. But that's just a guess, really you'll have to use the brower's debug tools to figure out which object it doesn't get and why (the one it tries to set the title on)

Fabian Haupt · Jul 12, 2018 go to post

and subsequently you can export compiled classes and only import deployed code on another system. So you never get source code on a customer's system.

Fabian Haupt · Jun 1, 2018 go to post

the pwd should be set at runtime of the container (we have the parameters for that). No matter if prod or non-prod. If you have any pwd fixed in the image, it introduces an unnecessary risk.

Fabian Haupt · Jun 1, 2018 go to post

After loading your classes you should re-scramble the password, so you don't accidentally distribute an image with a defined/known instance password.

Fabian Haupt · May 31, 2018 go to post

Hi,

why are you doing the separate step of checking out your sources outside of eclipse/Atelier? You can do that directly in there, which would simplify your workflow to something like this:

  1. Checkout repository in EGit into an Atelier project
  2. Create ticket123 branch
  3. Make your modifications
  4. Submit your modifications into the branch
  5. Merge branch into master as necessary

Best, Fab

Fabian Haupt · May 30, 2018 go to post

adding an answer so this doesn't show up in 'unanswered questions' anymore

Fabian Haupt · Apr 27, 2018 go to post

"We want our code to be as accessible and readable as possible to as many people as possible. " Do we? ;) "We always prefer whitespace formatting and curly brackets to arcane one line syntax." -- I don't ;) Using arcane one liners shows that you are a superiour wizard. One should always use the short forms of commands to make code more terse and save space. If people want to read the code, they can use 'expand code' in studio (which expands the shortform commands to the full version). Note, there might be some sarcasm in here. People who know me, might also know that I'm only maybe 80% joking;)

Fabian Haupt · Mar 28, 2018 go to post

There really isn't a general answer as to what the 'best way' (tm) is. There are way too many dependencies on that.

It really depends on your workflow and requirements of your backend. Zabbix is very well capable of ingesting SNMP data, just as well as ODBC (https://www.zabbix.com/documentation/3.4/manual/config/items/itemtypes/snmp).

Usually the answer to 'the best way' comes down to: what are you most familiar with? To use ODBC you'd need to implement some glue code on the Caché side, same if you were to go with a REST interface. Since you mentioned you have custom indicators, you'll have to write some code in any case. So, again, it comes down to your preferences and preexisting experiences.

Evgeny already pointed out one of the local SNMP articles to get you started on this.

Cheers, Fab

Fabian Haupt · Mar 26, 2018 go to post

There are any number of ways to connect with the DB. ODBC, REST api, jdbc, nodejs,... It really comes down to your requirements.

Fabian Haupt · Mar 23, 2018 go to post

I'm not sure there is such a thing as 'typical' in terms of Eclipse installation. Whether you get egit or not depends very much on the edition you are downloading/installing.

Fabian Haupt · Feb 5, 2018 go to post

In short: a container is a sandbox that runs a single process. This in turn can spawn off other processes. For us, that is isc-main, which will take care of running on the necessary processes (write daemons etc). But as soon as that first process goes away, the container is being closed In a classical VM a complete machine is being simulated. Which in turn stars up a complete OS and not just a single process context. There are plenty of articles that explain the difference in more detail (for example: https://blog.netapp.com/blogs/containers-vs-vms/) (It's important to notice that on some OSes[windows + macos] docker is 'cheating' by creating a hidden linux VM to run the docker images)

Fabian Haupt · Feb 1, 2018 go to post

The first thing I'd check are the permissions on these files. If you created them as root, they might not be readable for other users?

Fabian Haupt · Feb 1, 2018 go to post

As Mike already said, pretty much it comes down to the specifics of your site and code. There aren't any big changes between 2014.1.2 and the current version, so I wouldn't expect much coding work. The majority of work is probably going to be your testing of the procedure and the resulting upgraded test environment. We are more than happy to discuss your upgrade plan and help with any issues you might encounter, feel free to contact the WRC and we'll go from there! Best, Fab

Fabian Haupt · Dec 26, 2017 go to post

That's a server side error. Nothing you can do about it, we'll have to wait till they resolve it on the server side. -Fab

Fabian Haupt · Dec 22, 2017 go to post

Just as a quick follow up, this seems to happen if you had installed the standalone Atelier client and subsequently install a full eclipse into the same directory. This will lead to a conflict between a couple of jar, leading to the errors as shown above. Doing a clean fresh install of eclipse solves it.