#devguide | Explore Tumblr posts and blogs

enterinit · 6 years ago

Text

Windows Admin Center Preview 1908 released

Windows Admin Center Preview 1908 released. You’ll start to see visual changes in this version as minor style updates to the Windows Admin Center UI, including a new, rich, entry page to the add connection experience:

Other changes include: NEW TOOL! Packetmon: Packetmon is a new feature that will allow you to diagnose your server by capturing and displaying network traffic through the networking stack in a log that is filtered, organized, and easy to follow and manipulate. This release of Packetmon supports 19H1 and 19H2 builds. In later releases, Windows Server 2019 will be supported, the actual names of networking stack components will be displayed in the log, users will be able to filter the log by components & dropped packets, and users will be able to save captures to analyze and manipulate the captures whenever needed. NEW TOOL! FlowLog Audit: Flowlog auditing is a new capability for the SDN firewall in Windows Server 2019. When you enable SDN firewall, any flow processed by SDN firewall rules (ACLs) that have logging enabled gets recorded. These logs can be used for diagnostics or archived for later analysis. With the new “Flowlog Audit” extension in Windows Admin Center, you can easily manage, search and filter the SDN logs for analysis and diagnostics. It can be difficult to gain insights into flow logging data by manually searching the log files. In this extension, you can also upload the log to Azure Blob, then use Power BI to visualize your most recent flow logs and learn about traffic on your network.

UPDATED TOOL! Security: Install or update the Security tool from the extension feed. This update features a full visual refresh with the ability to toggle real-time Windows Defender protection, run a quick scan, modify your scan schedule, view history and edit default remediation actions. Windows Admin Center can now onboard Failover Cluster and Hyper-Converged Cluster connections to Azure Monitor: To configure Azure Monitor for your cluster, navigate to Settings -> Monitoring Alerts. The onboarding process will help set up the log analytics workspace in Azure and install the appropriate local agents on each server in your cluster to help you collect events and performance counters for analysis, reporting, and alerting. Windows Admin Center extension developers: The Active Directory search that was originally implemented for adding servers is now a reusable control – the link to the example is: https://localhost:6516/devguide/tools/active-directory-search-control WinRM over HTTPS: Supporting WinRM over HTTPS (port 5986) is a top user request. Starting in this version of Windows Admin Center, you will have the option to choose WinRM over HTTPS (port 5986) as the method of connection to your managed nodes.

Known issues

Azure Monitor onboarding – If you’re managing a server or a cluster using “manage as” credentials, the onboarding may fail.Network – If you have configured an Azure Network Adapter, the value under Microsoft Azure Virtual Network Gateway Address will be formatted as a hyperlink but leads to an invalid address. Chrome users may see 403 Forbidden response from WAC after upgrading. The workaround is to close *all* open chrome tabs (make sure there are no chrome.exe processes running). After restarting chrome, everything will function normally. We have an error message that makes this clear, but chrome users with multiple windows admin center tabs open during upgrade will not see the message. Read the full article

#Windows #Windows10 #WindowsAdminCenter #WindowsServer #WindowsServer2012R2 #WindowsServer2016 #WindowsServer2019

0 notes

iwtrtech-blog · 6 years ago

Photo

Get 2 years of coding training with this $39 DevGuides subscription

0 notes

craigbrownphd-blog-blog · 7 years ago

Text

Boost your Cloud Foundry NodeJS Edit-Build-Test Speed!

So you’ve taken the dive into micro-services enterprise development, you’ve joined the church of the twelve-factor app and now you’ve got your SAP Cloud Foundry Cloud Platform account and are ready to burn away the cloud. You’re on the right path by following all the best practices and are using the multi-target application architecture to coordinate it all and have divided your monolithic enterprise app into a reasonable number of application modules. You crank up your trusty WebIDE and build and wait and deploy and wait and test and see an issue and start all over again. If you’ve got your application deployed into Cloud Foundry and you’re focusing your efforts on a couple of NodeJS modules, there is a much faster way. Use the cf ssh command to edit the already deployed files in CloudFoundry in order to quickly figure out what changes need to be made and then incorporate them back into your project. Currently the WebIDE will only support fully deployment of your whole application. Remember that each application module is in it’s own right a web server plus other logic for doing it’s work. So if you have four application modules and an app-router, you have to pull the dependencies for 5 web servers, build the mtar, deploy and test. If you’re only working on one module, that’s a lot of building and copying and running for nothing. Now you can take matters into your own hands and clone (you are using Git right) your project into a local directory and use cf push to deploy one module at a time but then you have to manage the attributes of how it gets pushed and any binding that may be required for the module to access the services it needs. When working with NodeJS modules in development (not production) the trick is to launch your NodeJS module with a module called nodemon instead of node as you normally would. Nodemon watches for file changes an reloads the server when it sees that something has changed. I’m going to demonstrate how to set all of this up using the HANA WebIDE found in HANA Express edition. The basic nuts and bolts can also be performed on your local workstation with the CF CLI and MTA plugin. The core of the technique I’m using here can be found at this cloud foundry docs page: https://docs.cloudfoundry.org/devguide/deploy-apps/ssh-apps.html#ssh-command I’m using a HANA Express (HXE) system that is hosted on AWS, but you should be able to do the same thing with HXE installed in a VM on your local workstation. I’ve can run it on my 16GB Macbook Pro under VMWare Fusion with 12GB, but it pretty much uses every bit of 12GB so this is for utilizing the tools and not doing large data-set testing. I’m going to use the HXE administrative user in these examples. You can use a different user, but since the files that drive the WebIDE are already owned by the hxeadm user, it makes for a simpler setup. Make sure you can ssh into your HXE server and become the hxeadm user. su - hxeadm Return to the root user and double check that you have the cf cli tool available and that it’s the current version. Here are the links to the installer and the MTA plugin that’s needed. CF CLI CloudFoundry CLI CF CLI MTA Plugin CloudFoundry CLI Plugin Page If you need help installing the plugin, look here: https://docs.cloudfoundry.org/cf-cli/use-cli-plugins.html#plugin-install cf install-plugin /tmp/cf-cli-mta-plugin-1.0.2-linux.bin Note that the plugin is installed for each user so if you change users, you’ll need to install the plugin again for that user. Double check that your cf cli version is what you expect and you’re not picking up an older version that might be lurking in your path. cf --version Also check that the plugins got installed correctly. cf plugins We need to make sure the hxeadm user is prepared for ssh connections. ls -al ~/.ssh If no files are seen, then generate new id files. ssh-keygen Generating public/private rsa key pair. Enter file in which to save the key (/usr/sap/HXE/home/.ssh/id_rsa): (blank for default) Enter passphrase (empty for no passphrase): (blank for no passphrase) Enter same passphrase again: (leave blank again) Your identification has been saved in /usr/sap/HXE/home/.ssh/id_rsa. Your public key has been saved in /usr/sap/HXE/home/.ssh/id_rsa.pub. The key fingerprint is: ... +----[SHA256]-----+ The WebIDE creates a directory on the server for each user that contains their projects in their workspace. Since the name of the directory is system generated, it’s best to discover it. Log into the WebIDE web interface and create a sample MTA project with a unique project name that will stand out. In this case we’ll use abcxyz. Since this is a HANA Express installation, we know that the xs files are located in /hana/shared/HXE/xs/ so change into that directory. cd /hana/shared/HXE/xs/ Now let’s look for that mta.yaml file starting at this directory. find . -name mta.yaml -print We see the long directory name with abcxyz in it. This is our workspace directory. Make a note of it. Change into it so that we can grab it’s full path. You’ll have to modify the specifics for your situation. cd ./controller_data/fss/625dcf6b-27d8-4323-b3cc-eff7bf02a40c/7a/0d/85/workspaceusr8phhempsj98re/ pwd Copy that full path into your clipboard. Then change back to the home directory of the hxeadm user. cd /usr/sap/HXE/HDB00/ Now to make things easier, create a symbolic link to your workspace in the hxeadm home directory. You will of course need to change the system generated values with the ones on your system. ln -s /hana/shared/HXE/xs/controller_data/fss/625dcf6b-27d8-4323-b3cc-eff7bf02a40c/7a/0d/85/workspaceusr8phhempsj98re workspace Change into it and look at the files. Should be the same as what you see in the WebIDE interface. Go ahead and delete this abcxyz project. It’s served it’s purpose for us. rm -rf abcxyz Now for grins, go back to the WebIDE web interface in your browser. Notice that it seems like the project is still there. It’s not. It’s just that we’re modifying the underlying files directly on the server. To put things back in sync with the WebIDE, perform a refresh from the Workspace level. It should disappear. From here we’re going to work with an existing simple NodeJS application called scp2cf. Clone the following project into your server. https://github.com/alundesap/mta_scp2cf.git This is a basic multi-target application with a single NodeJS module called monme and a supporting script. There is also a tmp folder with will be used to hold some temporary files in a bit. The only difference between this sample NodeJS application and the default one is that I’ve included a dependency for a module called nodemon and I’ve replace node in the start command with nodemon. This allows the server.js (or any other file that your server relies on) to be modified and automatically reloaded when a change is detected. Build your project by right-clicking on the project level and selecting Build. This creates a .mtar file in the Deploy your .mtar to Cloud Foundry by right-clicking on it and picking Deploy > To Cloud Foundry. Enter your Cloud Foundry API endpoint URL: https://api.cf.us10.hana.ondemand.com and hit tab. You have to wait for a while for the system to get your orgs and spaces. If needed you’ll be asked to authenticate. This is the SAP-ID username and SAP-ID password. Watch the console for any issues during deploy. If it fails you can use the following cf commands. cf mta-ops cf deploy -i ### -a monitor cf dmol You may find that you have to abort a failed deploy and cf undeploy it and try again. Check your running apps. cf a OK, now that we know our app is running, let’s figure out how to ssh into it’s container. Check that the space in CF is enabled for SSH. cf space-ssh-allowed If it’s not then have your space’s Manager enable it for your. cf allow-space-ssh Find your app’s url by displaying it’s details. routes: cf app monme Open your application in a browser and check that it’s working. https://a-team-shared-dev-monme.cfapps.us10.hana.ondemand.com/ You should see this: If you wanted to make a change, you’d have to go back to the WebIDE, edit the file, rebuild the mtar file, redeploy it, hope nothing bad happened, and then test it again. This can take a significant amount of time and as your multi-target application get larger, the time gets longer. But there is a better way. You can ssh into your application module’s container and manipulate the files directly after they are deployed. To do this continue on. You’ll need to get ssh’d into your server and start using the cf cli. Check that the application is enabled for SSH cf ssh-enabled monme If it’s not then enable it. cf enable-ssh monme IMPORTANT!!! You won’t be able to ssh into your application until to restage it. cf restage monme Now. Test that you can connect to the application with the cf ssh command. cf ssh monme You should get a prompt that starts with vcap@. If you do you’ve ssh’d into your application. You can perform a limited set of linux commands like, ls, pwd, cat, cd, and vi etc. You’ll find your application files in the app directory. cd app Since vi is available, you can use it to edit the server.js file and save it. Once you do so, NodeJS will be reloaded and you can browse to your application’s URL and see the change. Type exit to return to your system. This is a great time saver when you want to jump in and tweek a few files to make sure that things are working as you expect or experiment while using the live cloud foundry environment. You’ll want to have a ssh window open with the cf logs command running to keep an eye on what’s happening. Keep in mind that you’re changing files on the live cloud foundry environment. If you don’t make the same changes back in your WebIDE, they will be lost. In fact if you do something that causes the application to fail, the system will restart it with the last staged files and your latest changes will be lost. If you’d rather continue working on the file within the WebIDE, then there are things you can do to help facilitate this automatically. The cf ssh command is great, but what if you want to use the normal scp command to send modified files into cloud foundry? There is a way to do this but it’s a bit more complicated. Let’s ssh into the application container again but this time use the ssh command. First we need to know your applicaiton’s guid. cf app monme --guid I’ll continue to use mine in this example, but you’ll need to use yours. Ask your cloud foundry system for a special one-time-use password code for sshing in. cf ssh-code Now put the guid into this form of the ssh command. Alter the guid and cf region to match yours. ssh -p 2222 cf:8aa9f796-e53e-4564-b4e3-597e82d7c2e7/[email protected] When prompted for the password, use the string that cf ssh-code returned. > cf ssh-code CWgTh2ZmZH > ssh -p 2222 cf:8aa9f796-e53e-4564-b4e3-597e82d7c2e7/[email protected] cf:[email protected]'s password: CWgTh2ZmZH vcap@f576b9fe-b05a-47aa-589b-2489:~$ If this works for you, then you’re ready to try the scp version of the command. In order to facilitate this automatically, I’m using a linux program called expect and wrapping the details into a shell script called scp2cf2.sh. This script will need to read and write files to a local folder, so I’ve included one called tmp. Also, for reasons I’ll show shortly, I need to invoke this script from within the module’s source directory so there are several relative path specifiers involved. Change into the workspace folder as described above. cd workspace Change into the project mta_scp2cf. cd mta_scp2cf The script expects the guid of your application module to be in the file tmp/guid so do this. cf app monme --guid > tmp/guid Change into the monme module directory. cd monme Run the script from the parent directory like this. Specifying the file you want to copy to into your app running in cloud foundry. Notice I’m chaining 2 commands together with a “;”. cf ssh-code > ../tmp/code ; ../cp2cf2.sh server.js If you get permission denied, you’ll need to change the script’s permissions. chmod 755 ../cp2cf2.sh Re-run the command. cf ssh-code > ../tmp/code ; ../cp2cf2.sh server.js If all goes well, you should see scp’s progress bar and that the file is 100% transmitted. If you don’t then go over the steps above and verify each one and troubleshoot. Now go into the WebIDE and change the file server.js. I added “I’m changed.”. and save it. No go back to your ssh window and re-run the last command. server.js ssh.cf.us10.hana.ondemand.com:/home/vcap/app/server.js And reload your browser. Now you can edit files in the WebIDE and see the results pretty quickly. One last thing. You can take advantage of a linux command called inotifywait to automate this for you! I won’t get into the details, but if you run have inotify installed on your linux system you can paste this script into your ssh console and then all you have to do is to edit your files in the WebIDE and save them, then go reload the browser to test! Pretty handy. DIFF=0 LAST=0 inotifywait -re modify -m --exclude '/\..+' . | while read -r directory events filename; do echo "Events: $events" relpath=$directory$filename echo "RelPath: $relpath" NOW=$(date +%s) printf "%s\n" "$NOW" DIFF=$(($NOW - $LAST)) if [[ $DIFF -gt 10 ]]; then cf ssh-code > ../tmp/code ; ../cp2cf2.sh $relpath; else echo "Skip"; fi LAST=$NOW done Again, I’m doing this on a linux machine. MacOS and Windows has similar mechanisms if you want to use your local workstation and the cf cli tools. Another note is that while the cf ssh command should would with any language, each language and web server handles how it’s re-loaded differently so you’ll need to modify things for java or python or PHP accordingly but the same principal applies. I hope this saves someone out there a ton of time. http://bit.ly/2FGOoQ6 #SAP #SAPCloud #AI

0 notes

devopsengineer · 4 years ago

Text

Azure devops pull request trigger

Azure devops pull request trigger Azure devops pull request trigger Daily news Azure devops pull request trigger Azure DevOps Pull Request Templates Devguides Read more posts by this author. Devguides Pull requests are a very handy feature when you are working in a team. However, you might want to have a check list of some sort or maybe a special format on your pull requests. One way to…

View On WordPress

#Azure #devops #pull #request #trigger Azure devops pull request trigger

0 notes

italiacamerun · 5 years ago

Text

Cookie Policy

https://aedic.eu/cookie-policy/

Cookie Policy

Cosa sono i cookie

I cookie sono piccoli file di testo e numeri che vengono scaricati e registrati nella memoria del proprio browser quando viene visitato un sito web o utilizzato un social network attraverso computer, tablet, smartphone e su qualunque dispositivo utilizzato per navigare in Internet, in grado di memorizzare le informazioni di navigazione dell’utente e le sue preferenze.

I cookie svolgono diverse e importanti funzioni nell’ambito della rete (esecuzione di autenticazione informatiche, monitoraggio di sessione, memorizzazione di informazioni su specifiche configurazioni riguardanti gli utenti che accedono al server, memorizzazione delle preferenze, ecc.)Tecnicamente un cookie è una riga di testo, normalmente composta dal nome del server da cui il cookie è stato inviato, da un valore costituito generalmente da un numero generato a caso dal computer, dal dominio (URL di riferimento), data di creazione e scadenza.

Tipi di cookie

I cookies possono essere classificati:

sotto il profilo soggettivo in:

Cookies proprietari (o di prima parte)

cioè installati dallo stesso gestore del sito visitato.

Cookies di terze parti

nel caso il cookie sia installato da un sito diverso, per il tramite del sito visitato. a seconda della finalità:

Cookie tecnici (strettamente necessari)

sono quelli che consentono di navigare o di fornire un servizio richiesto dall’utente. Rientrano in questa categoria i cookie che riconoscono in automatico la lingua che l’utente utilizza, quelli che facilitano gli acquisti on line o quelli che rendono meno complessi e più sicure le procedure di home banking. Ai sensi della direttiva 2009/136/CE, recepita dal D.lgs. 28 maggio 2012 n. 69, e del provvedimento del Garante per la protezione dei dati personali relativo all’“Individuazione delle modalità semplificate per l’informativa e l’acquisizione del consenso per l’uso dei cookies” dell’8 maggio 2014, essendo i cookies tecnici essenziali per il corretto funzionamento di un sito web possono essere utilizzati anche senza il preventivo consenso dell’utente, fermo restando l’obbligo di informativa ai sensi dell’art. 13 del Codice privacy.

In base ai tempi di permanenza all’interno del dispositivo informatico in:

Cookies di sessione:

vengono rimossi quanto l’utente chiude il browser e che, pertanto, hanno una durata limitata alla tua visita;

Cookies permanenti:

che rimangono nel dispositivo utilizzato per navigare in Internet per un tempo determinato. Questi cookie hanno date di scadenza tipiche e, pertanto, la loro durata varia a seconda del cookie utilizzato.

Cookie analitici

Sono utilizzati per raccogliere informazioni in maniera aggregata di natura statistica (es. numero di visitatori del sito web, determinazione geografica). Sono righe di testo lasciate all’interno dei browser dal server del sito che l’utente sta visitando. Per semplificare, ogni volta che viene visitata una pagina, viene rilasciato un cookie che consente al gestore di tenere traccia degli articoli più letti, di quanto tempo si rimane su una pagina, ecc. I cookie analitici servono a monitorare l’uso del sito da parte degli utenti al fine di ottimizzazione dello stesso.

Un ulteriore distinzione necessaria per il rispetto degli adempimenti normativi ai sensi del provvedimento 8 maggio 2014 emesso dall’autorità Garante della privacy (doc. web. N.3118884) è tra:

Cookie analitici di prima parte:

possono essere assimilati ai cookie tecnici soltanto se utilizzati ai fini di ottimizzazione del sito direttamente dal titolare che potrà raccogliere informazioni in forma aggregata sul numero degli utenti e sulle loro modalità di utilizzo del sito. A queste condizioni il gestore del sito in quanto titolare del trattamento ha l’obbligo di segnalarli nell’informativa privacy (Privacy Policy) senza l’obbligo del consenso dell’interessato e della notificazione al Garante della privacy.

Cookie analitici di terze parti:

Il gestore del sito è soggetto agli obblighi del banner informativo e di consenso e della notificazione al garante salvo che non vengano adottati strumenti idonei a ridurne il potere identificativo (mascheramento di porzioni significative dell’indirizzo IP) e che la terza parte si impegni contrattualmente a non farne un uso ulteriore rispetto alla erogazione del servizio in favore del gestore del sito

Tipi di cookie che utilizziamo

Sono presenti nel nostro sito, al fine di analizzare le modalità di utilizzo dello stesso, dei cookie analitici di Google Analytics fornito da Google Inc. e dunque di terze parti.

Google Analytics

Per impostazioni predefinita, Google Analytics utilizza l’intero indirizzo IP degli utenti del sito web. Affinché il gestore del sito non sia tenuto alla realizzazione del banner di informazione e consenso e alla notificazione all’autorità Garante per la privacy è necessario che Google Analytics sia configurato in maniera tale da ridurre la sua capacità identificativa, mascherando parte dell’indirizzo IP e facendo sì che la terza parte Google si impegni contrattualmente a non utilizzare le informazioni in suo possesso per finalità estranee all’erogazione del servizio.

Di seguito vi indichiamo la procedura adottata per il nostro sito:

Al link https://support.google.com/analytics/answer/2763052 viene fornita da Google la spiegazione tecnica di come Google Analytics anonimizza gli indirizzi IP su richiesta del gestore del sito.

In aggiunta all’anonimizzazione dell’indirizzo IP Google mette a disposizione la possibilità di sottoscrivere un emendamento conforme alla disciplina dettata dalla Direttiva Europea 95/46/CE al link https://support.google.com/analytics/answer/3379636?hl=it l’accettazione dell’emendamento non incide sulle funzionalità di Google Analytics ma comporta dei vincoli contrattuali attraverso i quali Google assicura l’utilizzazione dei cookie per la sola fornitura del servizio.

L’emendamento è una pattuizione aggiuntiva alle condizioni contrattuali di Google Analytics, per effetto della quale, rispetto ai dati personali del cliente, Google assume il ruolo di Responsabile del trattamento.

Ulteriori informazioni in merito al servizio Google Analytics ed alle procedure da seguire per disabilitare i cookie possono essere trovate i seguenti collegamenti:

http://www.google.com/intl/en/analytics/privacyoverview.html https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage

Social media cookie

Alcune pagine sul nostro sito web sono caratterizzate dalla presenza dei cd. social plug-in i quali vi permettono di condividere i nostri contenuti su social media network come Facebook, Twitter, Linkedin.

I cookies Terze parti non sono sotto il nostro controllo e, pertanto, per ulteriori informazioni su come la Terza Parte utilizza i cookies, si consiglia di visitare il sito web della Terza Parte di cui qui di seguito si riportano gli indirizzi web ove presenti le diverse informative e modalità di gestione dei cookies terze parti:

Facebook: Informativa: https://www.facebook.com/help/cookies/ Twitter: Informativa: https://support.twitter.com/articles/20170514 Configurazioni: https://twitter.com/settings/security0 LinkedIn: Informativa: https://www.linkedin.com/legal/cookie-policy Configurazioni: https://www.linkedin.com/settings/

Tipi di cookie che non utilizziamo

Cookie pubblicitari e di pubblicità comportamentale (profilazione)

Questi cookies utilizzati per raccogliere dati sulle abitudini di navigazione e le preferenze dell’utente al fine di sviluppare un profilo specifico per personalizzazioni dell’offerta commerciale, per il compimento di ricerche di mercato o di vendita a distanza.

Gestione dei cookie

In ogni momento, l’utente può rifiutare di accettare tutti o alcuni dei cookies utilizzati su questo sito web nelle seguenti modalità.

Ogni browser ha specifiche istruzioni di configurazione. Ulteriori informazioni in merito alle procedure da seguire per disabilitare i cookie possono essere trovati sul sito internet del fornitore del browser.

Google Chrome:

https://support.google.com/chrome/answer/95647?hl=it

Mozilla Firefox:

http://support.mozilla.org/it/kb/Attivare%20e%20disattivare%20i%20cookie

Internet Explorer:

http://windows.microsoft.com/it-it/windows7/block-enable-or-allow-cookies

Safari:

http://support.apple.com/kb/PH5049

Gestione di Google Analytics

Per disabilitare soltanto l’uso dei cookies di Google Analytics l’utente può utilizzare il componente aggiuntivo messo a disposizione da Google al seguente collegamento seguendo la procedura di opt-out indicata da Google https://tools.google.com/dlpage/gaoptout?hl=it

Conservazione dei dati

Come osservato in precedenza, la durata dei cookies dipende dalla loro natura: i cookies di sessione scadono quando l’utente chiude il browser; i cookies persistenti hanno date di scadenza tipiche che, a meno di particolari eccezioni, non superano i 20 anni.

Modifiche cookie policy

L’associazione A.E.D.I.C. si riserva la facoltà di apportare delle modifiche alla presente cookie policy. L’utente accetta di essere vincolato a tali eventuali e future revisioni e si impegna, pertanto, a visitare periodicamente questa pagina per essere informato su eventuali variazioni.

0 notes

femmelynch · 5 years ago

Text

Cookie Policy

New Post has been published on https://aedic.eu/cookie-policy/

Cookie Policy

Cosa sono i cookie

Tipi di cookie

I cookies possono essere classificati:

sotto il profilo soggettivo in:

Cookies proprietari (o di prima parte)

cioè installati dallo stesso gestore del sito visitato.

Cookies di terze parti

nel caso il cookie sia installato da un sito diverso, per il tramite del sito visitato. a seconda della finalità:

Cookie tecnici (strettamente necessari)

In base ai tempi di permanenza all’interno del dispositivo informatico in:

Cookies di sessione:

vengono rimossi quanto l’utente chiude il browser e che, pertanto, hanno una durata limitata alla tua visita;

Cookies permanenti:

Cookie analitici

Un ulteriore distinzione necessaria per il rispetto degli adempimenti normativi ai sensi del provvedimento 8 maggio 2014 emesso dall’autorità Garante della privacy (doc. web. N.3118884) è tra:

Cookie analitici di prima parte:

Cookie analitici di terze parti:

Tipi di cookie che utilizziamo

Sono presenti nel nostro sito, al fine di analizzare le modalità di utilizzo dello stesso, dei cookie analitici di Google Analytics fornito da Google Inc. e dunque di terze parti.

Google Analytics

Di seguito vi indichiamo la procedura adottata per il nostro sito:

Al link https://support.google.com/analytics/answer/2763052 viene fornita da Google la spiegazione tecnica di come Google Analytics anonimizza gli indirizzi IP su richiesta del gestore del sito.

Ulteriori informazioni in merito al servizio Google Analytics ed alle procedure da seguire per disabilitare i cookie possono essere trovate i seguenti collegamenti:

http://www.google.com/intl/en/analytics/privacyoverview.html https://developers.google.com/analytics/devguides/collection/analyticsjs/cookie-usage

Social media cookie

Tipi di cookie che non utilizziamo

Cookie pubblicitari e di pubblicità comportamentale (profilazione)

Gestione dei cookie

In ogni momento, l’utente può rifiutare di accettare tutti o alcuni dei cookies utilizzati su questo sito web nelle seguenti modalità.

Google Chrome:

https://support.google.com/chrome/answer/95647?hl=it

Mozilla Firefox:

http://support.mozilla.org/it/kb/Attivare%20e%20disattivare%20i%20cookie

Internet Explorer:

http://windows.microsoft.com/it-it/windows7/block-enable-or-allow-cookies

Safari:

http://support.apple.com/kb/PH5049

Gestione di Google Analytics

Conservazione dei dati

Modifiche cookie policy

0 notes

isearchgoood · 5 years ago

Text

March 02, 2020 at 10:00PM - DevGuides Online Programming Education Subscriptions (87% discount) Ashraf

https://harry-bhanot.blogspot.com/2020/03/march-02-2020-at-1000pm-devguides.html?utm_source=dlvr.it&utm_medium=tumblr

0 notes

funyandroid · 6 years ago

Link

#Blogger #android

0 notes

tagdennis · 6 years ago

Text

DevGuides Online Programming Education Subscriptions for $39

Expires March 25, 2024 23:59 PST Buy now and get 87% off KEY FEATURES It’s no secret that programming is one of the more lucrative skills to learn in today’s job market, but finding the time to go back to school can be a challenge. That’s why there’s...

More at iHash.eu

#Special Offers

0 notes

perfectnewgadgets · 6 years ago

Text

Get 2 years of coding training with this $39 DevGuides subscription

Programming is one of the most lucrative skills in today’s job market. But taking time off from your daily grind to learn it can be tough.

Rather than going back to school, try learning on your own time with a subscription to DevGuides Online Programming Education. While it won’t replace the comprehensive education you’d get in a classroom, DevGuides can give you the training you need.

Once you…

View On WordPress

0 notes

masaa-ma · 8 years ago

Text

ECサイトの集客から売り上げまでGAで分析したい！ eコマーストラッキングを徹底解説［第55回］ | 衣袋教授の新・Googleアナリティクス入門講座

from http://web-tan.forum.impressrd.jp/e/2017/09/28/26908

トラッキングコードのカスタマイズの最後を飾るのは、ECサイトの売上データをGoogleアナリティクスに取り込んで分析し、売り上げアップなどの施策をより良くするための「eコマース」のトラッキングコードだ。

これから3回にわたり、eコマースのトラッキングを紹介する。今回はトラッキングコードの設定方法を解説する。

eコマースサイトでは、購入された商品や個数、合計購入金額などは基本的に毎回異なるのが普通だ。通常は、そうした売り上げレポートは別途作っていることだろう。しかし、Googleアナリティクスにこうしたデータを取り込めば、サイト上でのユーザー行動をあわせて分析でき、より具体的なユーザー理解と改善案につなげられるようになる。

それを実現するには、動的にプログラミングしてデータを収集できるようにしなければならない。

eコマースのトラッキングコード実装はハードルが高いが、集客やサイト内の行動だけでなく、最終的に売り上げにどう結びついたのかをGoogleアナリティクスで見られることのメリットは大きい。一定規模以上のeコマースサイトであれば、ぜひチャレンジしてほしいカスタマイズだ。

自前で決済システムを作っている巨大なサイトもあれば、カート投��から決済までの部分は外部のレンタルカートシステムを利用している場合もあるだろう。後半ではそのような場合の注意点についても簡単に触れておく。

この記事で学べること：

集客からeコマースサイトの売り上げまでGoogleアナリティクスで分析するように設定できる

トラッキングコードのどこをカスタマイズすればいいかわかる

「管理」画面で事前にeコマースを「オン」にする

「eコマース」の機能を利用するためには、「管理」画面（図1赤枠部分）でその準備を行っておく必要がある。ビューの列（図1青枠部分）の項目の「eコマースの設定」（図1緑枠部分）をクリックしよう。すると図1のような表示になる。

図1：［管理］＞［eコマースの設定］画面

右上に表示されているeコマースの設定が「オフ」になっているので（図1黒枠部分）、まずはここをクリックして「オン」にする（図2赤枠部分）。そして「次のステップ」（図2青枠部分）をクリックしよう。

図2：カスタムディメンションを追加

「関連商品の有効化」はいずれなくなる可能性が高い

関連商品の有効化については、オフのままでよいだろう（図2緑枠部分）。以前は、この設定をオンにすると同時購入した商品パターンを見ることができた。ただしこれには「一定量のトランザクションデータと商品数が必要で、関連商品のリストを生成するために30日分のデータが必要」と条件が厳しく、筆者はレポートで確認したことがない。またAPIでの提供が終了しているので、レポート上でもおそらくすでに利用できないか、なくなると思われる。この設定はオフでよいだろう。

関連商品（アナリティクスヘルプ） https://support.google.com/analytics/answer/6223409?hl=ja

Googleアナリティクス Reporting APIに関する変更履歴（Google Developers） https://developers.google.com/analytics/devguides/reporting/core/v4/changelog

続いて表示された画面（図3）で、拡張eコマースの設定はオフ（図3赤枠部分）のまま、「送信」（図3青枠部分）をクリックしよう。これでレポート側の準備は終わりだ。

図3：カスタムディメンションを追加

eコマースには2種類ある

この設定プロセスでおわかりのとおり、eコマースの計測方法には現在2つの種類ある。

普通のeコマース（購入完了時のデータ）

拡張eコマース（ページの閲覧やカート投入なども網羅したデータ）

普通のeコマースは「購入完了時点に売上データだけを収集する」方法だ。拡張eコマースは「商品ページの閲覧やカート投入といったさまざまなユーザーの行動まで含んだデータを網羅的に収集する」方法で、設計力と高度で多様な実装が必要になる。

拡張eコマースは本連載の範囲をはるかに超える難易度になるので、ここでは普通のeコマースの実装についてのみ解説する。

準備をしないとレポートに注意書きが出る

この準備をしていないと、関連するレポートである［コンバージョン］＞［eコマース］セクションのレポート群（図4赤枠部分）を見ようと思っても、次のような注意書きが表示（図4青枠部分）される。

図4：［コンバージョン］＞［eコマース］セクションのレポート

トラッキングコードは4種類の記述をセットで行う

それでは本題のトラッキングコードについて進めていこう。eコマースのトラッキングコードは決済完了ページに設定するの��一般的だ。そのページが購入商品や金額が確定した直後だからだ。

そして大きく次の4種類の記述をセットで行う必要がある。

eコマースプラグインの読み込みの記述

トランザクション（購入全体情報）の記述

個々の売上商品明細の記述

以上のトランザクションデータを送信するための記述

正確には2番目と3番目のデータのどちらかだけを送信する記述方法もあるが、そうしたバリエーションについてはここでは説明しない。ここで紹介するのはオーソドックスに一度でデータを送る基本的なパターンの実装方法だと考えてほしい。

①eコマースプラグインの読み込みの記述

それでは1つずつ説明していこう。最初の「eコマースプラグインの読み込みの記述」とは、eコマース機能を利用するために必要な準備をするプログラムを読み込むための記述だ。具体的には次の記述を行う。

ga('require', 'ecommerce');

次のような標準のトラッキングコードのトラッカーオブジェクト（下記赤字部分のこと）作成後の場所に記述する必要がある。標準のトラッキングコードの下（下記青字部分）にeコマースのトラッキングコード一式を追加していくのが素直だろう。

以降は、ここで追加した1行の下に続けて記述していく。

②トランザクション（購入全体情報）の記述

続いて「トランザクションの記述」部分だ。これは該当する1購入全体の情報が含まれる。具体的には、最大で次の5種類の情報を指定する。

変数値の型必須意味 id テキストはいトランザクションID（1つひとつの購買ID） affiliation テキストいいえ売り上げた店舗 revenue 通貨いいえ※ 合計販売金額（送料や税金を含む総合計を指定するのが一般的） shipping 通貨いいえ送料 tax 通貨いいえ税金

表1：トランザクションの記述

表1で※印がある「revenue（合計販売金額）」が「必須」でないのは違和感があるかもしれない。基本的な実装では合計販売金額を記述すべきだが、合計販売金額を送信するにはそれ以外にもさまざまな記述方法が許容されているので「必須ではない」となっているだけだ。※印がある項目は基本的に必須と考えた方が無難だろう。後述する表2でも同様だ。

トラッキングコードの記述例は以下のとおりだ。青字部分が今回記述する範囲で、赤字部分が各変数の値になる箇所なので、そこが各トランザクションで個別に変化する箇所になる。

ga('require', 'ecommerce'); ga('ecommerce:addTransaction', { 'id': 'abc1234', 'affiliation': 'xyz shop', 'revenue': '10800', 'shipping': '500', 'tax': '800' });

上記の例では、購買IDが「abc1234」で、購入店舗が「xyz shop」ということだ。税込売上額が10,800円で、そのうち送料が500円、税が800円なので、その分を差し引けば商品の本体価格は9,500円だということになる。

③個々の売上商品明細の記述

続いて「個々の売上商品明細の記述」部分だ。これは動的なプログラムで商品ごとに繰り返し記述する。たとえば「商品A」が2個、「商品B」が3個売れたのであれば、「商品A」と「商品B」の2つ分の記述が必要になるということだ。各商品では最大で次の6種類の情報を指定する。

変数値の型必須説明 id テキストはいトランザクションID（1つひとつの購買ID） name テキストはい商品の名前 sku テキストいいえ商品のSKU category テキストいいえ商品カテゴリ price 通貨いいえ※ 各商品の単価 quantity 整数いいえ※ 購入した個数

表2：個々の売上商品明細の記述

トラッキングコードの記述例は以下のとおり。赤字部分が各変数の値になるので、可変部分になる。トランザクションIDは、「トランザクションの記述」部分で指定したトランザクションIDと同じものを指定する。

ga('require', 'ecommerce'); ga('ecommerce:addTransaction', { 'id': 'abc1234', 'affiliation': 'xyz shop', 'revenue': '10800', 'shipping': '500', 'tax': '800' }); ga('ecommerce:addItem', { 'id': 'abc1234', 'name': 'klmn', 'sku': '9876xyz', 'category': 'Toy', 'price': '9500', 'quantity': '1' });

各商品を識別するための変数には「name」「sku」「category」があり、これがGoogleアナリティクスのレポート上にあるディメンション「商品」「商品のSKU」「商品カテゴリ」に対応する。レポートでの見え方について詳しくは次回、この記事の最後で簡単に説明する。

「SKU」とは「Stock Keeping Unit」の略で、サイズや色違いの管理したい最小単位のことだ。素直にこの3つを利用するとすれば、一番大きい単位が「category」で、次が「name」、最後が「sku」ということになるだろう。

あとはその販売した商品の単価と販売数量の2つを指定すればいい。

④以上のトランザクションデータを送信するための記述

最後は「以上のトランザクションデータを送信するための記述」部分で、次の記述を行う。これはサイトや商品によって変化せず、同じ記述でよい。

eコマースのトラッキングコードのフルの記述例

最終的にトラッキングコード一式としてはどう記述するかを見てみよう。青字部分がeコマーストラッキングで追記した箇所で、赤字部分がプロパティIDやトランザクションデータ固有の部分だ。赤字部分を実態に合わせて変更することになる。

外部のカートシステムを利用している場合は？

カートシステムは外部のシステムを利用しているという場合もあるだろう。有名なショッピングカートシステムであれば、Googleアナリティクスに対応している場合も多い。しかし商品を陳列している自分のサイトのドメインと外部のショッピングカートは別ドメインになると思うので、次の2つのことを確認しよう。

自分のサイトとカートのサイト間の移動でセッションが切れないように、クロスドメインというトラッキングコードのカスタマイズを行う必要があるかどうか

同じ目的（セッションが切れないようにするため）で、Googleアナリティクス側の参照元除外の設定が必要になるかどうか

ここでは詳細は省略するが、カートシステムが別ドメインになる場合は、Googleアナリティクス側ならびにショッピングカートシステム側でどのような設定が必要か、専門家に聞いて正しく実装と設定を行うようにしてほしい。

対応するeコマースのレポート

eコマース系のレポートの活用方法については次回詳しく解説する予定だが、ここでもトラッキングコードで指定した各変数がレポートのどこに該当するのかだけを示しておこう。

まず「id」は、［コンバージョン］＞［eコマース］＞［トランザクション］レポートにおけるディメンション「トランザクションID」（図5赤枠部分）として利用される。「affiliation」は直接目にすることはないが、セカンダリディメンション（図5青枠部分）などから利用することが可能で、「アフィリエーション」と表示されるディメンションだ。

「revenue」「shipping」「tax」は同レポートにおける「収益」「配送」「税金」の指標（図5緑枠部分）として集計される。

図5：［コンバージョン］＞［eコマース］＞［トランザクション］レポート

「name」「sku」「category」は前述したように［コンバージョン］＞［eコマース］＞［商品の販売状況］レポート上のディメンション「商品」「商品のSKU」「商品」（図6赤枠部分）に対応する。「price」と「quantity」は同レポートの各指標（図6青枠部分）の集計数値に利用される。

図6：［コンバージョン］＞［eコマース］＞［商品の販売状況］レポート

次回は、こうやって収集したeコマースのレポートをどのように見て、分析していくかを解説する。

※このコンテンツはWebサイト「Web担当者Forum - 企業ホームページとネットマーケティングの実践情報サイト - SEO/SEM アクセス解析 CMS ユーザビリティなど」で公開されている記事のフィードに含まれているものです。オリジナル記事：ECサイトの集客から売り上げまでGAで分析したい！ eコマーストラッキングを徹底解説［第55回］ | 衣袋教授の新・Googleアナリティクス入門講座 Copyright (C) IMPRESS CORPORATION, an Impress Group company. All rights reserved.

この記事の筆者

衣袋宏美（いぶくろ　ひろみ）

1960年東京都生まれ。東京大学教養学部教養学科卒業。大手電気メーカー勤務後、日経BP社へ。調査部、インターネット視聴率センター長などを経て、2000年ネットレイティングスへ。視聴率サービスやアクセス解析サービスの立ち上げに尽力。2006年株式会社クロス・フュージョンを設立し代表取締役に。現在アユダンテ株式会社の社外フェロー、アクセス解析イニシアチブ副代表も兼任。

著書など：

『Google Analyticsによるアクセス解析入門』単著

新バージョン対応『Google アナリティクス完全マニュアル』（電子書籍）

『PROFESSIONALアクセス解析』単著

『ネット視聴率白書2008-2009』編著

『Webアナリスト養成講座』監訳

ブログ： Insight for WebAnalytics

Web担当者Forumでの連載：

「Googleアナリティクスセグメント100選」

「衣袋宏美のデータハックス」

「リサーチ／データのリテラシー入門-----調査統計の基礎知識」

「データをざくざく処理するためのグラフの読み方、使い方」

「有名サイト、かってに解析！」

→衣袋宏美（株式会社クロス・フュージョン）のプロフィールページ

http://web-tan.forum.impressrd.jp/sites/default/files/images/article2016/ga-nyumon/ga-nyumon55_01m.png

#Feedly

0 notes