In this section, calendar APIs are explained.
Note that the following APIs, provided by previous versions of Systemwalker Operation Manager, are used in the same way as they are in this version. The operating environment, precautionary items and required files are the same as for this version.
Calendar Registration API (Mp_AddCalendar)
Calendar Update API (Mp_SetCalendar)
Calendar Information Acquisition API (Mp_GetCalendar)
Previous versions of Systemwalker Operation Manager indicate the following versions:
SystemWalker/OperationMGR V4.0L10/V4.0L20
SystemWalker/OperationMGR 4.0
The section below explains the operating environments, precautionary items, and required files which are common to calendar APIs.
Operating Environment
These APIs can only be operated on machines where the Systemwalker Operation Manager server is installed. They will not operate on machines where only the Systemwalker Operation Manager client is installed.
The APIs can be used only for Windows, Solaris and Linux..
Cautions
Do not perform optimization in a compiling environment.
In a compiling environment, use Visual C++ (version 2015) as the compiler and "multithread (DLL) " as the runtime library. [Windows]
Use the same version/levels of the LIB file and INCLUDE file.
Required Files
The following files are required to use the calendar APIs shown above:
Windows 32-bit
f3crhcap.lib
f3crhcap.h
Windows 64-bit
f3crhcap_x64.lib
f3crhcap_x64.h
Solaris 32-bit
libcalapi.so
f3crhcap.h
Solaris 64-bit
libcalapi_64.so
f3crhcap_64.
Linux 64-bit
libcalapi_x64.so
f3crhcap_x64.h
Each calendar API is stored in the LIB file, and the definitions and structures used by each API are declared in the INCLUDE file.
These files are stored in the following directories:
[Windows]
Systemwalker Operation Manager installation directory: MpWalker.JM\lib
Systemwalker Operation Manager installation directory: MpWalker.JM\include
Common to Solaris 32-bit, Solaris 64-bit and Linux 64-bit
/opt/FJSVjmcal/lib
/opt/FJSVjmcal/include
