DCO 8.0.4 rackPDU ans Web Branding issues

[DCIM_Support]

I have just upgraded my DCO server from 8.0.3 to 8.0.4 (8.0.4-68761-61f5f2) but I meet some issues

1) I am not able to edit rackPDUs in the web client (tested with IE / Firefox / Chrome) but it works through a smartphone (iOS)

2) the path /opt/jboss-as/standalone/deployments/webclient.war/web/client/css/branding for customizing the web branding (as described in https://dcimsupport.apc.com/display/public/UADCO8x/Customizing+web+branding) does no longer exist!

Are they known issues or issues on my installation?

Regards

Yannick

(CID:111938548)

[DCIM_Support · Accepted solution]

Hi Yannick,

1) It is currently not supported to edit rack pdus in the web client - the supported feature (for web client) is expected to be included in one of the near feature releases (it is an ongoing project at the moment).

2) you are right, the web branding folder is updated in 8.0.4:

/opt/jboss-as/standalone/deployments/webclient.war/web/resources/branding

for older versions, eg. from 8.0.0 to 8.0.3, the location of the web branding folder is:

/opt/jboss-as/standalone/deployments/webclient.war/web/client/css/branding

We will add these info to our documentation(s) soon,

Thank you,

Kind regards

(CID:111939068)

[DCIM_Support]

Hi Jef,

Thanks for your answer. I hope at least getting details of rack pdus will be supported soon. (for us editing objects in the web client is less priority)

About the web branding, the Own by user field needs to be updated in your documentation

With 8.0.4 it seems the file owner is now root instead of dcojboss...

# ls -l /opt/jboss-as/standalone/deployments/webclient.war/web/resources/branding/
total 244
-rw-rw-r--. 1 root root 230630 Feb 2 15:47 bg_login.jpg
-rw-rw-r--. 1 root root 821 Feb 22 13:00 branding.css
-rw-rw-r--. 1 root root 146 Feb 2 15:47 branding.json
-rw-r--r--. 1 root root 3928 Feb 22 13:00 company_logo.png
-rw-rw-r--. 1 root root 1928 Feb 2 15:47 logo.png

Best Regards,

Yannick

(CID:111939137)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.