Deploying the connector involves the following steps:
Depending on the release of Oracle Identity Manager that you use, perform the procedures described in one of the following sections:
The following sections provide configuration instructions that are specific to the target system database:
You configure IBM DB2 UDB by ensuring that:
Authentication on IBM DB2 UDB is done through the operating system. Therefore, the user that you want to provision must exist in the security system of the operating system.
For example, if you want to provision the domain, then the target (IBM DB2 UDB server) must exist on the domain server and the user that you want to provision must exist in the domain.
For databases or services that you want to provision to a login entity, you must enter the relevant lookup codes, corresponding to the databases or services that already exist on the target system, in the UD_Lookup.DB_DB2UDB_DBName lookup definition in Oracle Identity Manager.
Note:
For tablespaces that you want to provision to a user entity, configure the DBAccessLookupReconTask scheduled task in Oracle Identity Manager to populate the UD_Lookup.DB_DB2UDB_Tablespaces lookup definition.
For schemas that you want to provision to a user entity, configure the DBAccessLookupReconTask scheduled task in Oracle Identity Manager to populate the UD_Lookup.DB_DB2UDB_Schema lookup definition.
See "Configuring the Reconciliation Scheduled Tasks for Lookup Fields" for more information.
You configure Microsoft SQL Server by ensuring that:
The target database in which users are to be created exists in the target Microsoft SQL Server installation.
The Microsoft SQL Server user account that is used to create users has DBA privileges. For example, the sa/sa account.
For Microsoft SQL Server 2000 and 2005, ensure that:
The TCP/IP port is enabled. The default port is 1433.
To enable the TCP/IP port:
i. Open the Microsoft SQL Server Configuration Manager.
ii. Click SQL Server Network Configuration.
iii. Click Protocols for MSSQLSERVER.
iv. In the right frame, right-click TCP/IP and then click Enable.
The TCP/IP port is not the only port enabled.
Mixed mode authentication is enabled.
The TCP/IP port is not blocked by a firewall.
Note:
For a database that you want to provision to a user entity, configure the DBAccessLookupReconTask scheduled task in Oracle Identity Manager to populate the UD_Lookup.DB_SQL_DBNames lookup definition.
For a language that you want to provision to a user entity, configure the DBAccessLookupReconTask scheduled task in Oracle Identity Manager to populate the UD_Lookup.DB_SQL_DefaultLang lookup definition.
For a role that you want to provision to a user entity, configure the DBAccessLookupReconTask scheduled task in Oracle Identity Manager to populate the UD_Lookup.DB_SQL_DBRoles lookup definition.
See "Configuring the Reconciliation Scheduled Tasks for Lookup Fields" for more information.
To configure Oracle Database:
Ensure that the service name used to create users exists in the target Oracle Database installation.
Run one of the following scripts on the target system to create the target system user account for connector operations:
On Microsoft Windows platforms:
OIM_HOME/XLIntegrations/DatabaseAccess/SQLScripts/OIM.bat
On UNIX platforms:
OIM_HOME/XLIntegrations/DatabaseAccess/SQLScripts/OIM.sh
When you run the script, the following privileges are granted to the user:
CREATE SESSION
CREATE USER
GRANT ANY PRIVILEGE
GRANT ANY ROLE
ALTER USER
DROP USER
SELECT ON DBA_ROLE_PRIVS
SELECT ON DBA_USERS
SELECT ON DBA_ROLES
SELECT ON DBA_TABLESPACES
SELECT ON DBA_PROFILES
SELECT ON DBA_PROFILES
SELECT ON DBA_SYS_PRIVS
CREATE TABLE
You provide the credentials of this user account while configuring the IT resource. The procedure is described later in the guide.
Note:
For a role that you want to provision to a user entity, configure the DBAccessLookupReconTask scheduled task in Oracle Identity Manager to populate the UD_Lookup.DB_ORA_Roles lookup definition.
For a privilege that you want to provision to a user entity, configure the DBAccessLookupReconTask scheduled task in Oracle Identity Manager to populate the UD_Lookup.DB_ORA_Privileges lookup definition.
For a profile that you want to provision to a user entity, configure the DBAccessLookupReconTask scheduled task in Oracle Identity Manager to populate the UD_Lookup.DB_ORA_Profiles lookup definition.
For a default tablespace that you want to provision to a user entity, configure the DBAccessLookupReconTask scheduled task in Oracle Identity Manager to populate the UD_Lookup.DB_ORA_Tablespaces lookup definition.
For a temporary tablespace that you want to provision to a user entity, configure the DBAccessLookupReconTask scheduled task in Oracle Identity Manager to populate the UD_Lookup.DB_ORA_TempTablespaces lookup definition.
See "Configuring the Reconciliation Scheduled Tasks for Lookup Fields" for more information.
You configure Sybase by ensuring that:
The target database in which logins and users are to be created exists in the target Sybase ASE installation.
The procGrantAllToUser.sql script is run on the target Sybase database. This file contains the stored procedures that create and grant the required roles to the Sybase user for connector operations.
The procRevokeAllFromUser.sql script is run on the target Sybase database. This file contains the stored procedures that revoke roles from the Sybase user for connector operations.
Refer to the "Copying the Connector Files" section for instructions to copy these files from the connector installation package.
Note:
For default databases that you want to provision to login entities, enter lookup codes corresponding to the databases that already exist on the target system in the UD_Lookup.DB_Sybase_Databases lookup definition.
For default languages that you want to provision to login entities, enter lookup codes corresponding to the languages supported by the target system in the UD_Lookup.DB_Sybase_DefaultLang lookup definition.
For roles that you want to provision to login entities, enter lookup codes corresponding to the roles defined on the target system in the UD_Lookup.DB_Sybase_Roles lookup definition.
For database groups that you want to provision to user entities, enter lookup codes corresponding to the database groups on the target system in the UD_Lookup.DB_Sybase_DBGroups lookup definition.
See Oracle Identity Manager Design Console Guide for information about modifying lookup definitions.
Depending on the target system, perform the steps given in one of the following sections to copy external code files:
Note:
While installing Oracle Identity Manager in a clustered environment, you copy the contents of the installation directory to each node of the cluster. Similarly, you must copy the contents of the connectorResources directory and the JAR files to the corresponding directories on each node of the cluster.
For connectors used with IBM DB2 UDB, copy the db2jcc.jar and db2jcc_license_cu.jar files from the DB2_HOME/IBM/SQLLIB/java directory into the OIM_HOME/xellerate/ThirdParty directory.
After you copy the external code file, proceed to the "Importing the Connector XML Files" section.
For connectors used with Microsoft SQL Server 2000 target systems, the required external JAR files are the JDBC driver files: mssqlserver.jar, msbase.jar, and msutil.jar.
To obtain these files, first download Microsoft SQL Server 2000 Driver for JDBC Service Pack 4 from the Microsoft Web site.
For connectors used with Microsoft SQL Server 2005, the required external JAR file is the sqljdbc.jar JDBC driver file. This file can be downloaded from the Microsoft Web site.
You must copy the required JAR files into the OIM_HOME/xellerate/ThirdParty directory.
If the connector is used with Oracle8i Database, then the required external code file is classes12.jar.
If the connector is used with Oracle9i Database or Oracle Database 10g, then the required external code file is ojdbc14.jar.
These JAR files are available in the Oracle Database installation at, for example, the following path:
ORACLE_HOME/jdbc/lib
In this directory path, ORACLE_HOME is the location where Oracle Database is installed. For example, C:\Oracle\ora92.
You must copy the required JAR file (classes12.jar or ojdbc14.jar) into the OIM_HOME/xellerate/ThirdParty directory.
Note:
If you are using Oracle Identity Manager release 9.0.3.1 or later, then the ojdbc14.jar file is already present in the ThirdParty directory.
After you copy the external code file, proceed to the "Importing the Connector XML Files" section.
For connectors used with Sybase ASE, copy the jconn2.jar file from the SYBASE_HOME/jConnect-5_5/classes directory into the OIM_HOME/xellerate/ThirdParty directory.
Note:
In this guide, the term Connector Installer has been used to refer to the Connector Installer feature of the Oracle Identity Manager Administrative and User Console.
Installing the connector on Oracle Identity Manager release 9.1.0 or later involves the following procedures:
To run the Connector Installer:
Copy the contents of the connector installation media into the following directory:
OIM_HOME/xellerate/ConnectorDefaultDirectory
Log in to the Administrative and User Console by using the user account described in the "Creating the User Account for Installing Connectors" section of Oracle Identity Manager Administrative and User Console.
Click Deployment Management, and then click Install Connector.
From the Connector List list, select Database Access RELEASE_NUMBER. This list displays the names and release numbers of connectors whose installation files you copy into the default connector installation directory:
OIM_HOME/xellerate/ConnectorDefaultDirectory
If you have copied the installation files into a different directory, then:
In the Alternative Directory field, enter the full path and name of that directory.
To repopulate the list of connectors in the Connector List list, click Refresh.
From the Connector List list, select Database Access RELEASE_NUMBER.
Click Load.
To start the installation process, click Continue.
The following tasks are performed in sequence:
Configuration of connector libraries
Import of the connector Target Resource user configuration XML file (by using the Deployment Manager). If you want to import the target system as a trusted source for reconciliation, then see "Configuring the Target System As a Trusted Source".
Compilation of adapters
On successful completion of a task, a check mark is displayed for the task. If a task fails, then an X mark and a message stating the reason for failure are displayed. Depending on the reason for the failure, make the required correction and then perform one of the following steps:
Retry the installation by clicking Retry.
Cancel the installation and begin again from Step 0.
If all three tasks of the connector installation process are successful, then a message indicating successful installation is displayed. In addition, a list of the steps that you must perform after the installation is displayed. These steps are as follows:
Ensuring that the prerequisites for using the connector are addressed
Note:
At this stage, run the PurgeCache utility to load the server cache with content from the connector resource bundle in order to view the list of prerequisites. Refer to "Clearing Content Related to Connector Resource Bundles from the Server Cache" for information about running the PurgeCache utility.
There are no prerequisites for some predefined connectors.
Configuring an IT resource for the connector
Record the name of the IT resource displayed on this page. The procedure to configure the IT resource is described later in this guide.
Configuring the scheduled tasks that are created when you installed the connector
Record the names of the scheduled tasks displayed on this page. The procedure to configure these scheduled tasks is described later in this guide.
When you run the Connector Installer, it copies the connector files and external code files to destination directories on the Oracle Identity Manager host computer. These files are listed in Table 1-2.
Installing the Connector in an Oracle Identity Manager Cluster
While installing Oracle Identity Manager in a clustered environment, you must copy all the JAR files and the contents of the connectorResources directory into the corresponding directories on each node of the cluster. See Table 1-2 for information about the files that you must copy and their destination locations on the Oracle Identity Manager server.
Note:
Perform this procedure if you are installing the connector on Oracle Identity Manager release 9.1.0 or later.
You must specify values for the parameters of the IT resource as follows:
Log in to the Administrative and User Console.
Expand Resource Management.
Click Manage IT Resource.
In the IT Resource Name field on the Manage IT Resource page, enter the name of one of the following IT resources, and then click Search:
For IBM DB2 UDB, enter DB2UDB.
For Microsoft SQL Server, enter MS SQL Server.
For Oracle Database, enter Oracle Database.
For Sybase, enter Sybase Server.
Click the edit icon for the IT resource.
From the list at the top of the page, select Details and Parameters.
Specify values for the parameters of the IT resource. Refer to "IT Resources" for information about the parameters of the IT resource.
To save the values, click Update.
Installing the connector on any Oracle Identity Manager release between releases 8.5.3.1 and 9.0.3.1 involves the following procedures:
The connector files to be copied and the directories to which you must copy them are given in the following table.
See Also:
"Files and Directories on the Installation Media" for more information about these files
| File in the Installation Media Directory | Destination Directory |
|---|---|
lib/xliDatabaseAccess.jar |
OIM_HOME/xellerate/JavaTasks OIM_HOME/xellerate/ScheduleTask |
|
Files in the |
OIM_HOME/xellerate/connectorResources
|
|
Files in the |
OIM_HOME/xellerate/XLIntegrations/DatabaseAccess/SQLScripts
|
|
Files in the |
OIM_HOME/xellerate/XLIntegrations/DatabaseAccess/config
|
|
Files in the |
OIM_HOME/xellerate/XLIntegrations/DatabaseAccess/config
|
|
Files in the |
OIM_HOME/xellerate/XLIntegrations/DatabaseAccess/scripts
|
|
Files in the |
OIM_HOME/xellerate/XLIntegrations/DatabaseAccess/xml
|
Note:
In a clustered environment, copy the JAR files and the contents of the connectorResources directory to the corresponding directories on each node of the cluster.
Definitions of the connector objects are in the following XML files:
For IBM DB2 UDB, the connector object definitions are in the xliDBAccessLogin_DM Nontrusted.xml file.
For Microsoft SQL Server, the connector object definitions are in the xliDBAccessLogin_DM Nontrusted.xml and xliDBAccessUser_DM Nontrusted.xml files.
For Oracle Database, the connector object definitions are in the xliDBAccessLogin_DM Nontrusted.xml file.
For Sybase, the connector object definitions are in the xliDBAccessLogin_DM Nontrusted.xml and xliDBAccessUser_DM Nontrusted.xml files.
To import the required connector XML files into Oracle Identity Manager:
Open the Oracle Identity Manager Administrative and User Console.
Click the Deployment Management link on the left navigation bar.
Click the Import link under Deployment Management. A dialog box for opening files is displayed.
Locate and open the xliDBAccessLogin_DM Nontrusted.xml file, which is in the OIM_HOME/xellerate/XLIntegrations/DatabaseAccess/xml directory. Details of this XML file are shown on the File Preview page.
Click Add File. The Substitutions page is displayed.
Click Next. The Confirmation page is displayed.
Click Next. The Provide IT Resource Instance Data page for the Oracle Database IT resource is displayed. If this is the IT resource corresponding to the database that you are using, then perform the next step. Otherwise, click Next until the Provide IT Resource Instance Data page for the IT resource of the database that you are using is displayed.
Depending on the database that you are using, specify values for the parameters of the IT resource. Refer to the appropriate table in the "IT Resources" section for information about the values to be specified.
Click Next. The Provide IT Resource Instance Data page for a new instance of the Database IT resource type is displayed.
Click Skip to specify that you do not want to define a new IT resource. The Confirmation page is displayed.
See Also:
If you want to define another IT resource, then refer to Oracle Identity Manager Administrative and User Console Guide for instructions.
Click View Selections.
The contents of the XML file are displayed on the Import page. You may see a cross-shaped icon along with some nodes. These nodes represent Oracle Identity Manager entities that are redundant. Before you import the connector XML file, you must remove these entities by right-clicking each node and then selecting Remove.
Click Import. The connector file is imported into Oracle Identity Manager.
If you use Microsoft SQL Server or Sybase, then import the xliDBAccessUser_DM Nontrusted.xml file by performing Steps 3 through 12.
This section provides IT resource parameter values for the following databases:
You must specify values for the IBM DB2 UDB IT resource parameters listed in the following table.
| Parameter | Description |
|---|---|
|
|
Type of RDBMS Value: |
|
|
Not required |
|
|
JDBC driver class Value: com.ibm.db2.jdbc.net.DB2Driver |
|
|
JDBC URL for the target database (Note: The URL that you specify must be less than 2000 characters long.) Value: jdbc:db2://Target_Host:Port_Number/DatabaseName Sample value: jdbc:db2://10.1.1.127:6789/TESTDB Note: Use the IP address, not the computer name or host name. When the connector is used with Microsoft SQL Server 2000, Microsoft SQL Server 2005, or IBM DB2 UDB, the URL parameter of the IT resource accepts only the IP address of the target computer on which the database is installed. You cannot specify the host name of the computer as the value of the URL parameter. |
|
|
User name of the DBA login that is used to create, update, and delete users Sample value: |
|
|
Password of the DBA login that is used to create, update, and delete users |
|
|
Country code Default value: Note: You must specify the value in uppercase. |
|
|
Language code Default value: Note: You must specify the value in lowercase. |
|
|
Specifies whether or not a secure connection must be set up to the target system The value can be Note: This feature is supported only on for the Oracle Database. |
|
|
Number of times that the connector must retry connecting to the target server, if the connection fails Default value: |
|
|
Delay (in milliseconds) before the connector attempts to retry connecting to the target system, if the connection fails Default value: |
After you specify values for these IT resource parameters, proceed to Step 9 of the procedure to import connector XML files.
You must specify values for the Microsoft SQL Server IT resource parameters listed in the following table.
| Parameter | Description |
|---|---|
|
|
Type of RDBMS Value: |
|
|
Name of the target database in which users are created Sample value: |
|
|
For Microsoft SQL Server 2000 JDBC driver class: com.microsoft.jdbc.sqlserver.SQLServerDriver For Microsoft SQL Server 2005 JDBC driver class: com.microsoft.sqlserver.jdbc.SQLServerDriver |
|
|
JDBC URL for the target database (Note: The URL that you specify must be less than 2000 characters long.) For Microsoft SQL Server 2000 Format: jdbc:microsoft:sqlserver://Target_Host:Port_number;DatabaseName=DatabaseName Sample value: jdbc:microsoft:sqlserver://192.168.49.64:1433;DatabaseName=XELL Note: Use the IP address, not the computer name or host name in this URL. For Microsoft SQL Server 2005 Format: jdbc:sqlserver://serverName;instanceName:portNumber;property=value[;property=value] Sample value: jdbc:sqlserver://123.12.23.321:1433;database=master Note: Use the IP address, not the computer name or host name in this URL. |
|
|
User name of the DBA login that is used to create, update, and delete users Sample value: |
|
|
Password of the DBA login that is used to create users |
|
|
Country code Default value: Note: You must specify the value in uppercase. |
|
|
Language code Default value: Note: You must specify the value in lowercase. |
|
|
Specifies whether or not a secure connection must be set up to the target system The value can be Note: This feature is supported only on Oracle Database. |
|
|
Number of times that the connector must retry connecting to the target server, if the connection fails Default value: |
|
|
Delay (in milliseconds) before the connector attempts to retry connecting to the target system, if the connection fails Default value: |
After you specify values for these IT resource parameters, proceed to Step 9 of the procedure to import connector XML files.
You must specify values for the Oracle Database IT resource parameters listed in the following table.
| Parameter | Description |
|---|---|
|
|
Type of database Value: |
|
|
Name of the target database in which users are created Sample value: |
|
|
JDBC driver class Value: |
|
|
JDBC URL for the target database (Note: The URL that you specify must be less than 2000 characters long.) The URL value that you must specify depends on the number of database instances and the services they support:
|
|
|
User name of the Oracle Database user account that is used to create, update, and delete users See "Configuring Oracle Database" for information about creating this user account. |
|
|
Password of the Oracle Database user account that is used to create, update, and delete users |
|
|
Country code Default value: Note: You must specify the value in uppercase. |
|
|
Language code Default value: Note: You must specify the value in lowercase. |
|
|
Specifies whether or not a secure connection must be set up to the target system The value can be |
|
|
Number of times that the connector must retry connecting to the target server, if the connection fails Default value: |
|
|
Delay (in milliseconds) before the connector attempts to retry connecting to the target system, if the connection fails Default value: |
After you specify values for these IT resource parameters, proceed to Step 9 of the procedure to import connector XML files.
You must specify values for the Sybase Server IT resource parameters listed in the following table.
| Parameter | Description |
|---|---|
|
|
Type of RDBMS Value: |
|
|
Name of the target database in which users are created Sample value: |
|
|
JDBC driver class Value: com.sybase.jdbc2.jdbc.SybDriver |
|
|
JDBC URL for the target database (Note: The URL that you specify must be less than 2000 characters long.) Format: jdbc:sybase:Tds:Target_Host:Port_Number/DatabaseName Sample value: jdbc:sybase:Tds:integnt:5000/master |
|
|
User name of the DBA login that is used to create, update, and delete users Sample value: See "Configuring Sybase" for more information about this user account. |
|
|
Password of the DBA login that is used to create users |
|
|
Country code Default value: Note: You must specify the value in uppercase. |
|
|
Language code Default value: Note: You must specify the value in lowercase. |
|
|
Specifies whether or not a secure connection must be set up to the target system The value can be Note: This feature is supported only on for the Oracle Database. |
|
|
Number of times that the connector must retry connecting to the target server, if the connection fails Default value: |
|
|
Delay (in milliseconds) before the connector attempts to retry connecting to the target system, if the connection fails Default value: |
After you specify values for these IT resource parameters, proceed to Step 9 of the procedure to import connector XML files.
This section discusses the following topics:
Note:
In a clustered environment, you must perform this step on each node of the cluster.
Deploying the Microsoft Active Directory Connector If IBM DB2 UDB Is Used
Clearing Content Related to Connector Resource Bundles from the Server Cache
Note:
Perform this step only if the target system is IBM DB2 UDB.
IBM DB2 UDB installed on a Microsoft Windows server does not support the creation of user accounts. Instead, it uses operating system users. It assigns the required privileges to a Microsoft Windows user to convert the user into a complete IBM DB2 UDB user. After a user account is created in Microsoft Windows, it can be assigned the relevant privileges in IBM DB2 UDB.
Therefore, if you want to use the Database User Management connector to provision accounts in IBM DB2 UDB, then you must first deploy the connector for Microsoft Active Directory.
See Also:
Oracle Identity Manager Connector Guide for Microsoft Active Directory
Changing to the required input locale (language and country setting) involves installing the required fonts and setting the required input locale.
You may require the assistance of the system administrator to change to the required input locale.
Change the length of the SVP_FIELD_VALUE column in the SVP table to 2000 as follows:
Log in to the Oracle Identity Manager database by using the Oracle Identity Manager database user credentials.
Enter the following command at the SQL prompt:
For Oracle Database:
ALTER TABLE SVP MODIFY SVP_FIELD_VALUE VARCHAR2(2000);
For Microsoft SQL Server:
ALTER TABLE SVP ALTER COLUMN SVP_FIELD_VALUE VARCHAR(2000);
While performing the instructions described in the "Copying the Connector Files" section, you copy files from the resources directory on the installation media into the OIM_HOME/xellerate/connectorResources directory. Whenever you add a new resource bundle in the connectorResources directory or make a change in an existing resource bundle, you must clear content related to connector resource bundles from the server cache.
To clear content related to connector resource bundles from the server cache:
In a command window, change to the OIM_HOME/xellerate/bin directory.
Note:
You must perform Step 1 before you perform Step 2. An exception is thrown if you run the command described in Step 2 as follows:
OIM_HOME\xellerate\bin\batch_file_name
Enter one of the following commands:
On Microsoft Windows:
PurgeCache.bat ConnectorResourceBundle
On UNIX:
PurgeCache.sh ConnectorResourceBundle
Note:
You can ignore the exception that is thrown when you perform Step 2.
In this command, ConnectorResourceBundle is one of the content categories that you can remove from the server cache. Refer to the following file for information about the other content categories:
OIM_HOME/xellerate/config/xlConfig.xml
When you enable logging, Oracle Identity Manager automatically stores in a log file information about events that occur during the course of provisioning and reconciliation operations. To specify the type of event for which you want logging to take place, you can set the log level to one of the following:
ALL
This level enables logging for all events.
DEBUG
This level enables logging of information about fine-grained events that are useful for debugging.
INFO
This level enables logging of messages that highlight the progress of the application at a coarse-grained level.
WARN
This level enables logging of information about potentially harmful situations.
ERROR
This level enables logging of information about error events that may allow the application to continue running.
FATAL
This level enables logging of information about very severe error events that could cause the application to stop functioning.
OFF
This level disables logging for all events.
The file in which you set the log level and the log file path depend on the application server that you use:
Oracle WebLogic Server
To enable logging:
Add the following line in the OIM_HOME/xellerate/config/log.properties file:
log4j.logger.OIMCP.DUTC=log_level
In this line, replace log_level with the log level that you want to set.
After you enable logging, log information is displayed on the server console.
IBM WebSphere Application Server
To enable logging:
Add the following line in the OIM_HOME/xellerate/config/log.properties file:
log4j.logger.OIMCP.DUTC=log_level
In this line, replace log_level with the log level that you want to set.
After you enable logging, log information is written to the following file:
WEBSPHERE_HOME/AppServer/logs/SERVER_NAME/SystemOut.log
JBoss Application Server
To enable logging:
In the JBoss_home/server/default/conf/log4j.xml file, add the following lines if they are not already present in the file:
<category name="OIMCP.DUTC">
<priority value="log_level"/>
</category>
In the second XML code line, replace log_level with the log level that you want to set.
After you enable logging, log information is written to the following file:
JBoss_home/server/default/log/server.log
Oracle Application Server
To enable logging:
Add the following line in the OIM_HOME/xellerate/config/log.properties file:
log4j.logger.OIMCP.DUTC=log_level
In this line, replace log_level with the log level that you want to set.
After you enable logging, log information is written to the following file:
OC4J_home/opmn/logs/default_group~home~default_group~1.log