On deploy a prefix is add

Hello:
Tools --> Options -->Compiler  I set <b>com.company.project</b>.
The IView 's name is: <u>Viernes</u> but when I deploy and run the IView the URL is complete with some numbers and letters:
http://host/irj/servlet/prt/portal/prtroot/com.sap.portal.navigation.portallauncher.default?NavigationTarget=ROLES%3A%2F%2Fportal_content%2Fcom.sap.gm.cnt%2Fcore%2FVCRole%2FPreviewWorkArea&object=pcd%3Aportal_content%2Fcom.sap.gm.cnt%2Fvcmodels%2Fcom.company.project.1.Javier%2Fcom.company.project.iviews%2F<b>com.company.project.1XD.Viernes</b>
Why is it <b>1XD</b> add? (com.company.project.<b>1XD</b>.Viernes)
Something gives a different number to each iView and uses it to concatenate the prefix with the IView 's name.
Any Idea?
Thanks a lot for the time on this thread.
RLS.

Hi
This seems to be part of the iview ID and is added by the portal.
Jarrod Williams

Similar Messages

  • Deploy crystal report with add-on package by b1de

    Hi
    I have some problem with add-on installer. after i package add-on by b1de, I install it on client machine. It works correctly. But when i call report, It have error with crystal report license code and .dll. I found solution that solve that problem. I must include crystal report merge module and License code into  windows installer project. But i use b1de to package. How i can include crystal report merge module and License code into b1de project . If anybody have other method to package crystal report into b1de. please help me.
    Regards,Seang

    for this problem I created window installer which only have merge modules of crystel report & provide it to user to install it as well , bcz sap installer was not including merge modules
    , how ever u can try professional installer of SAP DE
    but I have not try it,

  • Billing CDR prefix Error Billing CDR prefix Error Billing CDR prefix Error

    Thank you for your help.
    i have this question, My AS5400 send CDR for my Billing System ... but the calls or CDR for incoming national calls (Mobile & Fix)to my network are coming without prefix for our local and national calls which is 00962, on other hand calls from my network to other local carriers include the prefix 00962...is it clear?
    All other International calls include correct prefixes no problem.
    Example:
    Local Mobile= 0777223344
    Local Fix= 064536543
    my network= 063000000
    Jordan Prefix= 962
    Now call from o777223344 or 064536543
    to 063000000 has the error where CDR at Billing system without 00962 it is only 063000000 it is not 96263000000 this take us that call comes from Phillipines Fix 63 and not from my network 63000000.
    Remember calls from 063000000 to any destination is right prefix.
    any help please at AS5400 or PGW2200??

    Hi,
    Without knowing if you are using switched or nailed PGW config, I can say there are 2 solutions. One on the PGW
    and one on the 5400. You can choose which solution fits you the best.
    PGW Nailed solution:
    Setup a bmoddig in a dialplan to prefix 962 to any number coming in starting with 63
    Apply custgrpid to incoming ss7path.
    #### creates the dialplan ####
    numan-add:dialplan:custgrpid="lma3", OVERDEC="YES"
    #### digits to prefix ####
    numan-add:digmodstring:custgrpid="lma3",name="add962",digstring="962"
    ### result set for dialplan ####
    numan-add:resultset:custgrpid="lma3",name="addpre"
    #### modify the b number starting at the beginning and add the digits specified in digmodstring ####
    numan-add:resulttable:custgrpid="lma3",name="addprefix",resulttype="BMODDIG",dw1="1",dw2="0",dw3="add962",setname="addpre"
    #### Route based on B number starting with digits 63 ####
    numan-add:bdigtree:custgrpid="lma3",callside="originating",digitstring="63",setname="addpre"
    #### Apply custgrpid to incoming ss7path ####
    prov-ed:sigsvcprop:name="ss7path",custgrpid="lma3"
    ### Deploy config ####
    prov-dply
    Restart of PGW software may be needed.
    PGW switched solution:
    Setup a bmoddig in a dialplan to prefix 962 to any number coming in starting with 63
    Apply custgrpid to incoming ss7 trunkgrp.
    #### creates the dialplan ####
    numan-add:dialplan:custgrpid="lma3", OVERDEC="YES"
    #### digits to prefix ####
    numan-add:digmodstring:custgrpid="lma3",name="add962",digstring="962"
    ### result set for dialplan ####
    numan-add:resultset:custgrpid="lma3",name="addpre"
    #### modify the b number starting at the beginning and add the digits specified in digmodstring ####
    numan-add:resulttable:custgrpid="lma3",name="addprefix",resulttype="BMODDIG",dw1="1",dw2="0",dw3="add962",setname="addpre"
    #### Route based on B number starting with digits 63 ####
    numan-add:bdigtree:custgrpid="lma3",callside="originating",digitstring="63",setname="addpre"
    #### Apply custgrpid to incoming ss7 trunkgrp ####
    prov-ed:trnkgrpprop:name="1000",custgrpid="lma3"
    ### Deploy config ####
    prov-dply
    Restart of PGW software may be needed.
    NAS Solution:
    Create a voice translation rule to prefix 962 to 63 number.
    Apply to incoming pots voice port
    voice translation-rule 1
    rule 1 /\(^63\)/ /962\1/
    voice translation-profile add962
    translate called 1
    voice-port 2:D
    translation-profile incoming add962

  • Deployment error while deploying targeters in BCC

    Hi,
    I am trying to create a targeter with content groups and media internal texts. Whenever i deploy a project with these assets, i get deployment error.
    It says "Deployment '169200010' to target 'production' encountered a system level deployment error during data transfer. An automatic rollback deployment has successfully occurred, preserving the state of target 'production'. Click 'Resume' to re-attempt the deployment."
    I checked for the VFS set up for targeters and content groups and they are in place.
    There are 3 assets in the project. It says the asset already exists
    The error log below : I am struck up here and not able to take any step further. Please share your inputs on this
    2013-06-20 22:40:25,569 WARN  [nucleusNamespace.atg.epub.PublishingRepository] (http-172.19.0.197-40180-6) Using default JDBC type for: project:tar82 could not find this column in the table's meta data
    2013-06-20 22:40:51,348 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG Run first apply phase: true
    2013-06-20 22:40:51,349 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG Switch switchable CA datasources:
    2013-06-20 22:40:51,349 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG   isDeploymentRollback(): false
    2013-06-20 22:40:51,360 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG   Current Target live datasource name: DataSourceB
    2013-06-20 22:40:51,360 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG   CA switching datasource: /atg/commerce/jdbc/ProductCatalogSwitchingDataSource_production
    2013-06-20 22:40:51,361 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG     Current live datasource name: DataSourceA
    2013-06-20 22:40:51,361 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG     Current offline datasource name: DataSourceB
    2013-06-20 22:40:51,361 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG     The current CA live datasource is pointing at the Target offline datasource. No CA switch necessary.
    2013-06-20 22:40:51,361 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG Switchable CA datasources switched.
    2013-06-20 22:40:51,408 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG DistributedDeploymentAdapter:DAF Deployment with ID: 169200010 not previously deployed.
    2013-06-20 22:40:51,414 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG DistributedDeploymentAdapter:Creating standard DeploymentData
    2013-06-20 22:40:51,446 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG Forward deploying following active workspaces: [workspace:118102]
    2013-06-20 22:40:53,770 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG DistributedDeploymentAdapter:Deploy Data
    2013-06-20 22:40:53,771 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG DistributedDeploymentAdapter:Starting DAF deployment with ID: 169200010
    2013-06-20 22:40:53,776 INFO  [nucleusNamespace.atg.deployment.DeploymentManager] (Thread-103) Database: Oracle
    2013-06-20 22:40:53,922 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-103) DEBUG DistributedDeploymentAdapter:Polling Until Data Appplied
    2013-06-20 22:40:53,922 INFO  [nucleusNamespace.atg.deployment.DeploymentManager] (Main deployment thread: ) Starting deployment with id: 169200010
    2013-06-20 22:40:53,950 INFO  [nucleusNamespace.atg.deployment.DeploymentManager] (Main deployment thread: ) Executing deployment in LOCAL mode
    2013-06-20 22:40:55,442 WARN  [nucleusNamespace.atg.deployment.DeploymentManager] (FileWorkerThread-2(Add-Update Phase)) Attempt to add file that already exists: file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem
    2013-06-20 22:40:55,461 WARN  [nucleusNamespace.atg.deployment.DeploymentManager] (FileWorkerThread-2(Add-Update Phase))  item = fileMarker:mark106400001 cause = CONTAINER:atg.deployment.file.DeploymentSourceException: Attempt to add file that already exists: file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem; SOURCE:deploymentHandlerFileToAddExists: level 3: Attempt to add file that already exists: file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem
    atg.deployment.file.DeploymentTargetException: Attempt to add file that already exists: file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem
      at atg.deployment.file.FileWorkerThread.handleError(FileWorkerThread.java:1278)
      at atg.deployment.file.FileWorkerThread.runCommand(FileWorkerThread.java:762)
      at atg.deployment.file.FileWorkerThread.processMarkerForAddUpdatePhase(FileWorkerThread.java:463)
      at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:562)
      at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:335)
    message = Attempt to add file that already exists: file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem time = Thu Jun 20 22:40:55 CDT 2013  atg.deployment.DeploymentFailure@17dc0e19
    2013-06-20 22:40:55,490 WARN  [nucleusNamespace.atg.deployment.DeploymentManager] (FileWorkerThread-2(Add-Update Phase)) Attempt to add file that already exists: file /atg/registry/RepositoryTargeters/home_spot1_targeter.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem
    2013-06-20 22:40:55,490 WARN  [nucleusNamespace.atg.deployment.DeploymentManager] (FileWorkerThread-2(Add-Update Phase))  item = fileMarker:mark106400002 cause = CONTAINER:atg.deployment.file.DeploymentSourceException: Attempt to add file that already exists: file /atg/registry/RepositoryTargeters/home_spot1_targeter.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem; SOURCE:deploymentHandlerFileToAddExists: level 3: Attempt to add file that already exists: file /atg/registry/RepositoryTargeters/home_spot1_targeter.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem
    atg.deployment.file.DeploymentTargetException: Attempt to add file that already exists: file /atg/registry/RepositoryTargeters/home_spot1_targeter.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem
      at atg.deployment.file.FileWorkerThread.handleError(FileWorkerThread.java:1278)
      at atg.deployment.file.FileWorkerThread.runCommand(FileWorkerThread.java:762)
      at atg.deployment.file.FileWorkerThread.processMarkerForAddUpdatePhase(FileWorkerThread.java:463)
      at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:562)
      at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:335)
    message = Attempt to add file that already exists: file /atg/registry/RepositoryTargeters/home_spot1_targeter.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem time = Thu Jun 20 22:40:55 CDT 2013  atg.deployment.DeploymentFailure@38d281d4
    2013-06-20 22:40:55,547 WARN  [nucleusNamespace.atg.deployment.DeploymentManager] (FileWorkerThread-2(Add-Update Phase)) Attempt to add file that already exists: file /atg/registry/RepositoryGroups/home_spot1_content_group.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem
    2013-06-20 22:40:55,547 WARN  [nucleusNamespace.atg.deployment.DeploymentManager] (FileWorkerThread-2(Add-Update Phase))  item = fileMarker:mark106400003 cause = CONTAINER:atg.deployment.file.DeploymentSourceException: Attempt to add file that already exists: file /atg/registry/RepositoryGroups/home_spot1_content_group.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem; SOURCE:deploymentHandlerFileToAddExists: level 3: Attempt to add file that already exists: file /atg/registry/RepositoryGroups/home_spot1_content_group.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem
    atg.deployment.file.DeploymentTargetException: Attempt to add file that already exists: file /atg/registry/RepositoryGroups/home_spot1_content_group.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem
      at atg.deployment.file.FileWorkerThread.handleError(FileWorkerThread.java:1278)
      at atg.deployment.file.FileWorkerThread.runCommand(FileWorkerThread.java:762)
      at atg.deployment.file.FileWorkerThread.processMarkerForAddUpdatePhase(FileWorkerThread.java:463)
      at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:562)
      at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:335)
    message = Attempt to add file that already exists: file /atg/registry/RepositoryGroups/home_spot1_content_group.properties in VirtualFileSystem /atg/epub/file/ConfigFileSystem time = Thu Jun 20 22:40:55 CDT 2013  atg.deployment.DeploymentFailure@70126ca0
    2013-06-20 22:40:55,684 ERROR [nucleusNamespace.atg.deployment.DeploymentManager] (FileWorkerThread-2(Add-Update Phase))
    CAUGHT AT:
    CONTAINER:atg.deployment.file.DeploymentSourceException: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null; SOURCE:deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null; SOURCE:java.io.IOException: There was a repository exception while trying to create the file: /atg/registry/RepositoryGroups/home_spot1_user.properties in file system: /atg/epub/file/ConfigFileSystem. exception: atg.repository.RepositoryException: current development line null is not an open workspace..
      at atg.deployment.file.FileWorkerThread.handleErrorLogging(FileWorkerThread.java:1261)
      at atg.deployment.file.FileWorkerThread.handleError(FileWorkerThread.java:1276)
      at atg.deployment.file.FileWorkerThread.runCommand(FileWorkerThread.java:762)
      at atg.deployment.file.FileWorkerThread.processMarkerForAddUpdatePhase(FileWorkerThread.java:463)
      at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:562)
      at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:335)
    Caused by: deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null; SOURCE:java.io.IOException: There was a repository exception while trying to create the file: /atg/registry/RepositoryGroups/home_spot1_user.properties in file system: /atg/epub/file/ConfigFileSystem. exception: atg.repository.RepositoryException: current development line null is not an open workspace..
      at atg.deployment.file.DeploymentSourceException.<init>(DeploymentSourceException.java:74)
      ... 6 more
    SOURCE EXCEPTION:
    deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null; SOURCE:java.io.IOException: There was a repository exception while trying to create the file: /atg/registry/RepositoryGroups/home_spot1_user.properties in file system: /atg/epub/file/ConfigFileSystem. exception: atg.repository.RepositoryException: current development line null is not an open workspace..
    2013-06-20 22:40:55,685 ERROR [nucleusNamespace.atg.deployment.DeploymentManager] (FileWorkerThread-2(Add-Update Phase))  item = fileMarker:mark106400004 cause = CONTAINER:atg.deployment.file.DeploymentSourceException: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null; SOURCE:deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null; SOURCE:java.io.IOException: There was a repository exception while trying to create the file: /atg/registry/RepositoryGroups/home_spot1_user.properties in file system: /atg/epub/file/ConfigFileSystem. exception: atg.repository.RepositoryException: current development line null is not an open workspace..
      at atg.deployment.file.FileWorkerThread.handleError(FileWorkerThread.java:1278)
      at atg.deployment.file.FileWorkerThread.runCommand(FileWorkerThread.java:762)
      at atg.deployment.file.FileWorkerThread.processMarkerForAddUpdatePhase(FileWorkerThread.java:463)
      at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:562)
      at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:335)
    message = IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null time = Thu Jun 20 22:40:55 CDT 2013  atg.deployment.DeploymentFailure@1f344a25
    CAUGHT AT:
    CONTAINER:atg.deployment.file.DeploymentSourceException: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null; SOURCE:deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null; SOURCE:java.io.IOException: There was a repository exception while trying to create the file: /atg/registry/RepositoryGroups/home_spot1_user.properties in file system: /atg/epub/file/ConfigFileSystem. exception: atg.repository.RepositoryException: current development line null is not an open workspace..
      at atg.deployment.file.FileWorkerThread.handleError(FileWorkerThread.java:1278)
      at atg.deployment.file.FileWorkerThread.runCommand(FileWorkerThread.java:762)
      at atg.deployment.file.FileWorkerThread.processMarkerForAddUpdatePhase(FileWorkerThread.java:463)
      at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:562)
      at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:335)
    Caused by: deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/home_spot1_user.properties in VirtualFileSystem null; SOURCE:java.io.IOException: There was a repository exception while trying to create the file: /atg/registry/RepositoryGroups/home_spot1_user.properties in file system: /atg/epub/file/ConfigFileSystem. exception: atg.repository.RepositoryException: current development line null is not an open workspace..
      at atg.deployment.file.DeploymentSourceException.<init>(DeploymentSourceException.java:74)
      ... 5 more
    SOURCE EXCEPTION:

    yes i checked. To clear this out, i created a new project with new set of content groups and targeters.
    It throws this error. I get this error at 30% of deployment
    2013-06-21 12:04:07,944 INFO  [nucleusNamespace.atg.deployment.DeploymentManager] (Thread-124) Database: Oracle
    2013-06-21 12:04:07,959 INFO  [nucleusNamespace.atg.epub.DeploymentServer] (Thread-124) DEBUG DistributedDeploymentAdapter:Polling Until Data Appplied
    2013-06-21 12:04:07,959 INFO  [nucleusNamespace.atg.deployment.DeploymentManager] (Main deployment thread: ) Starting deployment with id: 135200010
    2013-06-21 12:04:07,970 INFO  [nucleusNamespace.atg.deployment.DeploymentManager] (Main deployment thread: ) Executing deployment in LOCAL mode
    2013-06-21 12:04:09,708 ERROR [nucleusNamespace.atg.deployment.DeploymentManager] (FileWorkerThread-1(Add-Update Phase))
    CAUGHT AT:
    CONTAINER:atg.deployment.file.DeploymentSourceException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:java.io.IOException: Cannot create OutputStream for read-only ContentRepositoryItem: /atg/registry/RepositoryGroups/homePage/group1.properties  OutputStreams can only be created for mutable ContentRepositoryItem objects.
      at atg.deployment.file.FileWorkerThread.handleErrorLogging(FileWorkerThread.java:1261)
      at atg.deployment.file.FileWorkerThread.handleError(FileWorkerThread.java:1276)
      at atg.deployment.file.FileWorkerThread.runCommand(FileWorkerThread.java:762)
      at atg.deployment.file.FileWorkerThread.processMarkerForAddUpdatePhase(FileWorkerThread.java:463)
      at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:562)
      at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:335)
    Caused by: deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:java.io.IOException: Cannot create OutputStream for read-only ContentRepositoryItem: /atg/registry/RepositoryGroups/homePage/group1.properties  OutputStreams can only be created for mutable ContentRepositoryItem objects.
      at atg.deployment.file.DeploymentSourceException.<init>(DeploymentSourceException.java:74)
      ... 6 more
    SOURCE EXCEPTION:
    deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:java.io.IOException: Cannot create OutputStream for read-only ContentRepositoryItem: /atg/registry/RepositoryGroups/homePage/group1.properties  OutputStreams can only be created for mutable ContentRepositoryItem objects.
    2013-06-21 12:04:09,715 ERROR [nucleusNamespace.atg.deployment.DeploymentManager] (FileWorkerThread-1(Add-Update Phase))  item = fileMarker:mark115500048 cause = CONTAINER:atg.deployment.file.DeploymentSourceException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:java.io.IOException: Cannot create OutputStream for read-only ContentRepositoryItem: /atg/registry/RepositoryGroups/homePage/group1.properties  OutputStreams can only be created for mutable ContentRepositoryItem objects.
      at atg.deployment.file.FileWorkerThread.handleError(FileWorkerThread.java:1278)
      at atg.deployment.file.FileWorkerThread.runCommand(FileWorkerThread.java:762)
      at atg.deployment.file.FileWorkerThread.processMarkerForAddUpdatePhase(FileWorkerThread.java:463)
      at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:562)
      at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:335)
    message = IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null time = Fri Jun 21 12:04:09 CDT 2013  atg.deployment.DeploymentFailure@7bbc32e1
    CAUGHT AT:
    CONTAINER:atg.deployment.file.DeploymentSourceException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:java.io.IOException: Cannot create OutputStream for read-only ContentRepositoryItem: /atg/registry/RepositoryGroups/homePage/group1.properties  OutputStreams can only be created for mutable ContentRepositoryItem objects.
      at atg.deployment.file.FileWorkerThread.handleError(FileWorkerThread.java:1278)
      at atg.deployment.file.FileWorkerThread.runCommand(FileWorkerThread.java:762)
      at atg.deployment.file.FileWorkerThread.processMarkerForAddUpdatePhase(FileWorkerThread.java:463)
      at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:562)
      at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:335)
    Caused by: deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:java.io.IOException: Cannot create OutputStream for read-only ContentRepositoryItem: /atg/registry/RepositoryGroups/homePage/group1.properties  OutputStreams can only be created for mutable ContentRepositoryItem objects.
      at atg.deployment.file.DeploymentSourceException.<init>(DeploymentSourceException.java:74)
      ... 5 more
    SOURCE EXCEPTION:
    deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:java.io.IOException: Cannot create OutputStream for read-only ContentRepositoryItem: /atg/registry/RepositoryGroups/homePage/group1.properties  OutputStreams can only be created for mutable ContentRepositoryItem objects.
    2013-06-21 12:04:09,741 ERROR [nucleusNamespace.atg.deployment.DeploymentManager] (FileWorkerThread-1(Add-Update Phase))  item = fileMarker:mark115500048 cause = CONTAINER:atg.deployment.file.DeploymentSourceException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:deploymentHandlerUnableToWrite: level 4: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null
    CONTAINER:atg.deployment.file.DeploymentTargetException: IOException received while trying to write file /atg/registry/RepositoryGroups/homePage/group1.properties in VirtualFileSystem null; SOURCE:java.io.IOException: Cannot create OutputStream for read-only ContentRepositoryItem: /atg/registry/RepositoryGroups/homePage/group1.properties  OutputStreams can only be created for mutable ContentRepositoryItem objects.

  • Error while deploying ADF web application from JDeveloper 11g to Web Logic

    Hi,
    I developed application following "Developing RIA Web Applications with Oracle ADF" tutorial.
    It works fine when started locally, from JDevelopwr 11g (11.1.1.1.0).
    I tried to deploy it to remote Oracle WebLogic Server (10.3.1, with ADF libraries installed) from JDeveloper, but got:
    +[02:29:00 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application HRDemo on AdminServer.: Failed to load webapp: 'HRDemo.war'.+
    +[02:29:00 PM] Weblogic Server Exception: weblogic.application.ModuleException: Failed to load webapp: 'HRDemo.war'+
    +[02:29:00 PM] Caused by: java.lang.ClassNotFoundException: oracle.adf.library.webapp.ResourceServlet+
    +[02:29:00 PM] See server logs or server console for more details.+
    +[02:29:00 PM] weblogic.application.ModuleException: Failed to load webapp: 'HRDemo.war'+
    +[02:29:00 PM] #### Deployment incomplete. ####+
    +[02:29:00 PM] Deployment Failed+
    Tried to add "ADF Common Web Runtime" to deployment profile's "Libraries selected for deployment" but than got:
    +[02:52:44 PM] [Deployer:149034]An exception occurred for task [Deployer:149026]deploy application HRSystem_ViewController_webapp1 on AdminServer.: Failed to load webapp: 'HRSystem_ViewController_webapp1.war'.+
    +[02:52:44 PM] Weblogic Server Exception: weblogic.application.ModuleException: Failed to load webapp: 'HRSystem_ViewController_webapp1.war'+
    +[02:52:44 PM] Caused by: java.lang.ClassNotFoundException: oracle.jsp.runtimev2.JspServlet+
    +[02:52:44 PM] See server logs or server console for more details.+
    +[02:52:44 PM] weblogic.application.ModuleException: Failed to load webapp: 'HRSystem_ViewController_webapp1.war'+
    +[02:52:44 PM] #### Deployment incomplete. ####+
    +[02:52:44 PM] Deployment Failed+
    Regards,
    Zdravko.
    Edited by: [email protected] on Sep 10, 2009 2:58 PM

    Hi,
    We did that earlier, too (modified existing domain).
    Also, after that, we created new domain and extended it according to you suggestions but no change.
    Regards,
    Zdravko.
    Edited by: [email protected] on Sep 11, 2009 10:20 AM

  • Mapping Input Parameter renders mapping unable to be compiled or deployed

    Hi there. I have an interesting issue I have not encountered before.
    I can create a new mapping with a Mapping Input Parameter (just one parameter of type Integer), map this to a table column of the same type and the mapping compiles and deploys without any issues.
    However, if I take an existing mapping (which already compiles and deploys without issues), add a Mapping Input Parameter to it (just one parameter of type Integer) and map this parameter through to a table column of the same type, when I compile the mapping I get a pop-up "Warehouse Builder Error" with a number 56 and a red cross. The mapping cannot generate any code and gives no explaination. Trying this on a different mapping causes the same issue but with a different number in the pop-up.
    I have tried changing the parameter from integer to another data type and this makes no difference.
    Removing the Mapping Input Parameter makes the mapping compilable and deployable again.
    Am I missing something here ?
    Thanks
    Paul

    Ok... this could be a bug, but I worked out how to resolve the issue.
    To get the issue:-
    1. Open a mapping which does not have a Mapping Input Parameter and compiles and deploys happily
    2. Add a Mapping Input Parameter object, add an output attribute to it and map it to a table column.
    3. Compile the mapping and you get a "Warehouse Builder Error" pop-up with a number, then a Validation Completed Successfully message. But no code can be generated and the mapping
    cannot be deployed.
    4. Slap your forehead and say "Doh!"
    To fix the issue :-
    1. Open the same mapping
    2. Resynch the tables you mapped the Mapping Input Parameter to. The mapping now compiles and deploys ok.
    3. Pat yourself on the back
    cheers
    Paul

  • NullPointerException when deploying sateless session bean

    I'm deploying a simple Stateless Session Bean, my deployment descriptors are
    being generated with xdoclet. I'm getting the following exception:
    weblogic.management.ApplicationException:
    Exception:weblogic.management.ApplicationException: prepare failed for
    formulacionEJB.jar
    Module: formulacionEJB.jar Error: Exception preparing module:
    EJBModule(formulacionEJB.jar,status=NEW)
    Unable to deploy EJB:
    C:\bea\user_projects\domains\formulacion\myserver\stage\_appsdir_formulacion
    _ear\formulacionEJB.jar from formulacionEJB.jar:
    java.lang.NullPointerException
    at
    weblogic.ejb20.deployer.SessionBeanInfoImpl.assignDefaultTXAttributesIfNeces
    sary(SessionBeanInfoImpl.java:291)
    at
    weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeTransactionAttribu
    te(MBeanDeploymentInfoImpl.java:807)
    at
    weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoIm
    pl.java:240)
    at weblogic.ejb20.deployer.EJBDeployer.prepare(EJBDeployer.java:1262)
    at weblogic.ejb20.deployer.EJBModule.prepare(EJBModule.java:477)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModule(J2EEApplicationContaine
    r.java:2962)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepareModules(J2EEApplicationContain
    er.java:1534)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java
    :1188)
    at
    weblogic.j2ee.J2EEApplicationContainer.prepare(J2EEApplicationContainer.java
    :1031)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepare
    Container(SlaveDeployer.java:2602)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer(
    SlaveDeployer.java:2552)
    at
    weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare(SlaveDep
    loyer.java:2474)
    at
    weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeplo
    yer.java:798)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(SlaveDeployer.ja
    va:507)
    at
    weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.j
    ava:465)
    at
    weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.ja
    va:25)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
    Do you have any idea of why is this happening?
    Thanks in advance,
    Alejandro Escalante Medina

    Im having what appears to be the same exact problem (Im getting a NPE and same error message). Did this get resolved? Im using xdoclet as well ... Here are the respective deployment descriptors that are getting created via xdoclet ...
    Thanks,
    Scott :)
    ejb-jar.xml:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
    <ejb-jar >
    <description><![CDATA[No Description.]]></description>
    <display-name>Generated by XDoclet</display-name>
    <enterprise-beans>
    <!-- Session Beans -->
    <session >
    <description><![CDATA[AdministrationManager EJB]]></description>
    <display-name>AdministrationManager</display-name>
    <ejb-name>AdministrationManager</ejb-name>
    <home>com.jnj.depuy.wwl.ejb.administrationmanager.AdministrationManagerHome</home>
    <remote>com.jnj.depuy.wwl.ejb.administrationmanager.AdministrationManager</remote>
    <local-home>com.jnj.depuy.wwl.ejb.administrationmanager.AdministrationManagerLocalHome</local-home>
    <local>com.jnj.depuy.wwl.ejb.administrationmanager.AdministrationManagerLocal</local>
    <ejb-class>com.jnj.depuy.wwl.ejb.administrationmanager.AdministrationManagerSession</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    <session >
    <description><![CDATA[SequenceManager EJB]]></description>
    <display-name>SequenceManager</display-name>
    <ejb-name>SequenceManager</ejb-name>
    <home>com.jnj.depuy.wwl.ejb.sequencemanager.SequenceManagerHome</home>
    <remote>com.jnj.depuy.wwl.ejb.sequencemanager.SequenceManager</remote>
    <local-home>com.jnj.depuy.wwl.ejb.sequencemanager.SequenceManagerLocalHome</local-home>
    <local>com.jnj.depuy.wwl.ejb.sequencemanager.SequenceManagerLocal</local>
    <ejb-class>com.jnj.depuy.wwl.ejb.sequencemanager.SequenceManagerSession</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    <!--
    To add session beans that you have deployment descriptor info for, add
    a file to your XDoclet merge directory called session-beans.xml that contains
    the <session></session> markup for those beans.
    -->
    <!-- Entity Beans -->
    <!--
    To add entity beans that you have deployment descriptor info for, add
    a file to your XDoclet merge directory called entity-beans.xml that contains
    the <entity></entity> markup for those beans.
    -->
    <!-- Message Driven Beans -->
    <!--
    To add message driven beans that you have deployment descriptor info for, add
    a file to your XDoclet merge directory called message-driven-beans.xml that contains
    the <message-driven></message-driven> markup for those beans.
    -->
    </enterprise-beans>
    <!-- Relationships -->
    <!-- Assembly Descriptor -->
    <assembly-descriptor >
    <!--
    To add additional assembly descriptor info here, add a file to your
    XDoclet merge directory called assembly-descriptor.xml that contains
    the <assembly-descriptor></assembly-descriptor> markup.
    -->
    <!-- finder permissions -->
    <!-- finder permissions -->
    <!-- transactions -->
    <!-- finder transactions -->
    </assembly-descriptor>
    </ejb-jar>
    weblogic-ejb-jar.xml:
    <!DOCTYPE weblogic-ejb-jar PUBLIC '-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN' 'http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd'>
    <!-- Generated XML! -->
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>AdministrationManager</ejb-name>
    <stateless-session-descriptor>
    <pool>
    </pool>
    <stateless-clustering>
    </stateless-clustering>
    </stateless-session-descriptor>
    <transaction-descriptor>
    </transaction-descriptor>
    <jndi-name>AdministrationManager</jndi-name>
    </weblogic-enterprise-bean>
    <weblogic-enterprise-bean>
    <ejb-name>SequenceManager</ejb-name>
    <stateless-session-descriptor>
    <pool>
    </pool>
    <stateless-clustering>
    </stateless-clustering>
    </stateless-session-descriptor>
    <transaction-descriptor>
    </transaction-descriptor>
    <jndi-name>SequenceManager</jndi-name>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    And for reference the error:
    BUILD FAILED
    file:C:/My Sources/WWL/wwlear/build.xml:201: weblogic.utils.compiler.ToolFailureException: [J2EE:160119]Appc is unable to process the file 'C:\My Buil
    java.lang.NullPointerException
    at weblogic.ejb20.deployer.SessionBeanInfoImpl.assignDefaultTXAttributesIfNecessary(SessionBeanInfoImpl.java:291)
    at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeTransactionAttribute(MBeanDeploymentInfoImpl.java:807)
    at weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymentInfoImpl.java:240)
    at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:155)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:415)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:387)
    at weblogic.appc.compileEJB(appc.java:802)
    at weblogic.appc.compileModules(appc.java:621)
    at weblogic.appc.compileEAR(appc.java:733)
    at weblogic.appc.compileInput(appc.java:458)
    at weblogic.appc.runBody(appc.java:184)
    at weblogic.utils.compiler.Tool.run(Tool.java:146)
    at weblogic.utils.compiler.Tool.run(Tool.java:103)
    at weblogic.appc.main(appc.java:1028)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at weblogic.ant.taskdefs.j2ee.CompilerTask.invokeMain(CompilerTask.java:278)
    at weblogic.ant.taskdefs.j2ee.Appc.execute(Appc.java:179)
    at org.apache.tools.ant.Task.perform(Task.java:341)
    at org.apache.tools.ant.Target.execute(Target.java:309)
    at org.apache.tools.ant.Target.performTasks(Target.java:336)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
    at org.apache.tools.ant.Main.runBuild(Main.java:609)
    at org.apache.tools.ant.Main.start(Main.java:196)
    at org.apache.tools.ant.Main.main(Main.java:235)
    at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java:164)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:415)
    at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java:387)
    at weblogic.appc.compileEJB(appc.java:802)
    at weblogic.appc.compileModules(appc.java:621)
    at weblogic.appc.compileEAR(appc.java:733)
    at weblogic.appc.compileInput(appc.java:458)
    at weblogic.appc.runBody(appc.java:184)
    at weblogic.utils.compiler.Tool.run(Tool.java:146)
    at weblogic.utils.compiler.Tool.run(Tool.java:103)
    at weblogic.appc.main(appc.java:1028)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:324)
    at weblogic.ant.taskdefs.j2ee.CompilerTask.invokeMain(CompilerTask.java:278)
    at weblogic.ant.taskdefs.j2ee.Appc.execute(Appc.java:179)
    at org.apache.tools.ant.Task.perform(Task.java:341)
    at org.apache.tools.ant.Target.execute(Target.java:309)
    at org.apache.tools.ant.Target.performTasks(Target.java:336)
    at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
    at org.apache.tools.ant.Project.executeTargets(Project.java:1255)
    at org.apache.tools.ant.Main.runBuild(Main.java:609)
    at org.apache.tools.ant.Main.start(Main.java:196)
    at org.apache.tools.ant.Main.main(Main.java:235)

  • Changing / Setting Namespace Prefix in SAX

    I am using sax to parse a document and I was wondering how I could change an existing namespace prefix or add one to the front of every element. I am using an XML standard called PIDX which requires each element to look like this "<pidx:ELEMENTNAME>". I know this should not be required but the standard requires it. I am familiar with using the startElement and endElment methods but I am not sure how to set a prefix. Any help or examples would be appreciated.

    I recognize all of the words in the item you posted, but when I tried to parse the whole message, I got nothing.
    If you are using SAX to parse a document, it is just telling you what it sees by calling the various SAX methods like startElement, etc. If the XML document should have namespaces for all elements and it doesn't, it is not the fault of SAX, but of the program that created the XML data. So, you cannot set a prefix in SAX. You can be told by SAX that it saw a prefix, and by not seeing a call, you can tell that there was no prefix.
    How is the XML data generated? That is where you should first be concerned.
    In this case, SAX is just the messenger telling you what is in the XML data.
    Dave Patterson

  • Deploy nexus1000v on HP C7000 Virtual Connect

    Today i have a problem , i should deploy a N1KV on my enclosure c7000 with virtual Connect,
    I have 3 Clusters : 
    1 cluster : 2  X ESX 5.5  Management  
    1 Cluster :  1 X ESX 5.5  PCA/PRA
    1 Cluster : 2 X ESX 5.5 Production 
    The first cluster Management hosting N1KV VSM 
    Each cluster on management have one vmnic 
    Each cluster on Production have two vmnic
    After have deploy my N1KV and add host's cluster production , I wanted to test a vmkping with vmkernel, my vmkernel is attached on port-group which is associated with vlan 1. My ping test is not successful, and i have another problem i succeed to deploy a VEM on one of my two ESXI 5.5 on attached cluster. I repeat this same process but my second VEM doesnt see this VSM after having enter the command :
    N1KV# show module vem
    Mod  Ports  Module-Type                       Model               Status
    3    332    Virtual Ethernet Module           NA                  ok
    Mod  Sw                  Hw
    3    4.2(1)SV2(2.2)      VMware ESXi 5.5.0 Releasebuild-1623387 (3.2)
    Mod  Server-IP        Server-UUID                           Server-Name
    3    10.13.2.192      34303437-3037-4742-3836-343353483358  10.13.2.220
    N1KV#
    I see only one module  and after i enter another command : 
    N1KV# show module vem missing
    Mod  Server-IP        Server-UUID                           Server-Name
    -    10.13.2.40       34343335-3239-435a-4a38-303430324739  NA
    N1KV#
    i can not success up my VEM another ESX.   As an attachment you find a config file my nexus1000v
    VLAN 1 : Network LAN  + Management
    VLAN 80 : Network Nexus Control & Packet N1KV
    VLAN 300 : Organisation vCloud Director
    VLAN 400 :  Organisation vCloud DIrector 2
    VLAN 500 :  Organisation vCloud DIrector 3
    VLAN 600 : Organisation vCloud DIrector 4
    Thanks you for your help
    Best Regard,
    Mikael Lelouch

    Hi Ashley,
    Is the HP server on the Nexus connected via 1G or 10G? I would be interested to see the pause counters on the server interface and the c7000 interfaces. Could you attach the appropriate 'show interface' outputs?
    Thanks,
    Carlo 

  • Deployment failing to staging when try to change sku price

    I've just upgraded my env from ATG 10.1.2 to 10.2 and testing a deployment in BCC. Here's what I'm trying to do:
    1. Create a new merchandising project from an existing sku
    2. Go to the pricelist tab and change prices for the given sku, save, ready for staging deployment.
    3. While trying deploying to staging i'm getting the below error
    /atg/deployment/DeploymentManager       Required property priceList on item descriptor price is null. Searched for p2480135 on item descriptor priceList. Setting on item p2480135
    /atg/deployment/DeploymentManager        item = repositoryMarker:mark53100018 cause = CONTAINER:atg.deployment.DistributedDeploymentException; SOURCE:java.lang.IllegalArgumentException: Attempt to set property named priceList (PriceLists_staging:Price:p2480135)  with value = null (class=null).  A null value is not allowed for a required property.
    /atg/deployment/DeploymentManager               at atg.deployment.repository.RepositoryWorkerThread.processMarkerForReferenceUpdatePhase(RepositoryWorkerThread.java:374)
    /atg/deployment/DeploymentManager               at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:568)
    /atg/deployment/DeploymentManager               at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:335)
    /atg/deployment/DeploymentManager        message = Deployment Failed time = Thu Jan 23 14:25:53 PST 2014  atg.deployment.DeploymentFailure@1896dc9      CONTAINER:atg.deployment.DistributedDeploymentException; SOURCE:java.lang.IllegalArgumentException: Attempt to set property named priceList (PriceLists_staging:Price:p2480135)  with value = null (class=null).  A null value is not allowed for a required property.
    /atg/deployment/DeploymentManager               at atg.deployment.repository.RepositoryWorkerThread.processMarkerForReferenceUpdatePhase(RepositoryWorkerThread.java:374)
    /atg/deployment/DeploymentManager               at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:568)
    /atg/deployment/DeploymentManager               at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:335)
    /atg/deployment/DeploymentManager       Caused by :java.lang.IllegalArgumentException: Attempt to set property named priceList (PriceLists_staging:Price:p2480135)  with value = null (class=null).  A null value is not allowed for a required property.
    /atg/deployment/DeploymentManager               at atg.repository.RepositoryItemImpl.setPropertyValue(RepositoryItemImpl.java:233)
    /atg/deployment/DeploymentManager               at atg.adapter.gsa.GSAItem.setPropertyValue(GSAItem.java:1567)
    /atg/deployment/DeploymentManager               at atg.deployment.repository.RepositoryWorkerThread.copyRepositoryItemProperties(RepositoryWorkerThread.java:1277)
    /atg/deployment/DeploymentManager               at atg.deployment.repository.RepositoryWorkerThread.deployItem(RepositoryWorkerThread.java:1120)
    /atg/deployment/DeploymentManager               at atg.deployment.repository.RepositoryWorkerThread.processMarkerForReferenceUpdatePhase(RepositoryWorkerThread.java:362)
    /atg/deployment/DeploymentManager               at atg.deployment.DeploymentWorkerThread.processMarkerPhase(DeploymentWorkerThread.java:568)
    /atg/deployment/DeploymentManager               at atg.deployment.DeploymentWorkerThread.run(DeploymentWorkerThread.java:335)
    I turned on the debug logs on DeploymentManager and found that BCC is loading the price and pricelist for the given sku from the catalog, but while updating
    , its trying to set the pricelist attribute to null.
    debug logs:
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Processing repository item price:p2480135 for deployment 91000003-auto_rb in Add-Update Phase, action is Update Deploying from development line: 74613
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Source item NOT found in preloaded set of items (mBatchItems): PriceLists:price:p2480135
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Property priceList is required
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Property version is a version property, skipping copy for all items
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Property complexPrice is a reference, skipping copy in first pass
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Copying properties for item price:p2480135
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Setting required property to dummy item: priceList value: priceList:plist9070002
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Copying property: parentSkuId value: null
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Copying property: listPrice value: 584.99
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Copying property: pricingScheme value: listPrice
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Copying property: skuId value: sku6340066
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Copying property: productId value: null
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Processing repository item price:p1810001 for deployment 91000003-auto_rb in Add-Update Phase, action is Update Deploying from development line: 74613
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Source item NOT found in preloaded set of items (mBatchItems): PriceLists:price:p1810001
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Copying properties for item price:p1810001
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Setting required property to dummy item: priceList value: priceList:plist9070002
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Copying property: parentSkuId value: null
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Copying property: listPrice value: 649.99
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Copying property: pricingScheme value: listPrice
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Copying property: skuId value: sku6340066
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Copying property: productId value: null
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Processing repository item price:p2300061 for deployment 91000003-auto_rb in Add-Update Phase, action is Update Deploying from development line: 74613
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Source item NOT found in preloaded set of items (mBatchItems): PriceLists:price:p2300061
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Copying properties for item price:p2300061
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Setting required property to dummy item: priceList value: priceList:plist9070002
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Copying property: parentSkuId value: null
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Copying property: listPrice value: 829.99
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Copying property: pricingScheme value: listPrice
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Copying property: skuId value: sku7830115
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Copying property: productId value: null
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Committing 3 markers, 0 failed markers
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Done committing transaction
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Started new transaction
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Finished for loop, transaction status = 6
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Got 1 thread batch items for deployment: 91000003-auto_rb, owner: HVDIVD01WAB2168:8852, threadName: RepositoryWorkerThread-1(Add-Update Phase)
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Current high water mark: 3 Markers available: 3
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) No more markers available for processing
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Exiting normally
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Add-Update Phase) Active thread count is 0
    /atg/deployment/DeploymentManager       Main deployment thread:  Waiting for Add-Update Phase phase to complete for deployment 91000003-auto_rb, polling interval is 750 milliseconds.
    /atg/deployment/DeploymentManager       Main deployment thread:  All markers have been written for deployment 91000003-auto_rb. Checking for completion.
    /atg/deployment/DeploymentManager       Main deployment thread:  Checking for Add-Update Phase phase to complete for deployment 91000003-auto_rb. Markers remaining for commit: 0. Number of active threads is 1. ThreadCount is 0
    /atg/deployment/DeploymentManager       Main deployment thread:  Phase Add-Update Phase now complete for deployment 91000003-auto_rb
    /atg/deployment/DeploymentManager       Main deployment thread:  Add-Update Phase took 6 seconds
    /atg/deployment/DeploymentManager       Main deployment thread:  Changing phase for deployment 91000003-auto_rb to Reference Update Phase
    /atg/deployment/DeploymentManager       Main deployment thread:  Resetting high water marks for deployment 91000003-auto_rb
    /atg/deployment/DeploymentManager       Main deployment thread:  Set high water marks to 0 and updated item.
    /atg/deployment/DeploymentManager       Main deployment thread:  About to commit transaction for resetting high water marks
    /atg/deployment/DeploymentManager       Main deployment thread:  repository high water mark value: 0
    /atg/deployment/DeploymentManager       Main deployment thread:  file high water mark value: 0
    /atg/deployment/DeploymentManager       Main deployment thread:  Sending deployment message with status Reference Update Phase for deployment 91000003-auto_rb
    /atg/deployment/DeploymentManager       Main deployment thread:  Handling message with status=Reference Update Phase
    /atg/deployment/DeploymentManager       Main deployment thread:  Starting phase Reference Update Phase
    /atg/deployment/DeploymentManager       Main deployment thread:  Starting 1 repository worker threads for 3 repository items and 0 file worker threads for 0 files
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Reference Update Phase) Start deployment worker thread for repository items
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Reference Update Phase) Pushing development line snapshot:74613
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Reference Update Phase) Current high water mark: 0 Markers available: 3
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Reference Update Phase) New high water mark: 3
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Reference Update Phase) preparing to create thread batch
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Reference Update Phase) Creating thread batch item for deployment: 91000003-auto_rb, owner: HVDIVD01WAB2168:8852, threadName: RepositoryWorkerThread-1(Reference Update Phase)
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Reference Update Phase) Preloaded 3 items
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Reference Update Phase) Got 3 markers for processing [1 - 3]
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Reference Update Phase) Processing repository item price:p2480135 for deployment 91000003-auto_rb in Add-Update Phase, action is Update Deploying from development line: 74613
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Reference Update Phase) Source item NOT found in preloaded set of items (mBatchItems): PriceLists:price:p2480135
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Reference Update Phase) Property parentSkuId is not a reference, skipping copy in second pass
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Reference Update Phase) Property listPrice is not a reference, skipping copy in second pass
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Reference Update Phase) Property version is a version property, skipping copy for all items
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Reference Update Phase) Property pricingScheme is not a reference, skipping copy in second pass
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Reference Update Phase) Property skuId is not a reference, skipping copy in second pass
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Reference Update Phase) Property productId is not a reference, skipping copy in second pass
    /atg/deployment/DeploymentManager       RepositoryWorkerThread-1(Reference Update Phase) Copying properties for item price:p2480135
    /atg/deployment/DeploymentManager       Required property priceList on item descriptor price is null. Searched for p2480135 on item descriptor priceList. Setting on item p2480135
    Any help would be appreciated.
    Thanks!

    Try to boot with a live CD/DVD system and see if you don't have a hardware issue.
    If the machine worked for a couple of days and if it works sometimes, that seems a hardware problem to me.
    Last edited by berbae (2014-05-03 08:40:22)

  • Error in jboss while deploying

    12:49:57,181 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.2.1_tomcat-4.1.24/server/all/deploy/MyBank.jar
    12:49:57,692 WARN [verifier] EJB spec violation:
    Bean : MySession
    Section: 22.2
    Warning: The Bean Provider must specify the fully-qualified name of the Java class that implements the enterprise bean's business methods in the <ejb-class> element.
    Info : Class not found: au.com.tusc.MySessionSession

    Here are the files u needed
    ========================================
    MySessionHome
    * Generated by XDoclet - Do not edit!
    package au.com.tusc;
    * Home interface for MySession.
    * @lomboz generated
    public interface MySessionHome
    extends javax.ejb.EJBHome
    public static final String COMP_NAME="java:comp/env/ejb/MySession";
    public static final String JNDI_NAME="MySessionBean";
    public au.com.tusc.MySession create()
    throws javax.ejb.CreateException,java.rmi.RemoteException;
    =========================================
    MySession
    * Generated by XDoclet - Do not edit!
    package au.com.tusc;
    * Remote interface for MySession.
    * @lomboz generated
    public interface MySession
    extends javax.ejb.EJBObject
    public java.lang.String learnJ2EE( java.lang.String msg )
    throws java.rmi.RemoteException;
    =========================================
    MySessionLocalHome
    * Generated by XDoclet - Do not edit!
    package au.com.tusc;
    * Local home interface for MySession.
    * @lomboz generated
    public interface MySessionLocalHome
    extends javax.ejb.EJBLocalHome
    public static final String COMP_NAME="java:comp/env/ejb/MySessionLocal";
    public static final String JNDI_NAME="MySessionLocal";
    public au.com.tusc.MySessionLocal create()
    throws javax.ejb.CreateException;
    =========================================
    MySessionLocal
    * Generated by XDoclet - Do not edit!
    package au.com.tusc;
    * Local interface for MySession.
    * @lomboz generated
    public interface MySessionLocal
    extends javax.ejb.EJBLocalObject
    public java.lang.String learnJ2EE( java.lang.String msg ) ;
    =========================================
    MySessionSession
    * Generated by XDoclet - Do not edit!
    package au.com.tusc;
    * Session layer for MySession.
    * @lomboz generated
    public class MySessionSession
    extends au.com.tusc.MySessionBean
    implements javax.ejb.SessionBean
    public void ejbActivate()
    public void ejbPassivate()
    public void setSessionContext(javax.ejb.SessionContext ctx)
    public void unsetSessionContext()
    public void ejbRemove()
    public void ejbCreate() throws javax.ejb.CreateException
    =========================================
    MySessionUtil
    * Generated file - Do not edit!
    package au.com.tusc;
    * Utility class for MySession.
    * @lomboz generated
    public class MySessionUtil
    /** Cached remote home (EJBHome). Uses lazy loading to obtain its value (loaded by getHome() methods). */
    private static au.com.tusc.MySessionHome cachedRemoteHome = null;
    /** Cached local home (EJBLocalHome). Uses lazy loading to obtain its value (loaded by getLocalHome() methods). */
    private static au.com.tusc.MySessionLocalHome cachedLocalHome = null;
    // Home interface lookup methods
    * Obtain remote home interface from default initial context
    * @return Home interface for MySession. Lookup using COMP_NAME
    public static au.com.tusc.MySessionHome getHome() throws javax.naming.NamingException
    if (cachedRemoteHome == null) {
    // Obtain initial context
    javax.naming.InitialContext initialContext = new javax.naming.InitialContext();
    try {
    java.lang.Object objRef = initialContext.lookup(au.com.tusc.MySessionHome.COMP_NAME);
    cachedRemoteHome = (au.com.tusc.MySessionHome) javax.rmi.PortableRemoteObject.narrow(objRef, au.com.tusc.MySessionHome.class);
    } finally {
    initialContext.close();
    return cachedRemoteHome;
    * Obtain remote home interface from parameterised initial context
    * @param environment Parameters to use for creating initial context
    * @return Home interface for MySession. Lookup using COMP_NAME
    public static au.com.tusc.MySessionHome getHome( java.util.Hashtable environment ) throws javax.naming.NamingException
    // Obtain initial context
    javax.naming.InitialContext initialContext = new javax.naming.InitialContext(environment);
    try {
    java.lang.Object objRef = initialContext.lookup(au.com.tusc.MySessionHome.COMP_NAME);
    return (au.com.tusc.MySessionHome) javax.rmi.PortableRemoteObject.narrow(objRef, au.com.tusc.MySessionHome.class);
    } finally {
    initialContext.close();
    * Obtain local home interface from default initial context
    * @return Local home interface for MySession. Lookup using COMP_NAME
    public static au.com.tusc.MySessionLocalHome getLocalHome() throws javax.naming.NamingException
    // Local homes shouldn't be narrowed, as there is no RMI involved.
    if (cachedLocalHome == null) {
    // Obtain initial context
    javax.naming.InitialContext initialContext = new javax.naming.InitialContext();
    try {
    cachedLocalHome = (au.com.tusc.MySessionLocalHome) initialContext.lookup(au.com.tusc.MySessionLocalHome.COMP_NAME);
    } finally {
    initialContext.close();
    return cachedLocalHome;
    /** Cached per JVM server IP. */
    private static String hexServerIP = null;
    // initialise the secure random instance
    private static final java.security.SecureRandom seeder = new java.security.SecureRandom();
    * A 32 byte GUID generator (Globally Unique ID). These artificial keys SHOULD <strong>NOT </strong> be seen by the user,
    * not even touched by the DBA but with very rare exceptions, just manipulated by the database and the programs.
    * Usage: Add an id field (type java.lang.String) to your EJB, and add setId(XXXUtil.generateGUID(this)); to the ejbCreate method.
    public static final String generateGUID(Object o) {
    StringBuffer tmpBuffer = new StringBuffer(16);
    if (hexServerIP == null) {
    java.net.InetAddress localInetAddress = null;
    try {
    // get the inet address
    localInetAddress = java.net.InetAddress.getLocalHost();
    catch (java.net.UnknownHostException uhe) {
    System.err.println("MySessionUtil: Could not get the local IP address using InetAddress.getLocalHost()!");
    // todo: find better way to get around this...
    uhe.printStackTrace();
    return null;
    byte serverIP[] = localInetAddress.getAddress();
    hexServerIP = hexFormat(getInt(serverIP), 8);
    String hashcode = hexFormat(System.identityHashCode(o), 8);
    tmpBuffer.append(hexServerIP);
    tmpBuffer.append(hashcode);
    long timeNow = System.currentTimeMillis();
    int timeLow = (int)timeNow & 0xFFFFFFFF;
    int node = seeder.nextInt();
    StringBuffer guid = new StringBuffer(32);
    guid.append(hexFormat(timeLow, 8));
    guid.append(tmpBuffer.toString());
    guid.append(hexFormat(node, 8));
    return guid.toString();
    private static int getInt(byte bytes[]) {
    int i = 0;
    int j = 24;
    for (int k = 0; j >= 0; k++) {
    int l = bytes[k] & 0xff;
    i += l << j;
    j -= 8;
    return i;
    private static String hexFormat(int i, int j) {
    String s = Integer.toHexString(i);
    return padHex(s, j) + s;
    private static String padHex(String s, int i) {
    StringBuffer tmpBuffer = new StringBuffer();
    if (s.length() < i) {
    for (int j = 0; j < i - s.length(); j++) {
    tmpBuffer.append('0');
    return tmpBuffer.toString();
    =========================================
    ejb-jar.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
    <ejb-jar >
    <description><![CDATA[No Description.]]></description>
    <display-name>Generated by XDoclet</display-name>
    <enterprise-beans>
    <!-- Session Beans -->
    <session >
    <description><![CDATA[]]></description>
    <ejb-name>MySession</ejb-name>
    <home>au.com.tusc.MySessionHome</home>
    <remote>au.com.tusc.MySession</remote>
    <local-home>au.com.tusc.MySessionLocalHome</local-home>
    <local>au.com.tusc.MySessionLocal</local>
    <ejb-class>au.com.tusc.MySessionSession</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    <!--
    To add session beans that you have deployment descriptor info for, add
    a file to your XDoclet merge directory called session-beans.xml that contains
    the <session></session> markup for those beans.
    -->
    <!-- Entity Beans -->
    <!--
    To add entity beans that you have deployment descriptor info for, add
    a file to your XDoclet merge directory called entity-beans.xml that contains
    the <entity></entity> markup for those beans.
    -->
    <!-- Message Driven Beans -->
    <!--
    To add message driven beans that you have deployment descriptor info for, add
    a file to your XDoclet merge directory called message-driven-beans.xml that contains
    the <message-driven></message-driven> markup for those beans.
    -->
    </enterprise-beans>
    <!-- Relationships -->
    <!-- Assembly Descriptor -->
    <assembly-descriptor >
    <!--
    To add additional assembly descriptor info here, add a file to your
    XDoclet merge directory called assembly-descriptor.xml that contains
    the <assembly-descriptor></assembly-descriptor> markup.
    -->
    <!-- finder permissions -->
    <!-- transactions -->
    <!-- finder transactions -->
    </assembly-descriptor>
    </ejb-jar>
    =========================================
    jboss.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE jboss PUBLIC "-//JBoss//DTD JBOSS 3.0//EN" "http://www.jboss.org/j2ee/dtd/jboss_3_0.dtd">
    <jboss>
    <unauthenticated-principal>nobody</unauthenticated-principal>
    <enterprise-beans>
    <!--
    To add beans that you have deployment descriptor info for, add
    a file to your XDoclet merge directory called jboss-beans.xml that contains
    the <session></session>, <entity></entity> and <message-driven></message-driven>
    markup for those beans.
    -->
    <session>
    <ejb-name>MySession</ejb-name>
    <jndi-name>MySessionBean</jndi-name>
    <local-jndi-name>MySessionLocal</local-jndi-name>
    </session>
    </enterprise-beans>
    <resource-managers>
    </resource-managers>
    </jboss>
    =========================================

  • Error to do upgrade with Prime Collaboration Deployment

    Hi all,
    We need do a upgrade from CUCM 8.0 to 10.0
    We are migratin with the Prime Collaboration Deployment, but when we add the Esxi host, an error appear.
    "Failed to mount Cisco Prime Collaboration Deployments export as NFS store to the ESXi Host"
    The UCS is a UCS 240.
    We can discover the cluster old, but don´t cant add the Esxi host.
    We deploy the new VM for the new CUCM 10.0
    Please, I need your help.
    Thanks
    Guillermo

    Most likely you don't have the right ESXi license for this, you need at least FND for PCD
    Page 11
    http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/ucmap/10_0_1/CUCM_BK_U9C58CB1_00_ucmap-administration-guide.pdf
    If you don't meet the ESXi license requirements, nothing to do here, either buy the necessary license, or don't use PCD.

  • Add-On packaging

    I have created some forms in asp.net for sap b one.I want to deploy i.e create add on for these forms.I tried running AddOnRegDataGen.exe.But what are the addon exe,installer exe and uninstaller exe ?I have created windows application.How can I create add-on this application ?

    Hello,
    Steps for addon creation are :
    1. Develop the addon
    2. Compile the addon
    3. develop uninstall code and compile it.
    4. Creating installer file using VISE or other, you could download from internet or SDK forum
    5. When creating installer, there are some *.dll file that copied from client folder (B1_SHR) folder, like addoninstall.dll or another I could not remember. You must also include the uninstall.exe file.
    6. You use installer file and addon.exe file (compilation from step 2) when creating addon registration file (Extension is *.ard).
    So, addon.exe is from step 2, installer.exe is fromstep 5 and uninstaller exe is from step 5.
    Rgds,

  • Deploying an Acrobat addin for Acrobat 7 and 8

    Hi,
    Is there an elegant / standard way of deploying a custom addin for use with either Acrobat 7 or 8. Technically, the addin we have written will work for both versions of Acrobat.
    As I understand it, we just need to deploy to the correct add-in folder depending on the version of Acrobat installed. We are looking to install the addin via and MSI and Marimba.
    Is there an environment variable for the addin path. We would like to avoid deploying to both paths, or having multiple packages (one for each adobe version).
    Thanks.

    For Acrobat 6.0+ you can use:
    [HKLM\SOFTWARE\Adobe\Adobe Acrobat\X.0\InstallPath]
    (Default)="C:\Program Files\Adobe\Acrobat X.0\Acrobat"
    Replace X with the major version you are looking for. There may be multiple versions listed (my system has 7.0, 8.0 and 9.0 because I have had, at some point, each of those versions installed) but the InstallPath key will only exist for the currently installed version.

  • Deployment missing DLL

    OK, I'll ask.  What are we doing wrong in our deployments?
    We do use a custom model that leverages xml files for....many things.
    Steps to reproduce:
    Deploy a Workspace that dependeds on xml for a workspace that contains a Lvproj that does not use DOMuserDefRef.dll (Athough the model does) and all vi's that use xml are broken.  Not the vi's in the workspace lvproj.   The model custom vi's, including those in vi.lib!
    Add Dummy.vi to open and close a xml file to the LabVIEW project and the vi.lib vi's are no longer broken... but the model vi's are!  The deployment still fails.
    Add the Dummy.vi to the TS Workspace, the Dummy.vi and the model.vis are broken.
    Add Step.DummyAction to MainSequence with a call to Dummy.vi (do not report) all is well........
    I really would like an explaination of what we could do better.
    Jeff

    Norbert_B wrote:
    Jeff,
    i don't know if this is connected by any means, but there is some coincidence.
    Does it help?
    Norbert
    Not really, I have a work-around.  So, for right now I good (Meaning it only took 3 man days to deploy what should have work the first time )
    Does it help NI to resolve the issue?
    "Jinkies! a clue." - Velma Dinkley
    Jeff

Maybe you are looking for