# Can I run Zowe on a separate LPAR to where z/OSMF is installed in the sysplex?
**URL:** https://community.openmainframeproject.org/t/can-i-run-zowe-on-a-separate-lpar-to-where-z-osmf-is-installed-in-the-sysplex/357
**Category:** Zowe
**Created:** [May 17, 2019, 10:35am UTC](https://community.openmainframeproject.org/t/can-i-run-zowe-on-a-separate-lpar-to-where-z-osmf-is-installed-in-the-sysplex/357 "2019-05-17T10:35:01Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@JoeWinchester](https://community.openmainframeproject.org/u/JoeWinchester)
#### Post date: [May 17, 2019, 10:35am UTC](https://community.openmainframeproject.org/t/can-i-run-zowe-on-a-separate-lpar-to-where-z-osmf-is-installed-in-the-sysplex/357/1 "2019-05-17T10:35:01Z")
… we are running sysplex with multiple zos images, zOSMF is running on one of the them. Can I create Zowe runtime on other images that no zOSMF running? Or do I must install runtime on the same image where zOSMF running?
---
### Author:  [@JoeWinchester](https://community.openmainframeproject.org/u/JoeWinchester)
#### Post date: [May 17, 2019, 10:48am UTC](https://community.openmainframeproject.org/t/can-i-run-zowe-on-a-separate-lpar-to-where-z-osmf-is-installed-in-the-sysplex/357/2 "2019-05-17T10:48:37Z")
The way that Zowe’s services connect to z/OSMF is through IP address, so this should work although we don’t allow a way to do this easily at install/configuration time. One thing that should work is to edit the IP address of where you want Zowe to find z/OSMF by updating the following files:
/api-mediation/api-defs/zosmf.yml. Edit the value in instanceBaseUrls. This is used by the API gateway to connect to z/OSMF
/explorer-data-sets-api/scripts/data-sets-api-server-start.sh. Edit the value zosmf.httpsport and zosmf.ipaddress. Do likewise in the file /explorer-jobs-api/scripts/jobs-api-server-start.sh.
At install time Zowe tries to import the z/OSMF certificate into its trust store and this will fail with z/OSMF on another system, however you can tell Zowe to trust the certificate and bypass this by editing the line -Dapiml.security.verifySslCertificatesOfServices=false \ in the three files /api-mediation/scripts/api-mediation-start-catalog.sh, api-mediation-start-discovery.sh, api-mediation-start-gateway.sh.