各自の予定はカレンダーと呼び、予定の検索や時間調整はスケジュールと呼びます。今回はスケジュールのお話し。Dominoがどの様にスケジュール情報を集めて処理しているか、またどのタスクや文書が関係しているかをご説明します。後半はOnTimeがDominoカレンダーとExchangeカレンダーの連携の実現方法についてもご説明しています。
Each event is called a calendar, and event search and time adjustment is called a schedule. This time I will talk about the schedule. Learn how Domino collects and processes schedule information and what tasks and documents are involved. In the second half, OnTime also explains how to implement linkage between Domino calendar and Exchange calendar.
This document outlines a presentation on deployment models given by José Cebrián, Marc Escalona, and Gonzalo Ozdy on July 14, 2021 for the Madrid MuleSoft Meetup #7. The presentation included an overview of deployment models, a comparative of CloudHub, on-premises, and Runtime Fabric options, use cases demonstrating the decision process, and the roadmap for Runtime Fabric. It was split into two sessions, the first on introduction to deployment models and the second a demo of Runtime Fabric installation.
Designing Apps for Runtime Fabric: Logging, Monitoring & Object Store Persist...Eva Mave Ng
Sydney MuleSoft Meetup - 15th July 2021
Designing Apps for Runtime Fabric: Logging, Monitoring & Object Store Persistence
Speakers:
- Shefreen Kunhimohamed, NJC Labs, Integration Architect
Hosts/Moderators:
- Eva Mave Ng, MuleSoft, Senior Solution Engineer
- Royston Lobo, MuleSoft, Senior Technical Architect
To be notified for all future events, please join the Sydney MuleSoft Meetup group at https://meetups.mulesoft.com/sydney/
各自の予定はカレンダーと呼び、予定の検索や時間調整はスケジュールと呼びます。今回はスケジュールのお話し。Dominoがどの様にスケジュール情報を集めて処理しているか、またどのタスクや文書が関係しているかをご説明します。後半はOnTimeがDominoカレンダーとExchangeカレンダーの連携の実現方法についてもご説明しています。
Each event is called a calendar, and event search and time adjustment is called a schedule. This time I will talk about the schedule. Learn how Domino collects and processes schedule information and what tasks and documents are involved. In the second half, OnTime also explains how to implement linkage between Domino calendar and Exchange calendar.
This document outlines a presentation on deployment models given by José Cebrián, Marc Escalona, and Gonzalo Ozdy on July 14, 2021 for the Madrid MuleSoft Meetup #7. The presentation included an overview of deployment models, a comparative of CloudHub, on-premises, and Runtime Fabric options, use cases demonstrating the decision process, and the roadmap for Runtime Fabric. It was split into two sessions, the first on introduction to deployment models and the second a demo of Runtime Fabric installation.
Designing Apps for Runtime Fabric: Logging, Monitoring & Object Store Persist...Eva Mave Ng
Sydney MuleSoft Meetup - 15th July 2021
Designing Apps for Runtime Fabric: Logging, Monitoring & Object Store Persistence
Speakers:
- Shefreen Kunhimohamed, NJC Labs, Integration Architect
Hosts/Moderators:
- Eva Mave Ng, MuleSoft, Senior Solution Engineer
- Royston Lobo, MuleSoft, Senior Technical Architect
To be notified for all future events, please join the Sydney MuleSoft Meetup group at https://meetups.mulesoft.com/sydney/
Satellite 6 introduces new features for automation including improved support for Puppet. Puppet allows for recipe-style configuration management and drift management. The presentation demonstrates installing and configuring Puppet on a server and client, writing Puppet code to manage files and directories, and using the Puppet dashboard. Considerations for using Puppet with Satellite 6 include keeping Puppet modules modular and mapping modules to Satellite host groups.
One of an Information Architect’s main roles is to develop and maintain an organization’s Information Model. But it’s usually up to other roles—tools and editorial, specifically—to express and enforce the Model. Wouldn’t it be nice if during the act of writing the Information Model, the IA was simultaneously creating the automatic enforcement and expression of the Model in the authoring environment?
In this presentation, George and Dawn show how an IA can author an organization’s Information Model using DITA topics and maps—as is the industry standard practice—but take it one step further, with the IA’s input being used as the specifications for auto-generated Schematron rules and tool tips.
The document discusses Dockerfiles, which are used to build Docker images. A Dockerfile contains instructions like FROM, RUN, COPY, and CMD to set the base image, install dependencies, add files, and define the main process. Images are read-only layers built using these instructions. Dockerfiles can be built locally into images and published to repositories for sharing. Volumes are used to persist data outside the container.
CICS is the power of mainframe. It has all the capabilities to handle online transactions. The ppt covers highly useful CICS concepts to refresh your CICS knowledge quickly.
Satellite 6 introduces new features for automation including improved support for Puppet. Puppet allows for recipe-style configuration management and drift management. The presentation demonstrates installing and configuring Puppet on a server and client, writing Puppet code to manage files and directories, and using the Puppet dashboard. Considerations for using Puppet with Satellite 6 include keeping Puppet modules modular and mapping modules to Satellite host groups.
One of an Information Architect’s main roles is to develop and maintain an organization’s Information Model. But it’s usually up to other roles—tools and editorial, specifically—to express and enforce the Model. Wouldn’t it be nice if during the act of writing the Information Model, the IA was simultaneously creating the automatic enforcement and expression of the Model in the authoring environment?
In this presentation, George and Dawn show how an IA can author an organization’s Information Model using DITA topics and maps—as is the industry standard practice—but take it one step further, with the IA’s input being used as the specifications for auto-generated Schematron rules and tool tips.
The document discusses Dockerfiles, which are used to build Docker images. A Dockerfile contains instructions like FROM, RUN, COPY, and CMD to set the base image, install dependencies, add files, and define the main process. Images are read-only layers built using these instructions. Dockerfiles can be built locally into images and published to repositories for sharing. Volumes are used to persist data outside the container.
CICS is the power of mainframe. It has all the capabilities to handle online transactions. The ppt covers highly useful CICS concepts to refresh your CICS knowledge quickly.