Anonymous_User Absent Member.
Absent Member.
440 views

Tool Designer frozen import process drivers


Friends,
I have a problem when I try to make an import of any driver through the
designer, in the process freezes and does not complete the importing
process.

Any suggestions for this case. Thanks


--
vaultuser
------------------------------------------------------------------------
vaultuser's Profile: https://forums.netiq.com/member.php?userid=294
View this thread: https://forums.netiq.com/showthread.php?t=3074

Labels (1)
0 Likes
10 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Tool Designer frozen import process drivers

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Which Designer version (and patch)? Which vault version? Has this
worked in the past? Does it work in another environment? How is your
connection between Designer and the vault? Are you able to create a new
driver config via iManager using the older preconfigs?

Good luck.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iQIcBAEBAgAGBQJQWcQeAAoJEF+XTK08PnB5BrsP/3PBShoi7s8fQYBDBXOTAZk8
4K11PYW/379O29d8mFZN3YnzrE5EdvTZ6QE8Ane27B/j8NEU4ysNbbrRjmIN6gtW
6xsEHzNOkBIdBAWnBauMe1SYMStsvFQl1PNmA0tRQ50slcfqzE5phtKoWvlnMTWy
lyJI+68scvr8Oym/CFA9WFrn48zlEjT9K7OIOt/VzgJDxYN5itEDwUgWdbjIK6/t
J/a5g2CHHKGs/PuuRGN9uw4pOpx8RXiNeXlAXwFTE5iKO18iBxkJviKSr3oejirF
cZxnwQ9YaUU4SCB880ly9PxkaQYJM8P24X61CcBUmMxyTiiRWWK9zB3DV3KBDgqo
ljICtHKoXlHku1cF7BuIDpZLTI/8DQKfy0RVnIAhhWpoGDO8YnABErG9acWc40Yl
THZuilx4iLXgE78tr0RAaAi2l6j2LbOsSGa9FCxczUlDJFwNBV1h7sjc2vRWxyLc
UpHOHFCckdvgqXYbS/NtfSN2QiRoHbieTQhbGxg5xsEAukyzcsgrz7/hHWklr4WQ
ggnsH5RwByFE9wG5CrChH5uq8ucB7z/8Gfeqi2L+3FLEfMs5rpjzMpoMb3aqYvZy
Hipj/1/mH+1wmPALAlScpzt85Im14OSfqdpNDfVezuucZNYjecN6Rr4AWId66TxO
j6HgMVnSmlAxr6kZvcyI
=6Qxb
-----END PGP SIGNATURE-----
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Tool Designer frozen import process drivers


Hello friend,
The designer version used is:
Designer for Novell Identity Manager

Version: 4.0.1 Auto Update
Build ID: 20111202

The PC if you have connection to the Vault. The procedure is attempted
is an import of the drivers that are in the vault with this tool.

Changed the configuration file to designer.ini shown below:
-Vm
D:\Designer\jre\bin\javaw.exe
-Clean
-Vmargs
-Xms512m
-Xmx1024M
-XX: MaxPermSize = 512m
-Dfile.encoding = UTF-8

And succeeded to import driver with an error at the end of the process:

java.lang.OutOfMemoryError: Java heap space

com.novell.prov.role.impl.RoleFactoryImpl.createLocalized (Unknown
Source)
com.novell.prov.role.impl.RoleFactoryImpl.create (Unknown Source)
org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.createObject
(XMLHelperImpl.java: 884)
org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.createObject
(XMLHelperImpl.java: 920)
org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectFromFactory
(XMLHandler.java: 2171)
org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectFromFeatureType
(XMLHandler.java: 2144)
org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObject
(XMLHandler.java: 2020)
org.eclipse.emf.ecore.xmi.impl.XMIHandler.createObject
(XMIHandler.java: 131)
org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature
(XMLHandler.java: 1825)
org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement
(XMLHandler.java: 1023)
org.eclipse.emf.ecore.xmi.impl.XMIHandler.processElement
(XMIHandler.java: 87)
org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement
(XMLHandler.java: 1001)
org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement
(XMLHandler.java: 712)
org.eclipse.emf.ecore.xmi.impl.XMIHandler.startElement
(XMIHandler.java: 167)
org.apache.xerces.parsers.AbstractSAXParser.startElement (Unknown
Source)
org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement
(Unknown Source)
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement
(Unknown Source)
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl $
FragmentContentDispatcher.dispatch (Unknown Source)
org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument
(Unknown Source)
org.apache.xerces.parsers.XML11Configuration.parse (Unknown Source)
org.apache.xerces.parsers.XML11Configuration.parse (Unknown Source)
org.apache.xerces.parsers.XMLParser.parse (Unknown Source)
org.apache.xerces.parsers.AbstractSAXParser.parse (Unknown Source)
org.apache.xerces.jaxp.SAXParserImpl $ JAXPSAXParser.parse (Unknown
Source)
org.apache.xerces.jaxp.SAXParserImpl.parse (Unknown Source)
org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load (XMLLoadImpl.java: 181)
org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad
(XMLResourceImpl.java: 180)
org.eclipse.emf.ecore.resource.impl.ResourceImpl.load
(ResourceImpl.java: 1445)
org.eclipse.emf.ecore.resource.impl.ResourceImpl.load
(ResourceImpl.java: 1241)
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoad
(ResourceSetImpl.java: 255)
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper
(ResourceSetImpl.java: 270)
org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResource
(ResourceSetImpl.java: 397)

Any recommendations for solving this process.
Thanks


--
vaultuser
------------------------------------------------------------------------
vaultuser's Profile: https://forums.netiq.com/member.php?userid=294
View this thread: https://forums.netiq.com/showthread.php?t=3074

0 Likes
Knowledge Partner
Knowledge Partner

Re: Tool Designer frozen import process drivers

Run on 64 bit linux, so you can use a 64 bit JVM. 🙂

I think your Role Catalog may be a smidgen large.

You can choose to import everything, but exclude the User App driver.

Then in a second pass, try the user app driver by itself.

if you are stick on Winders, you can boost the -Xmx1024M to -Xmx1200 I
find to get an extra 200 megs of heap which can make the difference.


On 9/19/2012 11:44 AM, vaultuser wrote:
>
> Hello friend,
> The designer version used is:
> Designer for Novell Identity Manager
>
> Version: 4.0.1 Auto Update
> Build ID: 20111202
>
> The PC if you have connection to the Vault. The procedure is attempted
> is an import of the drivers that are in the vault with this tool.
>
> Changed the configuration file to designer.ini shown below:
> -Vm
> D:\Designer\jre\bin\javaw.exe
> -Clean
> -Vmargs
> -Xms512m
> -Xmx1024M
> -XX: MaxPermSize = 512m
> -Dfile.encoding = UTF-8
>
> And succeeded to import driver with an error at the end of the process:
>
> java.lang.OutOfMemoryError: Java heap space
>
> com.novell.prov.role.impl.RoleFactoryImpl.createLocalized (Unknown
> Source)
> com.novell.prov.role.impl.RoleFactoryImpl.create (Unknown Source)
> org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.createObject
> (XMLHelperImpl.java: 884)
> org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.createObject
> (XMLHelperImpl.java: 920)
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectFromFactory
> (XMLHandler.java: 2171)
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObjectFromFeatureType
> (XMLHandler.java: 2144)
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.createObject
> (XMLHandler.java: 2020)
> org.eclipse.emf.ecore.xmi.impl.XMIHandler.createObject
> (XMIHandler.java: 131)
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature
> (XMLHandler.java: 1825)
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement
> (XMLHandler.java: 1023)
> org.eclipse.emf.ecore.xmi.impl.XMIHandler.processElement
> (XMIHandler.java: 87)
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement
> (XMLHandler.java: 1001)
> org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement
> (XMLHandler.java: 712)
> org.eclipse.emf.ecore.xmi.impl.XMIHandler.startElement
> (XMIHandler.java: 167)
> org.apache.xerces.parsers.AbstractSAXParser.startElement (Unknown
> Source)
> org.apache.xerces.parsers.AbstractXMLDocumentParser.emptyElement
> (Unknown Source)
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanStartElement
> (Unknown Source)
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl $
> FragmentContentDispatcher.dispatch (Unknown Source)
> org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument
> (Unknown Source)
> org.apache.xerces.parsers.XML11Configuration.parse (Unknown Source)
> org.apache.xerces.parsers.XML11Configuration.parse (Unknown Source)
> org.apache.xerces.parsers.XMLParser.parse (Unknown Source)
> org.apache.xerces.parsers.AbstractSAXParser.parse (Unknown Source)
> org.apache.xerces.jaxp.SAXParserImpl $ JAXPSAXParser.parse (Unknown
> Source)
> org.apache.xerces.jaxp.SAXParserImpl.parse (Unknown Source)
> org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load (XMLLoadImpl.java: 181)
> org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad
> (XMLResourceImpl.java: 180)
> org.eclipse.emf.ecore.resource.impl.ResourceImpl.load
> (ResourceImpl.java: 1445)
> org.eclipse.emf.ecore.resource.impl.ResourceImpl.load
> (ResourceImpl.java: 1241)
> org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoad
> (ResourceSetImpl.java: 255)
> org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper
> (ResourceSetImpl.java: 270)
> org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.getResource
> (ResourceSetImpl.java: 397)
>
> Any recommendations for solving this process.
> Thanks
>
>


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Tool Designer frozen import process drivers


Friend,
The designer is in Windows 7 (64-bit), in this process only driver
userapp matter.
When the change was made, in designer.ini file:
-vm
😧 \ Designer \ jre \ bin \ javaw.exe
-clean
-vmargs
-Xms512m
-Xmx1200m
-XX: MaxPermSize = 512m
-Dfile.encoding = UTF-8

No launch the Designer, the message shown here:
Could not create the java virtual machine


--
vaultuser
------------------------------------------------------------------------
vaultuser's Profile: https://forums.netiq.com/member.php?userid=294
View this thread: https://forums.netiq.com/showthread.php?t=3074

0 Likes
Knowledge Partner
Knowledge Partner

Re: Tool Designer frozen import process drivers

On 9/19/2012 4:04 PM, vaultuser wrote:
>
> Friend,
> The designer is in Windows 7 (64-bit), in this process only driver
> userapp matter.
> When the change was made, in designer.ini file:
> -vm
> 😧 \ Designer \ jre \ bin \ javaw.exe
> -clean
> -vmargs
> -Xms512m
> -Xmx1200m
> -XX: MaxPermSize = 512m
> -Dfile.encoding = UTF-8
>
> No launch the Designer, the message shown here:
> Could not create the java virtual machine


Oh, drop your PermSize from 512 to 128. Too much total.

PermSize is needed to hold the JAR's for Eclipse/Designer to actually
run, but 128 should work.

So Max 1200, permsize 128, and try again.

Are you using 4.02? There was something added in 4.02 to handle NOT
importing Roles.

You MIGHT be able to use permissions to import the whole thing, minus
the Role Catalog. Then switch users to one who can see the catalog and
try to get the rest, then switch back to a proper user.

Or you could try an iManager export of the driver and import that into
Designer.


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Tool Designer frozen import process drivers


Hello friend,
Can you tell me the URL where the certification indicates the JDK / JRE
for each version of the designer 4.0.0, 4.0.1, 4.0.2


thanks


--
vaultuser
------------------------------------------------------------------------
vaultuser's Profile: https://forums.netiq.com/member.php?userid=294
View this thread: https://forums.netiq.com/showthread.php?t=3074

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Tool Designer frozen import process drivers

vaultuser wrote:

> No launch the Designer, the message shown here:
> Could not create the java virtual machine


Seen this with earlier 40x releases, too. Seems to work again with the 402
Refresh, though.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Tool Designer frozen import process drivers


Friends,
Perform the upgrade to version 4.0.2 designer. and I still have the
same problem, you can not import any driver ...?


--
vaultuser
------------------------------------------------------------------------
vaultuser's Profile: https://forums.netiq.com/member.php?userid=294
View this thread: https://forums.netiq.com/showthread.php?t=3074

0 Likes
Knowledge Partner
Knowledge Partner

Re: Tool Designer frozen import process drivers

On 9/22/2012 1:04 AM, vaultuser wrote:
>
> Friends,
> Perform the upgrade to version 4.0.2 designer. and I still have the
> same problem, you can not import any driver ...?


There is supposed to be something in 4.02 about not importing all roles
for just this case.

Window menu, Preferences, expand Novell, then provisioning, the
Import/Deploy

Role Catalog section has three choices. Do no import, Prompt, and Auto
import. Mine is set to Prompt. What is yours?


0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Tool Designer frozen import process drivers


Hello Friend,
The option chosen when I try to import any driver is:
DO NOT IMPORT ROLE CATALOG (EXCLUDING SYSTEM ROLES)


Regards,


--
vaultuser
------------------------------------------------------------------------
vaultuser's Profile: https://forums.netiq.com/member.php?userid=294
View this thread: https://forums.netiq.com/showthread.php?t=3074

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.