Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 63 Insurance
- 535.7K On-Premises Infrastructure
- 138.1K Analytics Software
- 38.6K Application Development Software
- 5.6K Cloud Platform
- 109.3K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 71K Infrastructure Software
- 105.2K Integration
- 41.5K Security Software
WebLogic Portal (10.3.0) requires feature "com.m7.nitrox (1.0.20)" (?)

663562
Member Posts: 1
(I'm re-posting as recommended)
Greetings. I just installed WebLogic Portal 10.3 and I'm trying to install a couple of plug ins to Workshop/Eclipse, but whenever I select any item to install I get this error:
WebLogic Portal (10.3.0) requires feature "com.m7.nitrox (1.0.20)", or compatible.
Everything else seems to be working fine, so I'm not sure why my installation is giving me this issue. I've done a bit of digging already and haven't found what may be causing this issue, and I'm hoping someone here may be able to point me in the right direction.
Thanks!
Greetings. I just installed WebLogic Portal 10.3 and I'm trying to install a couple of plug ins to Workshop/Eclipse, but whenever I select any item to install I get this error:
WebLogic Portal (10.3.0) requires feature "com.m7.nitrox (1.0.20)", or compatible.
Everything else seems to be working fine, so I'm not sure why my installation is giving me this issue. I've done a bit of digging already and haven't found what may be causing this issue, and I'm hoping someone here may be able to point me in the right direction.
Thanks!
Best Answer
-
This is a known issue with WLP 10.3; it has been addressed for the next release of WLP. You could contact support to try to get a patch created (reference CR379999).
I can think of 2 possible workarounds:
1. Download the new plugin manually, and either a) create an extension location on the file system from it and add that via Help|Software Updates|Manage Configuration, or b) extract it to one of the workshop eclipse folders (i.e. tools/eclipse_pkgs/2.0/eclipse_3.3.2, tools/eclipse_pkgs/2.0/pkgs/eclipse, workshop_10.3/workshop4WP/eclipse, wlportal_10.3/eclipse) and restart Workshop.
2. Edit <beadir>/wlportal_10.3/eclipse/features/com.bea.wlp_10.3.0/feature.xml, comment out the <import feature="com.bea.*"/> lines in the <requires> block, restart Workshop, and try again.
Greg
Answers
-
This is a known issue with WLP 10.3; it has been addressed for the next release of WLP. You could contact support to try to get a patch created (reference CR379999).
I can think of 2 possible workarounds:
1. Download the new plugin manually, and either a) create an extension location on the file system from it and add that via Help|Software Updates|Manage Configuration, or b) extract it to one of the workshop eclipse folders (i.e. tools/eclipse_pkgs/2.0/eclipse_3.3.2, tools/eclipse_pkgs/2.0/pkgs/eclipse, workshop_10.3/workshop4WP/eclipse, wlportal_10.3/eclipse) and restart Workshop.
2. Edit <beadir>/wlportal_10.3/eclipse/features/com.bea.wlp_10.3.0/feature.xml, comment out the <import feature="com.bea.*"/> lines in the <requires> block, restart Workshop, and try again.
Greg
This discussion has been closed.