Assistance Required for SSB Setup and XML Object Exporter Task in SailPoint IdentityIQ

Dear Team,

I have downloaded the SailPoint Standard Build (SSB) package from the SailPoint Community Compass and saved it in my local Downloads folder. After extracting the package, I placed the base version .war file under the ga folder (located in the Base directory) and the patch file under the patch folder as per the instructions.

Next, I attempted to export all custom objects using the β€œXML Object Exporter” task. However, I encountered the following error message:

C:/Users/6137491/Downloads/ssb-v7.0.2/config/Application/Application-CyberarkPamModuleServer.xml (No such file or directory)

Could you please guide me on the next steps? Should I copy and paste the entire SSB folder into the application server directory and rerun the task? Or is there a step I might have missed during the setup process?

Your assistance in resolving this issue would be greatly appreciated.

Best regards,
Venu

Hi @Venu1010 ,

You need to place the SailPoint IIQ zip file and not .war file in ga folder under base directory.

Ensure config directory and its child directories in SSB has necessary write permissions to export the sailpoint objects from the environment.

You can follow the SSB user guide for detailed steps.

https://community.sailpoint.com/t5/Professional-Services/Services-Standard-Build-SSB-v7-0-2/ta-p/190496

1 Like

Hi @Venu1010 ,

To export an object object exporter plug-in suffice

Just run XML Object Exporter” task and provide the file path under server where iiq is spinned up not local machine

And other related to ssb has already been answered by peer

Thanks
Avinash Mulpuru

1 Like

Yes, I have already completed the task. However, the process of exporting all objects from the development environment to SSB is taking longer than expected.

Just curious, what fixed the initial error you mentioned?

Just given the path where IIQ has access to write.

Why this error: SSB scans all referenced objects. If any application / rule / workflow referenced in your environment is missing in config, SSB fails fast.

β€œApplication-CyberarkPamModuleServer.xml” just happened to be the first missing object it encountered.

Step 1: Verify SSB directory structure

Inside ssb-v7.0.2, you should see something like:

ssb-v7.0.2/

β”œβ”€β”€ Base/

β”‚ β”œβ”€β”€ ga/

β”‚ β”‚ └── identityiq-8.x.war :white_check_mark:

β”‚ └── patch/

β”‚ └── identityiq-8.xp?.jar :white_check_mark:

β”œβ”€β”€ config/

β”‚ β”œβ”€β”€ Application/

β”‚ β”œβ”€β”€ Rule/

β”‚ β”œβ”€β”€ Workflow/

β”‚ └── …

β”œβ”€β”€ bin/

β”‚ └── iiq

└── build.properties

If the config/Application folder exists but is empty, that’s expected initially.

Step 2: Run XML Object Exporter from IIQ, not SSB

Log in to IdentityIQ UI β†’ Tasks β†’ New Task β†’
Choose XML Object Exporter

Important settings to check:

  • Target Directory β†’ must point to your SSB config folder
    Example:

  • C:/Users/6137491/Downloads/ssb-v7.0.2/config

  • Object Types β†’ select what you want (Application, Rule, Workflow, etc.)

  • Include dependencies β†’ recommended :check_mark:

This task creates files like:

config/Application/Application-CyberarkPamModuleServer.xml

That file is missing right now β€” that’s why SSB failed.

Step 3: Rerun the XML Object Exporter

After running successfully, verify manually:

ssb-v7.0.2/config/Application/

└── Application-CyberarkPamModuleServer.xml

Once this exists, the error you saw will go away.

Hope this helps!

1 Like

@Venu1010 Use the Export task from the UI which is a clean approach to export all relevant artefacts removing the ids and other environment specific attributes. You can also schedule this task to run everyday and either take complete backup or take backup of artefacts modified or created after a specific date.

Note: Found a fix? Help the community by marking the comment as solution. Feel free to react(:heart:, :+1:, etc.) with an emoji to show your appreciation or message me directly if your problem requires a deeper dive.

Hi @Venu1010

Export Task

How can I deploy all the information that I made in Dev environment to Testing Environment ?

        Using Object Exporter, we can achieve this. In One go, it can export all the objects/tasks, But by default it is not available in the product. We need to Explicitly Setup β€œObject Exporter”.

        Installation :

1. Shutdown Application Server

2. Add ExportXML.class to C:\IIQ\apache-tomcat-9.0.56\webapps\identityiq\WEB-INF\classes\sailpoint

3. Restart Application Server.

4. Now Import XML file in the console - > TaskDefinition_Export_XML

5. Go to Setup-> Tasks ->XML Object Exporter

6. Save and Execute.

SSD -Service Standard Deployment

1. Run Deployer

2. Update Base Folder

3. Update build.properties

4. Update Server.properties

5. Update Config Folder

6. Update env.target.properties file

7. Update env.ignore.properties

Run Deployer

Go to SSDV6 β†’ Run deploySSD.bat β†’ hit Enter

1. Is the detected path correct? [y|n] β†’ y

2. Would you like to create property files for additional targets? [y|n] β†’ y

3. Enter the additional targets separated with commas. Whitespace will be removed. β†’ dev,test,prod

4. Are you ready to deploy ? β†’ y

Update Base Folder

        We need to update base folder.

Go to SSDV6 β†’ base folder

Efix->not using

1. Ga β†’ General Availability.

2. Patch β†’ not using here.

3. Now Goto ga folder β†’ copy the complete identityiq and paste here

Update build.properties

Go to SSDV6 β†’ build.properties, we need to tell that what sailpoint version we are using ?

#required properties

1. IIQVersion=8.2

2. IIQPatchLevel=leave blank, no patch we are using

image

Update server.properties

Comment out everything.

Go to CMD->hostname ->copy host name and paste it

Your_Host_Name = test (to which environment, we need to deploy). Ex : prod,test

Update Config Folder

Open it, you can see many folders but they are blank. So now copy the complete folder from Export task folder into Config Folder. And This is enough to complete the β€œimport task to test”

        How to do it ? open SSDV6 ->*CMD*

                                                        >*build war* (creating war file)

Identityiq.war + Sp, add all the XML from config folder β†’ it gives new war file

>build successful.

if you get any error in the middle, see the CMD while file causing the issue. delete that file in ssd, now run the comman again. >build war

You can see new war file in ssd-v6\build\deploy\identityiq.war

Update env.ignoreFile.properties

Whatever file names we mention here, Those will be ignored from deployment process.

Full deployment β†’ identityiq.war + add all the XML from config folder = new war file

Partial Deployment β†’ Only deploy changes which are required instead of everything.

Go to SSDV6 β†’ build β†’ Extract β†’ WEB-INF ->config ->copy custom folder and sp.init-custom.xml.

Custom Folder β†’ Whatever files present inside config file, will be copied here.

Now open sp.init-custom.xml ->edit the files which you want to keep, in which env you need to deploy. In this case, no restart required.

Update env.target.properties

Is it going to same SP USERNAME AND PASSWORD for server ? for all env, No right.

Goto ->test.target.properties in ssd folder

Create tokens here

%%CMDB_USER_NAME%%=root

%%CMDB_PASSWORD%%=root

%%CMDB_HOSTNAME%%=localhost

Now wherever you see this username, password, hostname, Just replace with tokens.

Hope this is helpful

Note: Found a fix? Help the community by marking the comment as solution. Feel free to react(:heart:, :+1:, etc.) with an emoji to show your appreciation or message me directly if your problem requires a deeper dive

For SSB, Please refer this article/blog post:

1 Like