Deployer 10.7 | Product Build Properties and Supported Assets for Repository-Based Deployment | Integration Server | Integration Server Administrative Assets | Adding Administrative Assets to the Source Directory
 
Adding Administrative Assets to the Source Directory
To include administrative assets in the composite for deployment, you must manually copy or check in the Integration Server_directory \instances\instance_name\config folder to the source directory.
Note:
To include CloudStreams administrative assets in the composite for deployment, you must manually copy or check in the WmCloudStreams\config folder to the source directory, at the same location as the user-defined packages.
Software AG recommends that you structure your source directory to contain all of the administrative assets to be included in the composite as shown in the following example:
In this example, you would define SRC_ROOT as the value of the build.source.dir property in the build.properties file. For more information about the build.properties file, see Setting Build Properties.
If the asset you want to include in the composite contains passwords or encrypted values, you must also add the passman.cnf and txnPassStore.dat files in the SRC_ROOT/config directory.
When run, the build script creates the following:
*A composite named package_name.zip for each package included in the source directory, where package_name is the name of the package (with a composite type ID of ispackage). For this example, the files would be named packageA.zip and packageB.zip.
*A composite named isconfiguration.zip (with a composite type ID of isconfiguration) that contains the administrative assets contained in the config directory.
For more information about building composites for repository-based deployment, see Building Composites.
The following table lists the files and directories that you must manually copy or check in to the source directory in order to build Integration Server administrative assets for deployment.
Asset
Files to copy or check into the source directory
ACLs
*Integration Server_directory \instances\instance_name\config\users.cnf
*Integration Server_directory \instances\instance_name\config\acls.cnf
Broker settings
Integration Server_directory \instances\instance_name\config\dispatch.cnf
Cache manager
All Ehcache configuration files located in the Integration Server_directory \instances\instance_name\config\Caching directory.
Note:
Do not include system cache managers. For example, do not include cache managers whose names start with “SoftwareAG”.
Certificate settings
Integration Server_directory \instances\instance_name\config\server.cnf
Client certificate
The Asset Build Environment extracts this asset from the database.
*If you are using the embedded database, the Asset Build Environment must have access to Integration Server_directory \instances\instance_name\db\embedded directory.
*If you are using an external database, the Asset Build Environment requires access to the JDBC configuration files.
CSRF guard configuration
Integration Server_directory \instances\instance_name\config\security\csrf\csrfguard.cnf
Note:
Integration Server creates this file only when the CSRF guard option is enabled in Integration Server Administrator. For more information, see webMethods Integration Server Administrator’s Guide.
Enhanced parser
Integration Server_directory \instances\instance_name\config\parsing.cnf
Enterprise Gateway configuration
Integration Server_directory \instances\instance_name\config\security\enterprisegateway\enterpriseGatewayRules.cnf
Extended settings
Integration Server_directory \instances\instance_name\config\server.cnf
Global variables
Integration Server_directory \instances\instance_name\config\globalVariables.cnf
Groups
Integration Server_directory \instances\instance_name\config\users.cnf
IS Packages
For all the assets contained in the IS package ACDL file, you must check in the Integration Server_directory \instances\instance_name\packages\package_name directory (where package_name is the package for which the ACDL is required) to the source directory.
The following files are required to retain ACL information for the different assets in a package:
*Integration Server_directory \instances\instance_name\config\acls.cnf
*Integration Server_directory \instances\instance_name\config\aclmap_sm.cnf
*Integration Server_directory \instances\instance_name\config\acllist.cnf
*Integration Server_directory \instances\instance_name\config\aclread.cnf
*Integration Server_directory \instances\instance_name\config\aclwrite.cnf
JDBC driver alias
Integration Server_directory \instances\instance_name\config\jdbc\driver\*.xml
Note:
The Asset Build Environment does not extract default driver aliases that are installed with Integration Server.
JDBC functional alias
Integration Server_directory \instances\instance_name\config\jdbc\function\*.xml
JDBC pool alias
Integration Server_directory \instances\instance_name\config\jdbc\pool\*.xml
Note:
The Asset Build Environment does not extract the embedded database pool alias.
JMS aliases
Integration Server_directory \instances\instance_name\config\jms.cnf
JNDI aliases
Integration Server_directory \instances\instance_name\config\jndi\jndi_*.properties
Keystore alias
The Asset Build Environment extracts keystore alias details from the *_config.xml files stored in the Integration Server_directory \instances\instance_name\config\security\keystore directory and then reads the actual keystore binary file (the .jks or .p12) from the value found in the "location" field of the keystore alias definition.
LDAP configuration
Integration Server_directory \instances\instance_name\config\ldap.cnf
Metadata
Integration Server_directory \instances\instance_name\packages\WmAssetPublisher\config\assetpublisher.cnf
Mobile Support configuration
*Integration Server_directory \instances\instance_name\packages\WmMobileSupport\config\mobileSyncComponents.cnf
*Integration Server_directory \instances\instance_name\packages\WmMobileSupport\config\mobileApp.cnf
For more information about these assets, see Mobile Support .
MQTT connection alias
Integration Server_directory \ instances\instance_name\packages\package_name\config\commonmessaging.cnf
Ports
Integration Server_directory \instances\instance_name\packages\package_name\config\listeners.cnf
Proxy server alias
Integration Server_directory \instances\instance_name\config\proxy.cnf
Proxy server bypass
Integration Server_directory \instances\instance_name\config\server.cnf
Note:
The Asset Build Environment does not extract this file if watt.net.proxySkipList is set to localhost. For more information about watt.net.proxySkipList, see webMethods Integration Server Administrator’s Guide.
Quiesce mode configuration
Integration Server_directory \instances\instance_name\config\quiesce.cnf
Reliable messaging configuration
Integration Server_directory \instances\instance_name\config\reliableMessaging.cnf
Remote server alias
Integration Server_directory \instances\instance_name\config\remote.cnf
Note:
The Asset Build Environment does not extract remote server aliases named "local".
SAML token issuer
Integration Server_directory \instances\instance_name\config\security\saml\trusted_saml_issuers.cnf
Scheduled tasks
The Asset Build Environment extracts this asset from a database, and requires either of the following:
*If you are using the embedded database, the Asset Build Environment must have access to Integration Server_directory \instances\instance_name\db\embedded directory.
*If you are using an external database, the Asset Build Environment requires access to the JDBC configuration files.
SFTP server alias
Integration Server_directory \instances\instance_name\config\sftp\sftpServerAliases.cnf
SFTP user alias
*Integration Server_directory \instances\instance_name\config\sftp\sftpUserAliases.cnf
*Integration Server_directory \instances\instance_name\config\sftp\identities directory and its contents
Truststore alias
The Asset Build Environment extracts truststore alias details from the *_config.xml files stored in the Integration Server_directory \instances\instance_name\config\security\keystore directory and reads the actual truststore binary file (.jks or .p12) from the value found in the "location" field of the truststore alias definition.
Universal Messaging connection alias
Integration Server_directory \instances\instance_name\config\messaging.cnf
URL alias
Integration Server_directory \instances\instance_name\packages\package_name\config\urlalias.cnf
Users
Integration Server_directory \instances\instance_name\config\users.cnf
Integration Cloud Accounts
Integration Server_directory \config\integrationlive\connections.cnf
Integration Cloud Applications
Integration Server_directory \config\integrationlive\applications directory
Integration Cloud Settings
Integration Server_directory \config\integrationlive\accounts.cnf
Web service endpoint alias
Integration Server_directory \instances\instance_name\config\endpoints\*.cnf
Web service policy
All .policy files in the Integration Server_directory \instances\instance_name\config\wss\policies directory
CloudStreams OAuth Tokens
Integration Server_directory\instances\instance_name\WmCloudStreams\config\auth\cls-oauthDetails.xml
CloudStreams Streaming Providers
Integration Server_directory\instances\instance_name\WmCloudStreams\config\resources\streaming\config.xml
CloudStreams Streaming Subscribers
Integration Server_directory\instances\instance_name\WmCloudStreams\config\resources\streaming\config.xml
CloudStreams Administration Database
WmCloudStreams\config\resources\wst-config.properties
CloudStreams Large Data Configuration
WmCloudStreams\config\resources\wst-config.properties