Tutte le novità su Lotus Notes e Domino 8.5.3, previsto entro fine anno ed attualmente in beta chiusa. Vieni a scoprire tutte le migliorie e nuove funzionalità di questo importante rilascio. Una sessione di interesse per sviluppatori ed amministratori.
Come ultima versione del ciclo di rilasci sprint della v10, TYPO3 versione 10.3 è definita versione "feature freeze". Questo significa nessuna nuova funzionalità d’ora in poi e fino alla versione LTS di aprile il core team e tutti i collaboratori saranno focalizzati sui test, la pulizia e il miglioramento della versione.
Global Azure Bootcamp 2018 - Verona.
Scalare una applicazione con le proprie applicazioni con Azure Functions.
All'interno è presente la spiegazione di Durable Functions con qualche esempio completo
Enterprise Spring and Flex applicationsmarcocasario
SpringSource ha recentemente annunciato Spring BlazeDS Integration, un nuovo progetto open source per permettere una facile integrazione tra il framework Spring e Adobe BlazeDS, una tecnologia open source basata su server Java remoting e Web messaging.
Il plugin di SpringSource fornisce un approccio più semplice ed intuitivo agli sviluppatori Spring e Java per creare Enterprise Rich Internet Applications utilizzando il framework Adobe Flex, una pietra miliare della Flash Platform.
In questa sessione ai partecipanti verrà fornita una panoramica del framework Flex e di BlazeDS, illustrando i vantaggi e le modalità di integrazione al framework Spring attraverso il plugin Spring BlazeDS.
Slides della presentazione fatta al Wordpress Camp Bologna il 24 novembre 2012. Per ulteriori informazioni potete contattarmi scrivendo a marco@partecipant.it
Queste sono le slide dell'evento organizzato da Visual Basic Tips & Tricks a Vicenza il 12/10/2012 relative alla sessione di Piero Sbressa e Carmelo La Monica su Team Foundation Server
TYPO3 v10.4 (chiamato anche TYPO3 v10 LTS indicando che si tratta di una versione di supporto a lungo termine) è la nostra nuova ammiraglia e, senza dubbio, uno dei sistemi di gestione dei contenuti open source basati su PHP più avanzati attualmente sul mercato.
La versione 10.1 di TYPO3 è la seconda versione dello sprint per arrivare alla versione LTS (supporto a lungo termine) nel 2020.
La nuova release ingloba più di 240 commit di Git (modifiche del codice sorgente revisionate, testate e approvate) dalla sua versione precedente la 10.0 pubblicata dieci settimane prima.
Sebbene gli utenti di backend non vedranno molti cambiamenti evidenti o nuove funzionalità importanti, TYPO3 versione 10.1 racchiude una serie di miglioramenti nel core.
Nel corso di quest’articolo vedremo come sia possibile sfruttare il Service Builder (Liferay Inc., 2014) per creare dei servizi da esporre all’esterno non direttamente collegati all’entità gestiste dallo specifico plugin.
Quello che vogliamo ottenere è quindi un servizio personalizzato chiamato Custom Users Service disponibile pubblicamente e che sfrutti i servizi core del portale. In questo particolare scenario vogliamo fare in modo che il servizio Custom Users Service, esponga un metodo che ritorni al consumer del servizio, la lista di utenti taggati con un determinato tag (Liferay Inc., 2014).
Come ultima versione del ciclo di rilasci sprint della v10, TYPO3 versione 10.3 è definita versione "feature freeze". Questo significa nessuna nuova funzionalità d’ora in poi e fino alla versione LTS di aprile il core team e tutti i collaboratori saranno focalizzati sui test, la pulizia e il miglioramento della versione.
Global Azure Bootcamp 2018 - Verona.
Scalare una applicazione con le proprie applicazioni con Azure Functions.
All'interno è presente la spiegazione di Durable Functions con qualche esempio completo
Enterprise Spring and Flex applicationsmarcocasario
SpringSource ha recentemente annunciato Spring BlazeDS Integration, un nuovo progetto open source per permettere una facile integrazione tra il framework Spring e Adobe BlazeDS, una tecnologia open source basata su server Java remoting e Web messaging.
Il plugin di SpringSource fornisce un approccio più semplice ed intuitivo agli sviluppatori Spring e Java per creare Enterprise Rich Internet Applications utilizzando il framework Adobe Flex, una pietra miliare della Flash Platform.
In questa sessione ai partecipanti verrà fornita una panoramica del framework Flex e di BlazeDS, illustrando i vantaggi e le modalità di integrazione al framework Spring attraverso il plugin Spring BlazeDS.
Slides della presentazione fatta al Wordpress Camp Bologna il 24 novembre 2012. Per ulteriori informazioni potete contattarmi scrivendo a marco@partecipant.it
Queste sono le slide dell'evento organizzato da Visual Basic Tips & Tricks a Vicenza il 12/10/2012 relative alla sessione di Piero Sbressa e Carmelo La Monica su Team Foundation Server
TYPO3 v10.4 (chiamato anche TYPO3 v10 LTS indicando che si tratta di una versione di supporto a lungo termine) è la nostra nuova ammiraglia e, senza dubbio, uno dei sistemi di gestione dei contenuti open source basati su PHP più avanzati attualmente sul mercato.
La versione 10.1 di TYPO3 è la seconda versione dello sprint per arrivare alla versione LTS (supporto a lungo termine) nel 2020.
La nuova release ingloba più di 240 commit di Git (modifiche del codice sorgente revisionate, testate e approvate) dalla sua versione precedente la 10.0 pubblicata dieci settimane prima.
Sebbene gli utenti di backend non vedranno molti cambiamenti evidenti o nuove funzionalità importanti, TYPO3 versione 10.1 racchiude una serie di miglioramenti nel core.
Nel corso di quest’articolo vedremo come sia possibile sfruttare il Service Builder (Liferay Inc., 2014) per creare dei servizi da esporre all’esterno non direttamente collegati all’entità gestiste dallo specifico plugin.
Quello che vogliamo ottenere è quindi un servizio personalizzato chiamato Custom Users Service disponibile pubblicamente e che sfrutti i servizi core del portale. In questo particolare scenario vogliamo fare in modo che il servizio Custom Users Service, esponga un metodo che ritorni al consumer del servizio, la lista di utenti taggati con un determinato tag (Liferay Inc., 2014).
1. The document discusses options for mail clients from Traveler to Verse On-Premises, including the transition from "Bring Your Own Device" to "Bring Your Own Client".
2. It provides an overview of IBM Verse On-Premises, which allows customers to deploy the Verse experience on-premises using their existing Domino infrastructure.
3. Technical details are presented on supported browsers, server platforms, and the high-level architecture involving APIs to Connections for social features.
IBM Watson Assistant
Workspace: IBM Watson Workspace
Services: IBM Watson Work Services
Platform: IBM Watson Work Platform
Developer: IBM Watson Work Developer
43
The document discusses enterprise integration and provides examples of integrating IBM products like IBM Verse and IBM Connections with Salesforce. It begins with discussing past challenges with enterprise integration and how application programming interfaces (APIs) now help enable integration. It then covers key integration challenges around data synchronization, security, and development. Live demos are presented showing how IBM Connections can be integrated into Salesforce using Lightning Out and REST APIs, and how IBM Verse and Salesforce can be integrated in a similar manner. Resources for further information are provided.
Ortocloud è arrivata seconda all'ICS del developer competition di IBM.
Permette di vedere come è stato possibile sfruttare i servizi weather di Bluemix con le XPages e noSQL Database di Domino
This document provides an overview of using Cloudant as a NoSQL database with XPages applications. It discusses why the author chose Cloudant for an HR application, introduces Cloudant and how it works, and shows how to connect to Cloudant from XPages using a Cloudant connector. Code examples demonstrate storing, retrieving, searching, and attaching files in Cloudant from XPages applications.
1. IBM Connections is a collaboration and social software platform that allows users to work together even when they are in different locations or time zones. It facilitates sharing and collaboration through features like communities, files, activities, and integration with other applications.
2. The document discusses the benefits of community sharing over individual sharing in IBM Connections, including shared ownership and granular access rights for community members. It also covers the differences between public, restricted, and private access settings for shared content.
3. Attachments are meant to accompany other items and are static, while files in IBM Connections allow for editing, versioning, commenting, liking, and flexible sharing settings depending on whether the file is personal or community-
This document provides various legal disclaimers and notices for information presented about IBM's Verse product. It states that product plans are subject to change without notice, and limits IBM's liability. It also notes that any statements about IBM's future intent or product plans could change or be withdrawn without notice. Performance data presented may have been obtained in controlled environments and may vary in other settings.
IBM presented its Notes and Domino roadmap, which includes continued support for current platforms through 2021, quarterly feature packs for incremental improvements, and the general availability of Verse On-Premises in December 2016. The roadmap aims to accelerate feature delivery through a continuous update model and provide customers choice in collaboration solutions.
- Traditional collaboration tools cause too much interruption from an overload of disconnected apps, interruptions, and data.
- IBM is developing Watson Work to integrate analytics, collaboration, content and Watson's cognitive abilities into a single platform. This will help organizations empower employees by connecting them to experts, speeding access to relevant information, and providing space to work simply and together.
- Watson Work will include team messaging, compliant communication and workflows, enterprise social networks, audio and video conferencing, content management, digital signatures, and analytics. It aims to transform digital workplaces.
17. Novità Lotus Designer 8.5.3 Novità della nuova Release Soggetto a modifiche da parte di IBM in fase di rilascio della GOLD Release Change with your picture, add a 4pt border color 255,204,0 Cambia con la tua foto, aggiungi un bordo spesso 4pt colore 255,204,0 Please make sure that your slide deck renders fine in Lotus Symphony Per favore controlla che le tue slide si vedano bene con Lotus Symphony
A new replication option, Enable Purge Interval Replication Control , on the Space Savers tab prevents older deletion stubs and document modifications from replicating to the application. Purge Interval Replication Control (PIRC) is a new replication setting which is designed to prevent old documents which may have been deleted from replicating back into a database after their deletion stubs have been purged. This problem has been encountered by many customers. The most common case occurs when an old version of a NAB (Domino Directory) is brought back online after several months or years. When this occurs, previously deleted person documents, group documents, server documents, and other design elements can replicate back into the environment because the deletion stubs have already been purged. PIRC prevents these documents from replicating back into the environment. How PIRC Works PIRC prevents documents from replicating back in two ways. The first is by modifying the 'since time' used by the replicator. If the server that is initiating the replication is release 8.5.3 and therefore PIRC-aware, then the algorithm to determine which documents qualify for replication has been changed to use the later of the PIRC date or the Since time contained in the replication history. This prevents the older documents from being replicated. Also, a DDM event is generated showing the number of documents skipped by PIRC. The second way in which PIRC prevents older documents from replicating in is by stopping the documents from being added to the database via NoteUpdate. This method occurs when a non-PIRC aware server is pushing older documents to the PIRC-aware server. In this case, NoteUpdate code will compare the SequenceTime of the document to the PIRC date. If the document is older, a DDM event will be logged and the document will be rejected. Note that the source server is unaware that the document was rejected. Therefore its logs will show that all documents were successfully replicated. However, the PIRC server will log the server name and the documents that were rejected, thus allowing the administrator to track down old replicas of the database and remove them from the environment. PIRC keys off the Cutoff date of a database. The cutoff date is the date when purge last ran. Purge is the process which removes deletion stubs from a database. Purge runs at one-third of the purge interval. So if the purge interval is set to 90 days, then a database may have deletion stubs up to 120 days old. Therefore PIRC will use this date to prevent documents older than this date from replicating into the database. If the cutoff date is not set in a database, which happens when replication history is cleared, the current date minus the purge interval is used.
@GetMachineInfo( [Keyword]; "Needed for some Keywords string" ) Keywords: IsLaptop boolean return True if machine is a laptop, otherwise false IsDesktop boolean return True if machine is NOT a laptop, otherwise false IsSingleLogOn boolean return True if machine has Notes client installed with "single sign on", otherwise false IsMultiUser boolean return True if machine has Notes client installed as Multi-User, otherwise false HasDesigner boolean return True if machine has Designer client installed, otherwise false HasAdmin boolean return True if machine has Admin client installed, otherwise false IsStandard boolean return True if machine is running Standard Notes client, otherwise false MachineName string return Name of the machine boolean return True if MachineName string after keyword matches this machine's MachineName, otherwise false Memory number return Total amount of memory (RAM) DiskSpace number return Amount of free disk space Note: With this keyword, you can add a second parameter for the drive to scan for free space. If this parameter is not passed to the function, free space for the first (logical) drive - for example, drive C on Windows system - is displayed. Example: @GetMachineInfo([DiskSpace];"d:") EnvVariable string return Requires string of the variable name in Notes.ini to read, and returns the value of that ini variable or "" (null string) if not found SysEnvVariable string return Requires string of the variable name in system environment to read, and returns the value of that variable or "" (null string) if not found IP string/list return String representation of the IP address(es) in the form XXX.XXX.XXX.XXX , otherwise "" (null string) if not available boolean return True if pattern IP string after keyword matches this machine's IP address, otherwise false MAC string/list return String representation of the MAC address(es) in the form XX:XX:XX:XX:XX:XX , otherwise "" (null string) if not available boolean return True if MAC string after keyword matches this machine's MAC address, otherwise false Information for creating policy setting formulas Be sure all formulas have the correct syntax and can be compiled. Be sure values generated are correct in the context of the policy setting it is evaluated to. If the policy setting is text, then the formula should evaluate to a textual value. If the evaluation of the formula results in a type other than that of the setting, a mismatch error will be logged in the client's log and the setting will contain the default value, not the formula evaluated value. Use multiple conditions (if necessary) to ensure the formula is targeted at the correct machines/clients, and applied for the correct environment, and machine characteristics. The following are examples of how the formulas can be entered for the available settings. For the 8.5.3 client, these settings will be defaulted to the selected value for that setting, any formula provided will be evaluated and the result will overwrite or add the setting to the policy when it is read by the client. Clients older than the 8.5.3 version, will receive the selected default setting, and the formula will not be evaluated and the variable settings will not overwrite the defaults. Local Mail File and Managed Replica The values are "1", "3", "7" and "8" and the results of the formula must be textual and one of these values. "1" Create local replica "3" Create managed replica "7" Create managed replica or convert local replica to managed replica "8" Delete local replica or managed replica "0" Don't create local replica or managed replica (FYI: Someone needs to update the MMR doc to include this value too.) See Notes documentation for information on Managed Replicas and their supporting policy settings. Using the @UnAvailable as a formula result will make the setting not available.
If "Require approval for device access" is enabled, and a user's device registers with the Lotus Traveler server, this policy checks to see if the user already has registered other devices. If the total count of registered devices including this one exceeds the "Number of devices to allow per user before approval is required", then the device is added to the Lotus Traveler system, but is not allowed to access any data until an administrator provides explicit approval for the device. When this occurs, if there is an email address or group name specified in the "Addresses to notify when approval action is pending", then the administrator and the user will receive an email indicating that an approval action is required before the device is allowed to use the system. To approve the device, the Lotus Traveler administrator opens the LotusTraveler.nsf application using the Domino Administrator client. In the Device Security view of this application, there is a new column called Device Approval which contains the device approval state. The administrator should select the action "Change Approval" to approve a device once they have confirmed that this is the appropriate action for this user.