Hybris system update using dump configuration - sap-commerce-cloud

After the recent hybris patch upgrade in Hybris 2011 there is no option for system update in hac.
Followed the below steps:
-generating the json structure using dump configuration and then doing a base64 encoding .
-Added the properties mentioned in the SAP documentation.
-Did migrate Data in CCV2 portal.
However the impexes added the custom patches extensions are not executed.
Can anybody help with detailed steps for patch update in ccv2 portal.

Related

Azure DevOps: Can no longer see Extensions in Project Settings

Noticed that Azure DevOps is no longer showing the menu options in Project Settings for the Extensions.
Does anyone else see this or know why?
I am unable to update settings for the installed extensions.
You can manage the installed extensions in the Organization settings.
Go organization settings--> Extensions under General. See document here for more information.
I have seen the same thing, and it only occurred recently. Yes, the org level extension management is still there, and that only allows for managing which extensions are available to use.
The configuration for the extension usage within each project was a separate section in the project settings - this is missing entirely. We have need to modify one of our extension configs and can no longer access it to do so.
I believe this must be an Error of type PEBKAC coming from a recent MS update to DevOps.

SharePoint 2016 - Copying content DB from Prod to Dev

I tried to copy the content DB from Prod to Dev server for the first time in my SP 2016 environment. Both the environments build versions are same (16.0.4705.1000). However in the prod under "Manage Patch Status" I see one extra Feature Pack 2 patch (16.0.4588.1001).
https://support.microsoft.com/en-us/help/4011127/descriptionofthesecurityupdateforsharepointserver2016september12-2017
Now when I am doing Mount-SPContentDatabase, I get the following error.
Mount-SPContentDatabase : An extension defined in the database is not registered with the farm.
In the ULS I see the following information. It says the project server database extensions are missing.
Following are my questions,
Is this because I have installed Feature Pack 2(link above) in Prod which has security updates for Project server? We don't have project server enabled in either of the environments.
Can I install the Feature Pack 2 in Dev now even though it has higher security update already installed? Isn't the later patch includes everything that was released in the previous patches?
This is just for my understanding. In the manage patch status why does the Install Status for feature pack 2 shows as "Superseded" even though I have other later patches?
Tried Restore-SPsite as well but getting error "The extension set does not match."
Had the same problem during the migration from 2016 -> 2019.
My solution:
Register the missing extension https://techcommunity.microsoft.com/t5/sharepoint-support-blog/upgrading-a-content-db-from-sharepoint-2016-to-sharepoint-2019/ba-p/1374209 (look at the bottom of the post)
remount the contentDB
Required code to perform the registration in step 1:
Check extensions in old farm
$contentservice=[Microsoft.sharepoint.Administration.SPwebservice]::ContentService
$contentservice.RegisteredDatabaseExtensionTypes >> SP2016Farm_registered_Extn.txt
Check extensions in new farm
$contentservice=[Microsoft.sharepoint.Administration.SPwebservice]::ContentService
$contentservice.RegisteredDatabaseExtensionTypes >>SP2019Farm_registered_Extn.txt
Register missing extension in new farm
$svc = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.Office.Project.Server.Database.Extension") | FL
$svc.RegisteredDatabaseExtensionTypes.EnsureAdded([Microsoft.Office.Project.Server.Database.Extension.ProjectDatabaseExtension])
$svc.Update($true)
In my case i did the steps below before i have registered the missing extension, but i think/hope there is no need to do that.
Powershell: Enable-ProjectServerLicense (Trail License)
Check running Sharepoint CA > ProjectServer Service
Check/create Sharepoint CA > ProjectServer Application

Hybris Backoffice Data Hub Build Failed

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".

Is there a tutorial that explains how the sandbox completes the 'source' with the sdk and executable code?

New guy here. I walked through the 'Cassandra data analytics demo' in the sandbox and was up and running in no time (using the recommended hardware, Raspberry Pi and DHT11 sensor).
Now I want to take it to the next step. I installed an instance of Kaa (not the sandbox anymore) and followed the same tutorial which explained setting up the schemas and log appenders etc (https://www.youtube.com/watch?v=VHwJLHQjl50) and exported the sdk to the Raspberry Pi. The issue I'm running into is understanding exactly what all was done for me in the sandbox, for instance, all of these steps performed when I click "Source":
Assembling sources for 'Cassandra data analytics demo' project... SDK
profile id of project: 10 Getting SDK for requested project...
Successfuly got SDK. Processing project archive...
CCassandraDataAnalyticsDemo/ CCassandraDataAnalyticsDemo/src/
CCassandraDataAnalyticsDemo/src/dht11/
CCassandraDataAnalyticsDemo/CMakeLists.txt
CCassandraDataAnalyticsDemo/src/dht11/dht11.h
CCassandraDataAnalyticsDemo/src/dht11/dht11.c
CCassandraDataAnalyticsDemo/src/kaa_demo.c
CCassandraDataAnalyticsDemo/build.sh Compressing source project
archive... CCassandraDataAnalyticsDemo/
CCassandraDataAnalyticsDemo/libs/
CCassandraDataAnalyticsDemo/libs/kaa/
CCassandraDataAnalyticsDemo/libs/kaa/kaa-c-ep-sdk-wcknkllgn6TIg3OjUlumWqcZSCw.tar.gz
CCassandraDataAnalyticsDemo/src/
CCassandraDataAnalyticsDemo/src/dht11/
CCassandraDataAnalyticsDemo/src/dht11/dht11.c
CCassandraDataAnalyticsDemo/src/dht11/dht11.h
CCassandraDataAnalyticsDemo/src/kaa_demo.c
CCassandraDataAnalyticsDemo/CMakeLists.txt
CCassandraDataAnalyticsDemo/build.sh Source project archive
compressed. Succesfully prepared project data!
-------- CLICK OK TO START DOWNLOAD PROJECT SOURCES --------
Finished!
My question is, once I download the c-sdk from my instance of kaa (not the sandbox), moved it to the Raspberry Pi and built it, what do I need to do, or what glue code is required to get the Pi to start logging a sensor's data and reporting back to my instance?
There is no tutorial that explains how the sandbox completes the 'source' with the SDK and executable code.
Kaa Sandbox is a preconfigured virtual environment designed for the users who want to use their private instance of Kaa platform for educational, development, and proof-of-concept purposes.
The Sandbox also includes a selection of demo applications that illustrate various aspects of the platform functionality.
When you click "Source", you got sample project with generated SDK for specified platform and language. See your first Kaa application guide for details.
For example, if you want to run the 'Cassandra data analytics demo' without the Kaa Sandbox, you should do the next:
Create an application.
Add this log schema (you can use Upload from file at Add log schema window in Kaa Admin Console).
Add "sensor_per_row", "sensor_per_date" and "sensor_per_region" log appenders using configuration from corresponding sensor_per_*_cassandra_appender.json located here
(you can use Upload from file at Add log appender window in Kaa Admin Console).
Download "c" folder from here.
Create folders "libs/kaa" (project files structure as in downloaded Cassandra data analytics demo from the Kaa Sandbox).
Add SDK profile for your application.
Generate SDK for C target platform.
Save SDK into the libs/kaa folder.
Follow the installation steps for Cassandra data analytics demo from Sandbox to run client application (for now you don't need to download the source code by clicking the "Source" button).

How do I migrate from TFS to Visual Studio Online using the OpsHub Utility?

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.

Resources