Run DCE-client and AdvancedView on modern Linux desktops, i.e. x86_64?

[DCIM_Support]

Hi all!

It is no secret, that the majority modern Linux desktops have only x86_64 architecture. For example, CentOS/RHEL-7.x or openSUSE-42.x can be a fine example. And of course, on these Linux desktops DCE-client and APC Advanced View won't be started, as these applications are intended for x86 architecture. But nevertheless it is possible and here how.

So, let we already installed a DCE-client rpm-package necessary for us on CentOS-7.3 and we try to start it. But DCE-client isn't started, and in ~/.isxc/7.4.2/.metadata/.log we see here such mistakes and errors:

bash~/.isxc/7.4.2/.metadata/.log!SESSION 2017-03-13 15:01:14.831 ----------------------------------------------- eclipse.buildId=unknown java.version=1.8.0_102 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Command-line arguments: -os linux -ws gtk -arch x86 !ENTRY org.eclipse.osgi 4 0 2017-03-13 15:01:17.459 !MESSAGE Application error !STACK 1 java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: /home/admin/.eclipse/1861345531/configuration/org.eclipse.osgi/bundles/482/1/.cp/libswt-pi-gtk-3659.so: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory no swt-pi-gtk in java.library.path /tmp/swtlib-32/libswt-pi-gtk-3659.so: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory Can't load library: /tmp/swtlib-32/libswt-pi-gtk.so

Obviously we see, that there is no 32-bit library libgtk-x11-2.0.so.0, that is normal for our 64-bit OS. Therefore, we look for a rpm-package necessary for us of this library:

bashyum provides libgtk-x11-2.0.so.0# yum provides libgtk-x11-2.0.so.0 Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile gtk2-2.24.28-8.el7.i686 : The GIMP ToolKit (GTK+), a library for creating GUIs for X Repo : c7-media Matched from: Provides : libgtk-x11-2.0.so.0

This rpm-package is the 32-bit version of gtk2-2.24.28-8.el7.i686, which further, with all set of dependent 32-bit rpm-packages, we install in our OS:

bashyum install gtk2-2.24.28-8.el7.i686# yum install gtk2-2.24.28-8.el7.i686 Transaction Summary ===================================================================================================================================================== Install 1 Package (+53 Dependent packages) Installed: gtk2.i686 0:2.24.28-8.el7 Dependency Installed: atk.i686 0:2.14.0-1.el7 audit-libs.i686 0:2.6.5-3.el7_3.1 avahi-libs.i686 0:0.6.31-17.el7 cairo.i686 0:1.14.2-1.el7 cups-libs.i686 1:1.6.3-26.el7 dbus-libs.i686 1:1.6.12-17.el7 expat.i686 0:2.1.0-10.el7_3 fontconfig.i686 0:2.10.95-10.el7 freetype.i686 0:2.4.11-12.el7 gdk-pixbuf2.i686 0:2.31.6-3.el7 glib2.i686 0:2.46.2-4.el7 graphite2.i686 0:1.3.6-1.el7_2 harfbuzz.i686 0:0.9.36-1.el7 jasper-libs.i686 0:1.900.1-29.el7 jbigkit-libs.i686 0:2.0-11.el7 keyutils-libs.i686 0:1.5.8-3.el7 krb5-libs.i686 0:1.14.1-27.el7_3 libX11.i686 0:1.6.3-3.el7 libXau.i686 0:1.0.8-2.1.el7 libXcomposite.i686 0:0.4.4-4.1.el7 libXcursor.i686 0:1.1.14-2.1.el7 libXdamage.i686 0:1.1.4-4.1.el7 libXext.i686 0:1.3.3-3.el7 libXfixes.i686 0:5.0.1-2.1.el7 libXft.i686 0:2.3.2-2.el7 libXi.i686 0:1.7.4-2.el7 libXinerama.i686 0:1.1.3-2.1.el7 libXrandr.i686 0:1.4.2-2.el7 libXrender.i686 0:0.9.8-2.1.el7 libXxf86vm.i686 0:1.1.3-2.1.el7 libcap-ng.i686 0:0.7.5-4.el7 libcom_err.i686 0:1.42.9-9.el7 libdrm.i686 0:2.4.67-3.el7 libffi.i686 0:3.0.13-18.el7 libjpeg-turbo.i686 0:1.2.90-5.el7 libpciaccess.i686 0:0.13.4-3.el7_3 libpng.i686 2:1.5.13-7.el7_2 libselinux.i686 0:2.5-6.el7 libsepol.i686 0:2.5-6.el7 libstdc++.i686 0:4.8.5-11.el7 libthai.i686 0:0.1.14-9.el7 libtiff.i686 0:4.0.3-27.el7_3 libverto.i686 0:0.2.5-4.el7 libxcb.i686 0:1.11-4.el7 libxshmfence.i686 0:1.2-1.el7 mesa-libEGL.i686 0:11.2.2-2.20160614.el7 mesa-libGL.i686 0:11.2.2-2.20160614.el7 mesa-libgbm.i686 0:11.2.2-2.20160614.el7 mesa-libglapi.i686 0:11.2.2-2.20160614.el7 openssl-libs.i686 1:1.0.1e-60.el7_3.1 pango.i686 0:1.36.8-2.el7 pcre.i686 0:8.32-15.el7_2.1 pixman.i686 0:0.34.0-1.el7 Complete!

And again, we try to start DCE-client and again it is unsuccessful, about what it is visible from the file ~/.isxc/7.4.2/.metadata/.log:

bash~/.isxc/7.4.2/.metadata/.log!SESSION 2017-03-13 15:08:56.291 ----------------------------------------------- eclipse.buildId=unknown java.version=1.8.0_102 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86, WS=gtk, NL=en_US Command-line arguments: -os linux -ws gtk -arch x86 !ENTRY org.eclipse.osgi 4 0 2017-03-13 15:08:56.926 !MESSAGE Application error !STACK 1 java.lang.UnsatisfiedLinkError: Could not load SWT library. Reasons: /home/admin/.eclipse/1861345531/configuration/org.eclipse.osgi/bundles/482/1/.cp/libswt-pi-gtk-3659.so: libXtst.so.6: cannot open shared object file: No such file or directory no swt-pi-gtk in java.library.path /tmp/swtlib-32/libswt-pi-gtk-3659.so: libXtst.so.6: cannot open shared object file: No such file or directory Can't load library: /tmp/swtlib-32/libswt-pi-gtk.so

But this time isn't enough already 32-bit library libXtst.so.6. Therefore, we look for a rpm-package necessary for us of this library:

bashyum provides libXtst.so.6# yum provides libXtst.so.6 Loaded plugins: fastestmirror, langpacks Loading mirror speeds from cached hostfile libXtst-1.2.2-2.1.el7.i686 : X.Org X11 libXtst runtime library Repo : c7-media Matched from: Provides : libXtst.so.6

This rpm-package is the 32-bit version of libXtst-1.2.2-2.1.el7.i686, which further we install in our OS:

bashyum install libXtst-1.2.2-2.1.el7.i686# yum install libXtst-1.2.2-2.1.el7.i686 Installed: libXtst.i686 0:1.2.2-2.1.el7 Complete!

Now we try to start our DCE-client again and it is successful! We check: everything normally functions, but here only some DCE-client settings, for example, an interface language, don't remain and aren't applied. The reason of it is restriction of write access for the /usr/lib/StruxureWare_Data_Center_Expert_7.4.2/configuration/config.ini file. Let's make it available on write for all users, for example:

bashchmod 666# chmod 666 /usr/lib/StruxureWare_Data_Center_Expert_7.4.2/configuration/config.ini

Now everything is normal and correct for DCE-client 😀.

Now concerning APC Advanced View: if listed above not to make everything, then in attempt of installation of APC Advanced View on x86_64 Linux we will receive a mysterious and unclear error:

bashAdvanced View install error?Graphical installers are not supported by the VM. The console mode will be used instead...

And here, if everything is executed correctly, then installation is correctly carried out, for example, here so:

bash$ sudo ./install.bin$ sudo ./install.bin

Important: this installer by default demands the graphic mode therefore, the user from whom installation is started has to have the right for opening X-window.

Further we specify where it is necessary to copy files, so that they were available for all users, for example in folder /usr/lib/APC_Advanced_View_4.5.4.

And the last: that it was convenient to start DCE-client and APC Advanced View from the graphic menu of a Linux desktop, we will create in the folder /usr/share/applications/ here such two files:

bash/usr/share/applications/data-center-expert.desktop[Desktop Entry] Encoding=UTF-8 Name=StruxureWare Data Center Expert 7.4.2 Comment=StruxureWare Data Center Expert 7.4.2 Exec=/usr/lib/StruxureWare_Data_Center_Expert_7.4.2/DataCenterExpert %u Terminal=false Type=Application Icon=/usr/lib/StruxureWare_Data_Center_Expert_7.4.2/icon.xpm StartupNotify=true Categories=System;

and:

bash/usr/share/applications/apc-advanced-view.desktop[Desktop Entry] Encoding=UTF-8 Name=APC Advanced View 4.5.4 Comment=APC Advanced View 4.5.4 Exec=/usr/lib/APC_Advanced_View_4.5.4/Advanced_View %u Terminal=false Type=Application Icon=/usr/lib/APC_Advanced_View_4.5.4/av_icon.gif StartupNotify=true Categories=System;

That's it 😀.

(CID:114231484)

[DCIM_Support]

Thanks for sharing 😀 

(CID:114233581)

[DCIM_Support]

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