nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Expand the content server builder debug capabilities

Fabrizio_Menichelli

Hi
I'd like to know if it is possible to expand de space avaible in the content server builder:

And this is the istruction that Write on the content server builder:
Echo (Message)

How can I write in the log?

Thanks

Find more posts tagged with

Comments

eLink User

If you run with debug=2 wantlogs=true and run builder and look at thread0.out that is the console that you are seeing. Builder is a single threaded livelink server that is the theory.Connect0.out is the database calls.

If you like to see the scrolling log realtime use a Windows tailing freebie

Ciao, Appu

On Sep 21, 2016, at 3:06 AM, eLink Entry: Content Server Development Forum <development@elinkkc.opentext.com> wrote:

eLink : Expand the content server builder debug capabilities
Expand the content server builder debug capabilities Posted byMenichelli, FabrizioOn 09/21/2016 04:03 AM

Hi
I'd like to know if it is possible to expand de space avaible in the content server builder:

And this is the istruction that Write on the content server builder:
Echo (Message)

How can I write in the log?

Thanks
[To post a comment, use the normal reply function]
Forum: Content Server Development Forum
Content Server: Knowledge Center

Fabrizio_Menichelli

Thank you very much

Please do you know why messages (wrote with Echo or EchoDebug) are not writed on the debug windows if don't open the Builder in ReadOnly mode?

HFCDev

Hi Fabrizio,

Do you mean that you only see messages in the Debug window when running in read-only mode? Or do you mean you only see messages in the Debug windows when you are running in place of the server (i.e. on builder start-up, you answer 'yes' when asked if you'd like to shut down the service)?

When you start up in read-only mode, you *can* get echo() statements if you execute a script in Builder, but anything you execute via the web page (i.e. request handlers, or browsing a folder) you shouldn't see.

When you start up with a service shutdown, you get both echo statements when you execute a script in builder, *and* you get any echo statements in request handlers that are executed. However, in this use case, if you have a busy server (i.e. lots of requests), the debug statements you're looking for can get buried. The Admin service generates a *ton* of debug traffic that often gets in the way (something that still isn't fixed even in CSIDE - I'd love for there to be a way to turn these off so we can see the debug we're really interested in).

In your original post, you didn't state what version of Content server you're running. Version 10.0 and less uses Builder, and version 10.5 and up uses Eclipse and the CSIDE plug-in.

-Hugh