Im trying to install Backoffice Data Hub into my existing Hybris 6.2. I followed the steps described in hybris help An error described in the the attached pic during the build :ant clean all
here is also in attached the updated
BUILD ERROR:
localextensionss.xml:
The problem might be caused by the fact that your file is named "localextensionss.xml"(there is one extra "s" at the end) instead of "localextensions.xml".
Related
Following the tutorials listed in https://github.com/HyperledgerHandsOn/trade-network, I was able to create a trade network and connect to it. However, after a VS code restart, all the created FAbric environments and wallets disappeared. Additionally, I am unable to recreate them.
Upon trying to manually add the Fabric environments/wallets am trying to add a new Fabric environment the "+" sign does not works (unresponsive) nor does an option appear after right clicks.
Tried giving the extension a reinstall but no luck:-
Additionally, I see weird errors when trying to run the extension commands on VS code pallet - for example this is what I see when I run a "View Prerequisite" command -
I was able to solve this problem by downgrading the version. Looks like this is an error with version 2.0.4.
Getting the following error in my apllication.
i am integrated Liferay and Pentaho with CAS for single sign on
Unable to start blueprint container for bundle pdi-dataservice-server-plugin due to unresolved dependencies [(objectClass=org.pentaho.metaverse.api.ILineageClient)]
Plz help
try deleting data\cache* directories content under Karaf directory (which is somewhere under your application install path), I've red this indication here for another software and it worked for me in Pentaho Data Integration, maybe it will work for you too
Deleting data\cache* directories content under Karaf will solve the issue.
I am attempting to migrate to VSO from TFS and receiving the following errors:
I have administrative rights in both VSO and TFS.
Please help me figure out what the problem is.
Thank you!
Here you find answers to your all queries.
Administrative Right(s):
The OpsHub Visual Studio Online Migration Utility requires that the user that is used to create the Visual Studio Online End Point is a member of the Project Collection Administrator Group.
To grant the user that particular right, follow the following link.
http://www.opshub.com/ohrel/Resources/TFS/permissions.php?page=admin
Template Customization:
You are facing template customization error due to you have configured custom field(s) at your source end.
& such field(s) are not exist on your target VSO.
Solution for this is to delete the custom field(s) at your source end & revalidate again to processed further using migration utility. Migration on customized process templates are not supported through free utility.
You can revert customization incase you want to continue your migration with free utility with the help of following article.
http://msdn.microsoft.com/en-us/library/dd236909.aspx
You can use power tools for quick configuration of custom fields
http://visualstudiogallery.msdn.microsoft.com/f017b10c-02b4-4d6d-9845-58a06545627f
Missing Link Type(s) Warning:
You are seeing link type warning because your target VSO instance is not having Affects and Affected by link types. Still you can continue the migration with warning, in this case your Affects & Affected by link type(s) will migrated as “Related” link type.
Alternative solution is to create new project with CMMI template in your target end. This will automatically add the missing Affects & Affected By link type(s) in target VSO. After doing this revalidate again and proceed further without warning. You can remove newly created CMMI project once you are able to see Affects, Affected by link types in you project.
I am trying to create an instance using the Configuration Manager of WCS 7. I am working on a Win 7 x64 machine with DB2 9.5 64 bit version.
I am struck with this Massloading error when the instance creation happens :
In createInstanceANT.log file :
[Massload] Massloading
C:\IBM\WebSphere\CommerceServer\schema\xml\wcs.keys.xml Error in
MassLoading, please check logs for details.
The error log shows the following error :
[jcc][10165][10044][4.3.111] Invalid database URL syntax:
jdbc:db2://:0/WCSDEMO. ERRORCODE=-4461, SQLSTATE=42815
C:\IBM\WEBSPH~1\COMMER~2\config\DEPLOY~1\xml\createBaseSchema.xml:185:
Error in massloading
WCSDEMO is the database name. The Massloader is not able to get the URL and port to connect. It is supposedly getting them from createInstance.properties file but it is not working. The createInstance.properties file has all the details of the DB to connect.
What could be the reason for this error and how to resolve it ? Is there any configuration change that I am missing ?
Can you provide some more details.
look inside the messages.txt file located in WC_install_dir/instances/instance_name/logs
and confirm what the exact issue is. If it is related to jdbc driver being wrong I may be able to help you.
I've been running into massloading problems with external systems. Eg. databases not on the same machine as the WAS installation.
In these cases I look for the
As you can see setting the loaderDBName to just the name of the database would look on the local machine. But by changing this statement so you load with the syntax
loaderDBName=[DATABASE_SERVER_NAME]:[PORT]/[DATABASE_NAME]
You'll be able to massload using the commerce standard scripts. These changes needs to be done in many scripts. Both for updating fixpacks and enabling features. If you run database updates without the changes it will crash at first and have done all the schema changes to the database that you then need to comment out before trying again.
IBM Software Support is your friend. They'll help you fix it.
I am deploying my project from sandbox to production. And i am using "ANT" tool for deploying. But it is giving me error as given below:
Error: objects/Form__c.object(144,13):field integrity exception:
unknown (must specify either cascade delete or restrict delete for
required lookup foreign key)
Can anybody help me please.
Thanks,
Goto line no 144 of your object Form__c there will be a Lookup Field , in that field remove the 'Required' Tag , remove that tag completed and start your ant deploying again.
Sounds like an API version mismatch thing. If I recall correctly ability to reparent master-detail relationships and to mark lookups as required on DB level instead of layout level was introduced in summer'12. Your XML file is coming from sandbox without this feature so SF is complaining at the missing tags.
See release notes (pages 183-184), though they don't really mention the metadata changes...