OpenText Product Documentation Portal

https://docs.microfocus.com/doc/397/24.1/
Admin
OpenText Product Documentation Portal provides comprehensive documentation for OpenText products...
Tokens:697,684
Snippets:4,983
Trust Score:9.7
Update:2 weeks ago
Show doc for...
Tokens:
Raw
### Start OO installer on Linux

Source: https://docs.microfocus.com/doc/397/24.1/cleaninstallall

Run this command from a Linux desktop or an X-Window terminal to start the OO installer. The OO installer requires an X11-based GUI to operate.

```bash
bash installer-oo-linux64-<version>.bin
```

--------------------------------

### Run Linux installer with bash command

Source: https://docs.microfocus.com/doc/397/24.1/cleaninstallall

Command to start the OO installer on Linux from a desktop or X-Window terminal. Requires an X11-based GUI to operate.

```bash
bash installer-oo-linux64-<version>.bin
        Copy
```

--------------------------------

### Example Git installation location for Studio

Source: https://docs.microfocus.com/doc/397/24.1/workinggit

Example value for the studio.git.installation.location property, showing the path format with forward slashes. The bin folder should be directly under C:/Program Files/Git.

```properties
studio.git.installation.location=C:/Program Files/Git
```

--------------------------------

### XML Get Element output example

Source: https://docs.microfocus.com/doc/397/24.1/filters

Example output of the XML Get Element filter when extracting the customer element from the sample XML. Shows the full element with attributes and child elements.

```xml
<customer firstName="John" lastName="Doe"> 
                  <company>myOrg</company>
                  <position>CIO</position>
                  <contactInfo>
                    <email>jdoe@myorg.com</email>
                    <email>johnsSecondEmail@myorg.com</email>
                    <mobile>12065551212</mobile>
                    <description internal="1">Private contact info</description>
                    <description>Partial contact info</description>
                  </contactInfo>
                  <description>Our best customer</description>
</customer>
```

--------------------------------

### GET /audit/records response example

Source: https://docs.microfocus.com/doc/397/24.1/auditevents

Example response body for the GET /audit/records request. Shows an array of audit event objects with fields like time, type, group, subject, outcome, and data.

```json
[

        Copy
        
```
   "time": 1412312016740,
   "type": "AuditConfigurationChange",
   "group": "AuditManagement",
   "subject": "mydomain\\myuser2",
   "outcome": "Success",
   "data": "{\"enabled\":false}"

        Copy
        
```

`}, { `
```
   "time": 1412312016722,
   "type": "InternalUserDelete",
   "group": "Authentication-Authorization",
   "subject": "mydomain\\myuser2",
   "outcome": "Success",
   "data": "{\"usersNames\": [\"admin\"]}"

        Copy
        
```

`}] 
```

--------------------------------

### Run installer with relative path to properties file

Source: https://docs.microfocus.com/doc/397/24.1/silentinstallssx

Example command for Windows when the installer and properties file are in a subdirectory (dirB) relative to the current directory (dirA). Uses double backslashes in the path.

```bash
dirB\\installer.exe -s silent.properties
```

--------------------------------

### Example idm.properties file

Source: https://docs.microfocus.com/doc/397/24.1/idmmode

Example configuration file for IdM integration in OO Central. Shows all required properties including URLs, usernames, encrypted passwords, signing key, tenant, and return URL. The return URL must use consistent protocol and ports throughout the login flow.

```properties
# IDM Properties
idm.configuration.url=https://idm-hostname:8443/idm-service/
idm.configuration.username=idmTransportUser
idm.configuration.password={ENCRYPTED}uNEBrRr29t/78P700j3BiA==
idm.configuration.internal.username=admin
idm.configuration.internal.password={ENCRYPTED}30l15qHg/7770l15qHgP700d2MiA==
idm.configuration.signing.key={ENCRYPTED}uWRUrRQ4BzUNr2EG/4PDfB700j9LiA==
idm.configuration.oo.central.tenant=OO_Central
idm.configuration.oo.central.return.url=https://central-hostname:8433/oo
```

--------------------------------

### Example idm.properties file

Source: https://docs.microfocus.com/doc/397/24.1/idmmode

Example configuration for the idm.properties file, showing the required properties for IdM integration, including the return URL and encrypted passwords.

```properties
# IDM Properties
idm.configuration.url=https://idm-hostname:8443/idm-service/
idm.configuration.username=idmTransportUser
idm.configuration.password={ENCRYPTED}uNEBrRr29t/78P700j3BiA==
idm.configuration.internal.username=admin
idm.configuration.internal.password={ENCRYPTED}30l15qHg/7770l15qHgP700d2MiA==
idm.configuration.signing.key={ENCRYPTED}uWRUrRQ4Bzr2EG/4PDfB700j9LiA==
idm.configuration.oo.central.tenant=OO_Central
idm.configuration.oo.central.return.url=https://central-hostname:8433/oo
```

--------------------------------

### Invalid script: extra lines starting with @

Source: https://docs.microfocus.com/doc/397/24.1/expressioneditor

Invalid script example: extra lines must not start with @. This shows an invalid description in the Expression Editor.

```text
@input input_name: this is the first line
                   @this is the second line
                   this is the third line
```

--------------------------------

### Get LWSSO configuration response body

Source: https://docs.microfocus.com/doc/397/24.1/lwssoconfiguration

Example JSON response body returned on a successful GET /authns/lwsso-config request. The initString is masked with asterisks.

```json
{
"enabled": false,
"initString": "************",
"domain": "mydomainnew1.com",
"protectedDomains": [
"mydomainnew1.com",
"mydomainnew2.com"
]
}
```

--------------------------------

### Example central-wrapper.conf values

Source: https://docs.microfocus.com/doc/397/24.1/changeservicename

Example values for the central-wrapper.conf file. The wrapper.name sets the service name, wrapper.displayname sets the display name, and wrapper.description sets the description. These are the values used in the example.

```plaintext
# Name of the service
```

```plaintext
wrapper.name=OOCentral
```

```plaintext
# Display name of the service
```

```plaintext
wrapper.displayname= Operations Orchestration Central
```

```plaintext
# Description of the service
```

```plaintext
wrapper.description=Operations Orchestration Central is the run time environment of Operations Orchestration. It is used for running flows, monitoring the various runs, and generating reports.
```
Tokens:
Raw