Use of 4760I

[freedom]

According to the TC that belongs to R9.1 (TC1244), with an update the option should be disabled.

12.2. OmniVista 4760i
This application is no more supported and can’t be activated anymore. Use mgr or OmniVista 4760
to configure the OmniPCX Enterprise. In case of upgrade to Release 9.1, the application will be
deactivated, if previously activated.

Would be nice if this disabling didn't work

[MrAnMo]

I think the 4760i is still in the system but ALU has removed the link from the system parameter menu. Does anybody now which sql table it is? I'm quite sure wen you wil directly in sql you will be able to enable it.

[frank]

It's actually a service that gets started and stopped.
If Apache is not present (and I can't say, I did not install 9.1 yet), then you can't do it.
You'll need not only apache, but the whole php scripts behind it. You might try to copy them.. if we can make a hack, we'll share.. and we did in the past !

[frank]

Ha, ha, ha.
I have upgraded company OXE to R9.1. 4760i was enabled in R9.0 and what You think does 4760i works on R9.1? You can try to answer in 3 times )))
You can't believe, it works. I have connected to http://xxx.xxx.xxx.xxx ( cpu IP), choosed configuration. Don't forget about JAVA compatibility or You need modify nmc_env.properties file under /usr3/httpd/nmc/html .
PC have downloaded R9.1 DB structure from OXE on first connection and it looks that works !!!!!
Its correct that doesn't exist 4760i option in SYSTEM PARAMETERS, but You need to proceed some tricky procedure.
1. Create empty DB on OXE R8 or R9.0; 2. Enable 4760i; 3. Make DB backup and upload on R9.1.

Nice !
Thanks for sharing

[OXE_4400]

One more thing. You need activate 4760i BEFORE installing R9.0 patch 38:
From R&D:
The 4760i application feature is not implemented in h1 301 38. This feature removed.This is normal behavior in h1 301 38. This feature is removed EOY 2009.

[OXE_4400]

It looks that 4760i completelly removed in R9.1 patch 13d. It worked with patch 12, but now I am getting red error message "Connection to administration server failed" ( on installed 4760i client ).
In both cases ( installed and browser based ) appear window for user and password entering after few seconds endless.

[OXE_4400]

I have compared startup of OXE with patch 12 and patch13d. OXE patch13d doesnt start 4760i at all. These messages appear in patch12:

@@@@@ Begin of '4760i_OnStartUp' at Wed Feb 10 17:31:59 2010
@@@@@ End of '4760i_OnStartUp' at Wed Feb 10 17:32:00 2010
@@@@@ Begin of 4760i_runconf at Wed Feb 10 17:32:09 2010

I have feeling that should be some config file with devalidated 4760i option. I saw that PC installer install 47860i components with patch13, its just question of some parameter.

[RTFM]

Unfortunately the 4760I is not stable and has also been used as a cheap Omnivista 4760 server alternative for those customers that only want to use the config app.

As stated in this thread there are two ways of getting the 4760i to work.

1. Set the "use of 4760" in a release < 9.0 Patch 38 and then upgrade to required release.

2. !Caution use this method at own risk!

via the console

>cdmao
>cuser

>select * from sysopt where instance=188; (sysopt 188 is "use of 4760" flag)

>update sysopt set value=1 where instance=188; (set value option 0="False" 1="True")

>commit; (apply changes)

>. (end cuser)

[OXE_4400]

As stated in this thread there are two ways of getting the 4760i to work.

1. Set the "use of 4760" in a release < 9.0 Patch 38 and then upgrade to required release.

>. (end cuser)

As I mentioned already first way doesn't work starting from R9.1 patch 13c, checked on two systems.

RTFM:

Are You sure that Your second proposal helps on R9.1 patch 13c or 13d?

[RTFM]

Hi OXE_4400,

If it didn't work then I wouldn't have made the effort to post it.

I have not tested patch 13c/d and mabey you can try method 2 and share your expierience with the rest of us?


(1)xa000000> cdmao
/DHS3data/mao
(1)xa000000> cuser
->> select * from sysopt where instance=188;


--> instance value
--> 188 0
Number of matching records = 1
temps d'execution = 0.000
->> update sysopt set value=1 where instance=188;

Number of matching records = 1
temps d'execution = 0.000
->> commit;

temps d'execution = 0.000
->> .

(1)xa000000>shutdown -r now

done...