This section describes how to create/update configuration items (CIs) in bulk via a CSV file

• To import CIs in Redpeaks, navigate to Organizations menu and press import CSV
• The import feature is able to create or update existing CIs
• It will use shortnames to identify if a CI already exists or not.
• Existing ones will be updated when possible
• Fields like shortnames cannot be changed. This means that you cannot move a CI from a parent to another once created
• If you want to change CI's hierarchie, you will have first to manually delete them.

Create a file and follow the below syntax to register the CI

• Define one CI per line
• Each line must start by the CI type
• Fields must be separated by semi colons
• Fields starting with ? are not mandatory
• Fields in CAPITAL letters can only use arbitrary values
• User profile must be associated by title in the connectors, so mind the naming convention
• CI's within an organization must be declared in following order:
  • ORGANIZATIONS
  • GROUPS
  • USERS
  • SYSTEMS
  • CONNECTORS

Note:

• You can omit to define Organizations and Groups
• In this case, the shortnames defined in systems or users definitions will be used to automatically create the corresponding CI's, using shortname as title.
• Example:
  • SYSTEM;redpeaks;europe;psm;… line will create “redpeaks” organization and “europe” group automatically.

• It is very important to pay attention to short name definition
• Short names will be used to build resource and metric URI, therefore it must be :
  • As short as possible (3 to 10 chars)
  • Meaningful (don't use serial numbers)
  • Don't use special characters or spaces
  • Must be unique vs other components from the same type
    • Example: 2 organizations or 2 systems cannot use the same shortname.
• Define a naming convention or use an existing one.
• Resource URI will be built by using shortname such as:
  • /[ORG_SHORTNAME]/[GROUP_SHORTNAME]/[SYSTEM_SHORTNAME]
  • Such as:
    • /dotnet/prod/prd
    • /dotnet/quality/qal
  • Therefore, to use short and meaningful names are important for the sake of readability of dashboards and reports
• If you are going to define many organizations, we advize to use a naming convention to identify an organization via a 5 character shortnames

ORGANIZATION;shortname;name;?description

GROUP;organization shortname;shortname;name;?description

USER;organization shortname;group shortname;user title;username;password

SYSTEM;organization shortname;group shortname;shortname;[TYPE];sid;title;[?ROLE];[?ENVIRONMENT];?description

Variables can be replaced by values from the below tables:

• You will find below a format description for each type of connector
• Each connector must be identified within a system with organization/group/system shortnames
• To define connector connection credentials, you will use the user title of a USER PROFILE.
• Example:
  • If you registered a user such as:
    • User title: ABAP user
    • User name: sapuser
    • Password: abcd123
  • You can assign this user profile to a connector by setting “ABAP user” to user profile field.

CONNECTOR_ABAP;organization shortname;group shortname;system shortname;name;host;client;logonGroup;MS port;user profile;?sap router;?AS direct connect

• AS direct connect: This field can contain an application server number (2 digits). If set, it will directly connect to this server not going though the message server.

CONNECTOR_ABAP_SNC;organization shortname;group shortname;system shortname;name;host;client;logonGroup;MS port;user profile;?sap router;?AS direct connect;SNC lib path;SNC partner;SNC myName

CONNECTOR_WEB;organization shortname;group shortname;system shortname;name;host;system number;user profile;?port;?loginUrl

CONNECTOR_SAPCONTROL;organization shortname;group shortname;system shortname;name;host;system number;user profile;?port;?useSecure mode;?isJ2ee

• useSecure mode: If set, will use secure protocol and port to connect
• isJ2ee: Set to true is the instance runs SAP J2EE applications

CONNECTOR_BO;organization shortname;group shortname;system shortname;name;CMS host;CMS port;CMS user profile;CMC host;CMC port;CMC user profile;[AUTHENTICATION_TYPE]

CONNECTOR_HANA;organization shortname;group shortname;system shortname;name;nodes;instance number;tenant DB;isSingleContainer;user profile;?custom port;?isSecure;?isPrimary

• nodes: A coma separated list of nodes
• isSingleContainer: Set to false for multi tenant systems
• custom port: Use it to connect to a non standard port (3XX13/3XX15)

CONNECTOR_SYBASE;organization shortname;group shortname;system shortname;name;host;port;database;user profile;properties
CONNECTOR_MSSQL;organization shortname;group shortname;system shortname;name;host;port;database;user profile;properties
CONNECTOR_MAXDB;organization shortname;group shortname;system shortname;name;host;port;database;user profile;properties
CONNECTOR_ORACLE;organization shortname;group shortname;system shortname;name;host;port;database;user profile;properties

• properties: Coma separated list of properties (PROP1=VAL1,PROP2=VAL2)

You can automatically assign profiles to the imported connectors by naming your profiles following the below convention:

• [ORG_SHORTNAME]-[GROUP_SHORTNAME]-[TYPE]
• [GROUP_SHORTNAME]-[TYPE]
• DEFAULT-[TYPE]

Example:

• Profile named: AGL-PROD-ABAP will be associated to all ABAP connectors from PROD group of AGL organization
• Profile named: DEV-ORACLE will be associated to all ORACLE connectors from groups using DEV as shortname (Will not match if matched by the first convention)
• Profile named: DEFAULT-HANA will be associated to all HANA connectors (will not match if matched by firs or second convention)

ORGANIZATION;AGL;Agentil;Agentil-Software
GROUP;AGL;dev;Development;Development group
GROUP;AGL;prd;Production;Production group
USER;AGL;prd;S4h user;PROMONITOR;<password>
USER;AGL;prd;MAXDB user;PROMONITOR;<password>
USER;AGL;prd;PSM-ABAP;PROMONITOR_S;<password>
USER;AGL;prd;PSM-ORACLE;PROMONITOR_S;<password>
SYSTEM;AGL;prd;psm;NETWEAVER;PSM;Solman;QUALITY;;
CONNECTOR_MAXDB;AGL;prd;psm;AGL-prd-S4H-maxdb con;host;1233;DB;MAXDB user;ENCRYPT=true
CONNECTOR_ABAP;AGL;prd;psm;PSM ABAP;1.2.3.4;001;SPACE;3600;PSM-ABAP;/H/2.2.2.3/S/3299;00
CONNECTOR_ORACLE;AGL;prd;psm;PSM_oracle;oracle.psm.com;1232;PSM;PSM-ORACLE;ENCRYPT=false
CONNECTOR_MSSQL;AGL;prd;psm;PSM_mssql;mssql.psm.com;666;PSM;PSM-ORACLE;ENCRYPT=true
CONNECTOR_SYBASE;AGL;prd;psm;PSM_sybase;sybase.psm.com;777;PSM;PSM-ABAP;ENCRYPT=false,TLS=1.3

ORGANIZATION;Pigeot;Pigeot;The Pigeot company;
GROUP;Pigeot;perf;Performance
USER;Pigeot;perf;S4H user;PROMONITOR;<password>
USER;Pigeot;perf;s4hadm_user;s4hadm;<password>
USER;Pigeot;perf;s4hadmin;s4hadm;<password>
SYSTEM;Pigeot;perf;s4h;NETWEAVER;S4H;System S/4HANA;PRODUCTION;S4;
CONNECTOR_ABAP;Pigeot;perf;s4h;S4H;mys4syshost;200;SPACE;3600;S4H user;/H/10.4.4.4/S/3299;00
CONNECTOR_SAPCONTROL;Pigeot;perf;s4h;s4h 00;mys4syshost;00;s4hadm_user;50013;true;false;
CONNECTOR_SAPCONTROL;Pigeot;perf;s4h;s4h 02;mys4syshost;03;s4hadm_user;;;
CONNECTOR_PORTAL;Pigeot;perf;s4h;portal;mys4syshost;04;s4hadmin;;/nwa

ORGANIZATION;Alpine;Alpine;;
GROUP;Alpine;perf;Performances
USER;Alpine;perf;S4H user;PROMONITOR2;<password>
USER;Alpine;perf;ha6_user;SYSTEM;<password>
USER;Alpine;perf;cms_user;CMS;<password>
USER;Alpine;perf;cmc_user;CMC;<password>
SYSTEM;Alpine;perf;HA6;HANA;HA6;System HANA2;QUALITY;S4;
SYSTEM;Alpine;perf;BOZ;BO;BOZ;System BOBJ;QUALITY;;
CONNECTOR_HANA;Alpine;perf;HA6;HA6;hananode1,hananode2;00;SYSTEMDB;false;ha6_user;;false;true
CONNECTOR_BO;Alpine;perf;BOZ;BOBJ BOZ;cms_host;6400;cms_user;cmchost;4567;cmc_user;LDAP