We're using elog as our CMDB, but now management wants us to employ "web services" and I fear going to another tool (elog is fitting the admins like a glove, so we'd rather keep it)

Is it possible to configure elog to be able to run as a web-service ?  (basically getting xml-output according to a specific (SOAP) schema instead of html output)

http://en.wikipedia.org/wiki/Web_services

A 'Web service' (also Web Service) is defined by the W3C as "a software system designed to support interoperable Machine to Machine interaction over a network." Web services are frequently just Web APIs that can be accessed over a network, such as the Internet, and executed on a remote system hosting the requested services.

The W3C Web service definition encompasses many different systems, but in common usage the term refers to clients and servers that communicate using XML messages that follow the SOAP standard. Common in both the field and the terminology is the assumption that there is also a machine readable description of the operations supported by the server written in the Web Services Description Language (WSDL). The latter is not a requirement of a SOAP endpoint, but it is a prerequisite for automated client-side code generation in many Java and .NET SOAP frameworks (frameworks such as Spring and Apache CXF being notable exceptions). Some industry organizations, such as the WS-I, mandate both SOAP and WSDL in their definition of a Web service.

At the moment no support for a Web Service is planned.

I would appreciate if elog could provide a simple support for mathematical expressions.

A solution similar to wikimedia should be easy to implement and would help a lot.
http://www.mediawiki.org/wiki/Manual:Running_MediaWiki_on_Windows#Alternative_Solution

The idea is to parse the elog entry for a tag (e.g.  <math></math>), extract the code, wrap it into a latex file, and pass this to latex, GhostScript, and ImageMagic. (The latter are already used by Elog, therefore the changes should not be too big.) The resulting image file would then be referenced by the  elog html code.

Of course, the FCKeditor would not support LaTeX. However, the majority of elog-useres should be scientists and rather familiar with LaTeX. Therefore it should be fine if the original LaTeX code is saved (e.g. in the ALT-tag of the image) and the replacement "code to image" is undone for editing.

Kind regards,
Jochen

We had already some time ago a request to integrate mimetex (elog:1827). I will see what I can do there.

Hello everyone, I am new to the forum.

I currently have an attribute which is a list. From this drop down menu, I can only access around 100 options (ELog restriction I think). How can I extend my drop down list to say 200?

Example:

Attributes = RB

Options RB = a, b, c, ...,etc.

Thanks,

Paul

The number of 100 options is defined in elogd.c with

#define MAX_N_LIST  100

You could try to increase this to 200, but I have no idea if you will hit some other memory limit then. So what about conditional attributes? You subdivide your list into several smaller lists, like

Attributes = Category, RB

Options Category = Cat1{1}, Cat2{2}

{1}Options RB = a,b,c,d...

{2}Options RB = e,f,g,h,...

this is then also easier to handle, as compared to select a value from a very long list.

Attributes = Category, RB

Options Category = Cat1{1}, Cat2{2}

{1}Options RB = a,b,c,d...

{2}Options RB = e,f,g,h,...

this is then also easier to handle, as compared to select a value from a very long list.

Stefan,

Thanks for that advice. I have made that change to the elogd.c file, but the only problem I don't know how to compile Elog to make that change take effect. I did the stop and restart of the elog  service in windows, but that made no difference. How do I compile ELog? Sorry for my ignorance, but I am fairly new to Elog.

Attributes = Category, RB

Options Category = Cat1{1}, Cat2{2}

{1}Options RB = a,b,c,d...

{2}Options RB = e,f,g,h,...

this is then also easier to handle, as compared to select a value from a very long list.

You need a C compiler to compile Elog under Windows. If you don't have one, I would suggest to follow the advice to use conditional attributes. This does not require a recompilation of Elog.