The Cloud Integration Content (CIC) Management Cockpit allows deploying integration content artifacts from SAP BTP Integration Content catalog or from an archive in the file system to an on- premise environment. CIC allows importing artifacts such as integration flows and value maps from tenant application on cloud or local file system. Use the Deploy feature in Integration Content tab, to import and deploy integration content artifacts.
Use the Cloud Integration Content Management Cockpit to deploy and manage the cloud integration content artifacts (such as integration flows, value mappings, and security artifacts).
You can use it to start and stop cloud integration scenarios (integration flows) and see the current status as well as errors. It also shows the available communication end points of the scenarios and you can view exiting alert rules or create new ones by selecting Alert Configuration.
To start the Cloud Integration Content Management Cockpit, choose one of the following options:
CIC Management Cockpit - Start options:
- Enter http://[host]:[port]/dir in any supported browser; this will open the SAP NetWeaver Process Integration Tools. Under Integration Directory, choose Cloud Integration Content.
- Enter http://[host]:[port]/IGWGBDeploy/Admin in any supported browser to go to the Cloud Integration Content Management Cockpit page directly.
To deploy new content in the Cloud Integration Content Management Cockpit, select Integration Content → Deploy. The Deploy Integration Content pane opens. You have three options for deployment.
Options to deploy Integration Content:
- Deploy Integration Content from Cloud Tenant via Destination. Select Destination to the tenant system in the Deploy Integration Content pane. To create Destinations, go to the NetWeaver Administrator → Destinations. The destination type must be HTTP. The recommended name for the destination is IntegrationContentCatalog.
- Deploy Integration content from Cloud Tenant via URL. Enter the values in the respective fields in theDeploy Integration Content pane, based on the following description.
Required information
Parameter Description Tenant URL Provide the URL of a tenant system, from which the application imports the integration content. For example, https://<domain name>:<port> . User Provide username of the tenant system. Password Provide password of the tenant system. - Deploy Integration Content from File System. Select File System, to import and deploy integration artifacts from a file. Choose Browse, to browse to the cloud integration content *.zip file. Enter a package name to deploy the artifacts or leave it empty to deploy to the default package.
Note
- Deployment via URL only allows basic authentication. Deployment using Destination also supports other authentication methods.
- You can undeploy the integration content. Choose the integration content deployed and click Undeploy.
- Some table columns are initially hidden, for example Application Status and Runtime Status.
- The Application Status column displays the status of the corresponding Java application that is deployed as part of the integration content deployment.
- The Runtime Status column displays the status of the integration content (only integration flow) deployed on the server. The runtime status displayed in the Cloud Integration Content Management Cockpit will be:
- Green, if the integration content is initialized.
- Yellow, if the status of the integration content cannot be determined.
- Red, if the integration content initialization fails or some error occurred during message processing. You can check error details in the log viewer.
- Grey, if the integration content is stopped.
- The status is a combined status resulting from application status and runtime status.
Manage Integration Content
The figure shows the possible options for managing the integration content.
Start and Stop Integration Flows
To start, stop or restart one or more integration flow scenarios, select the scenarios first and then select one of the options Start, Stop or Restart. Stopped integration flow scenarios don't process messages and stop all operations. Stopped integration flows remain stopped even if the NetWeaver Java Server or the application gets restarted.
Configuration of Log Levels in the MPL (Message Processing Log)
In the Cloud Integration Management Cockpit, you can configure MPL log levels for an integration flow. You can choose between the log levels:NONE, INFO, DEBUG or Trace. The default log level is INFO. In case of an error, the last 50 MLP events are stored. Log level Trace activates the writing of traces for message processing. You can display the traces in the Message Monitor for Cloud Integration Content. Writing of traces will remain enabled for 10 minutes and will automatically be disabled afterwards.
Download
You can download a support archive for SAP support analysis. This archive includes the generated web application for an integration flow.
Edit External Properties
Integration flows can have external properties, which are defined in the design of the scenario. The runtime values for the properties can be changed in the Cloud Integration Content Management Cockpit.
Select the integration flow and choose Properties → Configure to open a dialog box where you can change the values for each external property. You can save the external properties or directly redeploy the integration flow.
View Endpoints
Use End Points tab to view end points of services that are configured using SOAP, HTTP or OData adapter.
Display and Manage Locks
Use Locks tab to view and release locks created during message processing.
You can also search for table entries (search field).
To remove the lock entry and retrigger message processing, select the entry and choose Release.
Caution
Before releasing a lock entry, make sure you do a careful problem analysis. In particular, make sure that you have understood how the lock entry in question relates to the actual problem you are trying to solve. Careless usage of the release lock function may lead to data inconsistencies or other serious problems.
For example, in the case of an SFTP connection the lock entry is a file name (including the file path). In this case, check whether the problem is related to the file that is to be processed through SFTP.
Another indicator is the duration of the lock (time that has passed since the time specified under Created at).
Deploy and Manage JDBC Data Sources
JDBC Data Sources allow you to create and manage artifact connections to interact with a database. Each data source contains information on database-specific configuration parameters.
When you select a JDBC Data Source, the details display on the right side of the pane. The header area provides information on Configuration Parameters, on a specific database such as the Database Driver, Database URL, User, and so on.
Configure JMS Messaging
After having deployed the client libraries, you can configure the messaging runtime by creating a destination using the Cloud Integration Management Cockpit and selecting JMS.
The JMS configuration provides the following options for destination types:
- JNDI
- Uses JNDI to look up a JMS connection factory.
- Generic
- Uses provider-specific APIs to create a JMS connection factory.