Brava Server inaccessible due to Remote Cache error

Andrei Marculescu · 2022-01-27T20:12:59+00:00

There was an error rendering this rich post.

Hello everyone, I installed Brava for Content Suite alongside the Brava Server Components for my local instance of Content Server, yet I can't seem to access Brava Server as it gives me an Error 404. (I have made a server farm for it, I tried pinging it from Postman and I got a response with 200 meaning its okay, and when I access http://localhost:8080/BravaServer/Version it does show me the version correctly, I think I followed the installation guide correctly).

I get this Error in CS trying to open a document with Brava:

I suspect it might be because of this dependency but I was unable to find something called "Brava! Support for Remote Cache", I only found the Remote Cache Module, will that suffice for this?

Also, I would appreciate an explanation of how Brava handles cache or what this module does exactly. I apologize in advance if this question doesn't quite fit the forums or the category. I'm trying to install Brava in order to fully configure Extended ECM for Government on my test instance.

Thank you!

Find more posts tagged with

Content Suite Platform

Content Server

Comments

Appu Nair

Yesterday I ran into similar issues . Brava licenses mean for the user you are testing that user in CS should be assigned a license Also in the CS admin interface that should point to the real fqdn resolvable Brava Server . The ARR software is basically routing CS requests seamlessly to the Brava Server. Try with a simple pdf adjust it’s mime in the admin index option . I can show you what my server setup does . The Remote Cache module is a red herring not connected to your problem . Brava will only work if the Bravaserver is accessible and the caller is assigned a license and the mime settings . The jobprocessor and other aspects may require further setup as word and other mines require MS word etc on thevserver

Yvonne_Knauthe

To check if the Brava RC module is a red herring remove it from the staging folder. The dependency error should disappear. Just as a sanity check.

Appu Nair

@Yvonne_Knauthe can you also comment on my post if possible https://forums.opentext.com/forums/support/discussion/309504/brava-installation-and-use-of-the-arr-on-a-non-iis-cs-server#latest I just want to run CS on TC with no IIS server and preferably Brava on another server .I managed to create a monolith that seems to work for PDF's

Andrei Marculescu

@Appu Nair

I might have a guess on why everything is happening. I missed the part where it said that the Job Processor for Brava Server Components needs to be installed on a different machine, not on the one that has the Brava Server running. For this I am guessing I run the Server Components installer on a different machine and select only the Job Processor, and on the main machine I run the installer and select Brava Server?

How do you connect the Job Processor to the main machine? Both of them would be using Apache Tomcat.

Appu Nair

The Job Processor is essentially something that perhaps converts Word, Excel and so on so if someone did not have word on his/her machine and if you said you want the Brava Viewer it can do its job .It does require full O365(or old software Word).Brava uses print drivers and dlls on that to do the "Job" .

many image things like TIFF/PDF do not require the Job Processor CSF writer it also can be installed in the same server .I have all components in my monolithic server but this is a demo machine and we don't convert word or anything.

My server I built is like this

CS on TC , Brava on that same TC, OTDS on that same TC,WSDLS of SAP and CMIS on that TC

it will not work in a production environment but my use case is different

Andrei Marculescu

@Appu Nair My objective is also to build a demo environment, not yet a production one, do you think I can get away with not installing the Job Processor at all?

I'm thinking of only installing Brava Server on the same Tomcat with OTCS. I saw that Blazon also has a Job Processor component, I assume that as well has to be installed on another Machine?

Again, thank you very much for the information you're giving me!

Appu Nair

The reason why OT advises of separating them out is for performance gains AFA Blazon I have no idea what all ports it may need so either take the bullet and try to do a monolithic one or separate them out. Brava has no problem doing its stuff in a monolithic server.